The correct answer isA- zero-shot prompting refers toasking an LLM to perform a task without providing any prior examples in the prompt. In UiPath Agentic Automation, this is considered the simplest form of task prompting and is often used when:
* The request isstraightforwardorfamiliar to the LLM
* There'sno need for detailed contextor task demonstration
* You want rapid generation without lengthy prompt design
UiPath distinguisheszero-shot,few-shot, andchain-of-thought promptingas part of itsPrompt Engineering Toolkit. While zero-shot is fast and scalable, it's not ideal fornuanced or ambiguous tasks, which often benefit fromfew-shot examplesor structured reasoning steps.
Option B is misleading - complex scenarios usuallyrequiremore grounding.
C contradicts the definition of zero-shot.
D confuses prompting withmodel fine-tuning, which is a separate concept.
Zero-shot works well for common, templated tasks (e.g., classifying "Is this urgent?") but is less reliable in dynamic, multi-intent agent behaviors.

Bis the correct answer - in UiPath'sAgent Builder (Studio Web), when you want to invoke an existing UiPath process from an agent (viaTools # Processes), that process must meettwo key prerequisites:
* It must be published and deployed to a shared Orchestrator folder
* You - and the agent - must have access to that folder
This ensures that:
* The agent canlocate and run the processat execution time
* Role-based access control (RBAC) is respected
* Input/output arguments, execution logs, and exceptions are properly managed within the correct environment This aligns with UiPath'sOrchestrator-integrated agent orchestration model, where security and deployment visibility are tightly governed. It also allows agent authors toreuse existing RPA logicinside dynamic agent flows without duplicating automation work.
Option A and D incorrectly imply that argument types affect process visibility - that's false. Agents can invoke processes withany argument signature, as long as mapping is defined.
Option C is incorrect - publishing alone is not enough.Deployment and permissionsare required for the process to appear in the tool selector.
This model ensures that agents can call any compliant UiPath processsecurely, reliably, and in line with enterprise governance.

The correct answer isC-Business Process Model and Notation (BPMN)is astandards-based modeling languageused byprocess excellence practitionersto visually define, communicate, and govern business workflows.
In UiPath'sMaestroorchestration platform, BPMN acts as acollaborative bridgebetween:
* Business stakeholders(who define processes and goals)
* Technical implementers(who build automations and agent logic)
BPMN includes rich constructs such as:
* Gateways for conditional logic
* Events for escalations and errors
* Tasks, subprocesses, and human interventions
This makes itideal for dynamic, agentic workflows- not just static process mapping.
A and B are false - BPMN is built foradaptive,automated, andcollaborativeorchestration.
D is wrong - BPMN supportserror handling, retries, and fallback flows, all critical in agentic automation.

Bis correct - when a field (likeChannel Id) is set toPrompt, the agent will attempt to infer its valueat runtime, based on theinstructions in the promptand the context provided.
This is the default and preferred mode for agent tools when:
* The agent has enough context or memory to decide
* You wantLLM autonomyin filling the field dynamically
* You're using prompt instructions like: "Post to the user's default Slack channel" Option A is incorrect - "Argument" is used when you're passing aspecific variableinto the agent prompt (not inferred).
C misunderstands data flow direction - "Output" is not relevant for input fields.
D is invalid - "Variable" is not the standard method for field inference in this scenario.
This aligns with UiPath'sagent + tools orchestrationmodel usingStudio Web's low-code agent builder.

The correct answer isB- defining outcomes like"Approve"and"Deny"within an Action schema is critical for guiding downstream logic in agent behavior, especially in scenarios involvinghuman-in-the-loop reviews.
According to UiPath's documentation forAction Center, outcomes act asexplicit decision points. When a user completes a review (e.g., a document, output, or classification), the selected outcome drives what the agent or automation should do next - for example:
* "Approve"might trigger further processing or submission.
* "Deny"could lead to rework, escalation, or termination of the process.
This is especially relevant inagentic workflows, where the agent offloads uncertain tasks to humans, and the human response informs the next step via outcome-driven branching logic.
Options A, C, and D refer to unrelated features like data validation, mandatory fields, or UI tweaks - none of which define thelogical consequencesthat outcomes control.