Free UiPath-AABPv1 sample questions

Correct answer: API workflow

An API workflow in Studio Web is specifically designed to chain API calls, Integration Service connector activities, and structured data transformations without requiring UI automation. Because all three target systems expose REST APIs and connectors and no GUI interaction or non-deterministic reasoning is needed, an API workflow provides the fastest, lightest, and most reliable execution model.

Correct answer: True

UiPath enforces a solution-level lock across Studio Web and Studio Desktop. This lock prevents more than one user from working on the same solution simultaneously across either authoring environment, ensuring package and resource consistency across all projects inside the solution.

Correct answer: 7 Agent Units (6 Agent Units for the 3 Premium model calls plus 1 Agent Unit for the Standard model guardrail call)

For UiPath-hosted models, Agent Units are charged per LLM call made during an agent run: Premium models (such as Claude Opus 4.6, Claude Opus 4.7, GPT-5.5, and GPT-5.6 Sol) consume 2 Agent Units per LLM call, whereas Standard models (such as GPT-4o, Claude Sonnet 4.6, and Gemini 2.5 Pro) consume 1 Agent Unit per LLM call. Furthermore, the LLM as Judge guardrail makes its own LLM call and consumes Agent Units at the same per-model tier rates, which are tracked separately and added to the agent's own consumption (3 calls × 2 Agent Units + 1 call × 1 Agent Unit = 7 Agent Units). Flat per-run charging applies only to Customer-managed (Bring Your Own Model / Subscription) configurations.

Correct answer: Robot Units for the serverless unattended execution and AI Units for both Document Understanding and Semantic activities

Under the UiPath Flex licensing plan, Robot Units measure consumption for running unattended automations on UiPath-hosted robots, including Automation Cloud Robots - VM, Automation Cloud Robots - Serverless, and Automation Suite Robots - Serverless. AI Units measure consumption across AI products and features including AI Center, Document Understanding, IXP, Task Mining, Process Mining, GenAI Activities, and Semantic activities. Agent Units are reserved for agent-specific execution and LLM as Judge guardrails.

Correct answer: Web applications default to the DOM find method, which uses the DOM Extractor and an LLM to reach off-screen elements present in the DOM, whereas non-web applications default to the Image find method, which relies on the visible screen image and multimodal image grounding.

Semantic selectors support two find methods: DOM (Document Object Model) and Image. For web applications, the default find method is DOM, which uses the DOM Extractor and an LLM to inspect the page structure and can locate off-screen elements as long as they are present in the DOM. For non-web applications, the default find method is Image, which relies on the visible screen image and multimodal image grounding, meaning off-screen controls must be visible on screen to be located.

Correct answer: Use ScreenPlay with natural-language prompts to handle the high-branching, layout-changing hotel websites, and use classic deterministic UI Automation activities for the stable internal ERP data entry.

UiPath best practice for UI Automation is to keep workflows maximally deterministic and minimally agentic. Classic deterministic UI Automation should be used wherever the interface is stable and steps are known—such as the internal ERP window—because deterministic steps execute identically, fastest, and at the lowest cost. ScreenPlay should be reserved for parts of the workflow where selectors fail repeatedly, UIs change frequently, or high-branching navigation across many external websites requires cognitive, natural-language navigation. flowchart TD Start([Start Process]) --> CheckUI{UI Stability & Structure} CheckUI -->|Dynamic / High-Branching across 120 Sites| SP[Use ScreenPlay Cognitive Navigation] CheckUI -->|Stable & Known Internal ERP| Det[Use Classic Deterministic UI Automation] SP --> Consolidate[Consolidate Extracted Data] Consolidate --> Det Det --> Finish([Complete])