A.  

It is only used for modeling static workflows without support for dynamic or unpredictable process changes.

B.  

It solely provides tools for designing aesthetic workflows, with no focus on controlled automation or dynamic process management.

C.  

It acts as an enabler for standards-based, model-driven collaboration between business groups and IT implementers.

D.  

It lacks constructs such as error and exception handling support, limiting its use for controlled automation design.

A.  

When you plan to paste several different tables in succession during the same chat and expect Autopilot for Everyone to queue each paste automatically.

B.  

Whenever you need to paste any content regardless of operating system, file type, or the number of pastes.

C.  

When you are working on a Windows machine and need to perform a single AI-powered paste of a table (for example, from a PDF) into another application directly from the chat interface.

D.  

When you are using macOS and want Autopilot for Everyone to perform a copy and paste on a Linux VM.

A.  

A System Prompt is a technical script integrated into the automation process that determines tool usage and escalation protocols without considering natural language descriptions.

B.  

A System Prompt is a predefined list of actions and commands the agent strictly follows without adaptation or interaction over time.

C.  

A System Prompt allows a user to describe its role, goals, and constraints while specifying rules and guidelines for actions, including the use of tools, escalations, and context.

D.  

A System Prompt defines only the agent's constraints but does not address goal-setting or sequencing steps.

A.  

Guardrails are used exclusively to automate all tool corrections without the possibility of triggering human intervention.

B.  

Guardrails control unexpected behaviors within tool calls deterministically, allowing developers to configure conditions for human intervention and escalations.

C.  

Guardrails are designed to apply only after tool execution, without influencing pre-execution conditions.

D.  

Guardrails only validate tool inputs during development and do not address unpredictable behaviors at runtime.

A.  

Assignment recipient list

B.  

Agent Memory toggle

C.  

Inputs description fields

D.  

Outcome behavior section

A.  

Use robots (RPA) for the structured, repetitive tasks, leveraging their rule-based approach for reliability and precision, while agents handle the unstructured processes by using their adaptive decision-making capabilities.

B.  

Use agents exclusively, as they can cover both structured workflows and dynamic environments due to their probabilistic and adaptive nature.

C.  

Use robots (RPA) exclusively, as they are capable of adapting to dynamic workflows with exception handling and learning capabilities.

D.  

Use agents for the structured, repetitive tasks, as they can follow deterministic rules efficiently while robots (RPA) handle unstructured workflows requiring adaptability, decision-making capabilities and contextual awareness.

A.  

Static value

B.  

Clear value

C.  

Prompt

D.  

Argument

A.  

By identifying all feasible use cases without considering the potential impact or business benefit of implementing them.

B.  

By focusing solely on high-impact use cases without considering whether implementing them is feasible with available resources.

C.  

By evaluating use cases based on their potential business improvement and ease of implementation considering current resources and technology.

D.  

By prioritizing the automation of all processes regardless of their feasibility or actual impact on the organization.

A.  

Excessive flexibility in handling varied workflows across different systems like CRM and ERP

B.  

Over-reliance on AI-powered agents for all types of automation tasks

C.  

Limited ability to automate unstructured tasks that require judgment and contextual awareness

D.  

Inability to perform repetitive, structured tasks efficiently and reliably

A.  

It ensures the agent understands the tool's purpose and can use it effectively in relevant scenarios.

B.  

It guarantees that agents can access and modify any business application data, even without tool integration.

C.  

It limits the agent's actions to only those explicitly allowed by the user prompt, preventing incorrect reasoning.

D.  

It allows agents to execute all types of actions automatically, including Context Grounding and Escalations.

A.  

It reduces the risk of hallucination by referencing ground truth data stores.

B.  

It directly increases the LLM context window size without any interaction with knowledge bases.

C.  

It eliminates the need for knowledge bases by integrating all proprietary data directly into generative applications.

D.  

It exclusively provides access to historical data sources without supporting real-time updates.

A.  

Task

B.  

Swimlane

C.  

User Task

D.  

Exclusive Gateway

A.  

High feasibility and High Impact

B.  

Low feasibility and High Impact

C.  

High feasibility and Low Impact

D.  

Low feasibility and Low Impact

A.  

You are an invoice-approval agent who deals only with supplier invoices and rejects any other request.

Extract invoice_ID from the email text.

When an invoice_ID is found, run the LookupInvoice tool to retrieve invoice amount and supplier name.

If the total ≤ $10,000, escalate the case to Finance in Action Center, sending invoice_ID, amount, and supplier.

If the total > $10,000, approve the invoice.

Retu

B.  

You are an invoice-approval agent who deals only with supplier invoices and rejects any other request.

Extract {{invoice_ID}} from the email text.

When an {{invoice_ID}} is found, run the LookupInvoice tool to retrieve invoice amount and supplier name.

If the total ≤ $10,000, escalate the case to Finance in Action Center, sending {{invoice_ID}}, amount, and supplier.

If the total > $10,000, approve the invoice

C.  

You are an invoice approver. After processing, output exactly the following JSON template:

{ "id": "ABC-123", "status": "approved", "amount": 9999.9 }

Extract {{invoice_ID}} from the email text.

When an {{invoice_ID}} is found, run the LookupInvoice tool to retrieve invoice amount and supplier name.

If the total ≤ $10,000, escalate the case to Finance in Action Center, sending {{invoice_ID}}, amount, and suppl

D.  

You are an invoice approver. After processing, output exactly the following JSON template:

{ "id": "ABC-123", "status": "approved", "amount": 9999.9 }

Extract the {{invoice_ID}} from the email text.

Use LookupInvoice to get the invoice amount and supplier name.

Escalate to Finance if amount ≤ $10,000.

If amount > $10,000, approve the invoice.

Populate the fields above with real data.

A.  

Adding clear instructions detailing the output format.

B.  

Including constraints to limit the length of the agenda for simplicity.

C.  

Adding randomized formatting examples to test the agent's creativity.

D.  

Providing only examples without additional context about the task.

A.  

It defines the current way tasks are performed, helping to highlight inefficiencies, bottlenecks, and areas for improvement that can uncover automation potential.

B.  

It serves as a finalized map of processes ready for automation, removing the need for further adjustments or workshops.

C.  

It directly outlines the roles that agents will assume in the optimized process, ensuring alignment with automation requirements.

D.  

It establishes the goals of the new process, serving as a foundation to later create the "to-be" process map.

A.  

They are limited to handling structured workflows only.

B.  

They cannot integrate with UiPath Orchestrator.

C.  

They require extensive coding expertise for development.

D.  

They allow for quick agent creation using a low-code development application.

A.  

It modifies the similarity threshold for chunk retrieval and lowers the number of tokens used.

B.  

It makes the agent ignore all context completely, resulting in outputs that are entirely disconnected from the indexed data, regardless of its relevance to the query or prompt provided.

C.  

It changes the number of chunks returned, impacting both the size of the grounding payload and the filtering of relevant information.

D.  

It selects which Orchestrator folder to use, determining the location of stored workflows and deciding which set of predefined rules will apply during data retrieval and processing.