UiPath Updated UiPath-AAAv1 Exam Questions and Answers by inaaya

The correct answer isD— theOutcome Behavior sectionis where you configure how the agent should respond once an escalation is resolved by a human.

In UiPath’sagent design process, when a task is escalated to a human reviewer (viaAction Center, for instance), the agent:

Waits for human input

Receives anOutcome(e.g., Approve, Reject, Flag)

Then continues its process based on logic defined in theOutcome Behavior

This may include:

Proceeding with the automation

Triggering an alternate flow

Logging results or escalating further

Other options are incorrect or refer to unrelated settings:

A (Assignment recipient list) defineswhogets the task — not what happens after.

B (Agent Memory toggle) governscontext retention, not post-escalation behavior.

C (Input descriptions) help users understand fields but don’t control flow logic.

TheOutcome Behavior sectionensures agents respondintelligently and consistently after human interaction, which is critical in hybrid workflows involving both automation and human-in-the-loop review.

Cis correct — an agentic story that falls into the"Do Later"quadrant typically representshigh feasibility but low impact.

In UiPath’sImpact vs. Feasibility Matrix, used during theAgentic Discoveryphase, automation ideas are evaluated on:

Feasibility(ease of implementation)

Impact(business value, time saved, ROI)

Quadrants:

Quick Wins: High impact, high feasibility

Do Later: Low impact, high feasibility

Strategic Bets: High impact, low feasibility

Avoid/Backlog: Low on both

‘Do Later’ agentic stories are often simple to automate but don’t deliver meaningful outcomes — e.g., automating low-volume tasks or internal reports with limited audience.

Focusing onimpactful use casesensures agent development time translates to real business value — one of the key lessons from UiPath’s agentic blueprint methodology.

Dis correct — includingwell-designed examplesin prompts is a key part offew-shot learning, which helps LLM-based agents better understand thetask structure, output style, and expected behavior.

UiPath encourages the use of examples for:

Classification(e.g., labeling sentiment, email categories)

Transformation tasks(e.g., turning unstructured text into tables)

Step-by-step instructions(e.g., troubleshooting flows)

These examples serve two purposes:

Pattern induction: The model picks up on consistent structures or rules used across examples.

Generalization: With diverse examples, the agent can apply logic to unseen but similar cases.

Best practice:

Usetypical, real-world examplesrepresentative of the data the agent will encounter.

Keep formatsclear and consistentacross input-output pairs.

Pair examples withexplicit instructionsin the system or user prompt.

Option A is flawed — focusing only on edge cases can confuse the model.

B is false — omitting examples forces the LLM to guess the structure, reducing accuracy.

C is misleading — examples improve performance butdo not guarantee perfect output; testing and evaluation are still required.

In short,prompt engineering with examples is essentialto buildingreliable, generalizable, and scalableAI agents.

The correct answer isA—clear, structured instructions about output formatare essential for consistent LLM responses, even when few-shot examples are present.

UiPath’sPrompt Engineering Frameworkemphasizes the use of:

Explicit formatting rules(e.g., “Use bullet points with bolded headers”)

Output instructions(e.g., “List items under appropriate sections: Decisions, Action Items, Next Steps”)

Consistent prompt structure: combining examples with a detailedtask instruction

Without such instructions, LLMs — even with examples — mayhallucinate structure, interpret outputs loosely, or switch formats between runs.

This is especially important inagentic automation, where the output feeds downstream steps (e.g., emails, documents, summaries). Inconsistent format breaks reliability and automation flow.

Option B (length constraints) helps refine but isn’t the root issue here.

C (randomized formatting) introduces inconsistency — not helpful.

D describes the issue but not themissing critical step, which is the instruction.

UiPath advises combining:

Few-shot examples+

Task description+

Format constraints→ for best results in structured content generation.