Free UiPath-ADAv1 practice test: 30 questions with answers

Rule-based robots apply the same steps every time, which cuts manual keying errors and shortens processing inside the window. The other options either remove needed controls (full removal of review, direct database access) or only add cost without fixing the error rate (more temporary staff).

In agentic automation an AI model reasons about which tool or step to use next, while deterministic workflows keep their fixed steps. The other options describe purely scripted automation or wrongly claim that agents make Orchestrator unnecessary, since it still manages jobs, queues and assets.

Studio is the design and development tool used to build and test projects, while Orchestrator publishes packages and manages robot execution, schedules and queues. The other pairings swap or misplace these roles, such as putting production queues in Studio or authoring workflows inside robots.

The PDD is the business-facing document covering the process as it runs today and as it should run, while the SDD is the technical design covering components and integrations. The SDD does not come first, the PDD holds no compiled code, and folder and machine settings are not PDD content.

An attended robot runs alongside a person who starts it and can wait at a review step, which suits human approval. An unattended robot runs with no one present, while an Orchestrator tenant and a Studio Web session are not robot types and do not hold claim data.

A Flowchart lets a developer connect activities with arrows, which makes branching, merging and backward loops easy to show. A Sequence runs its steps in order and can contain If decisions, while the Global Exception Handler and Invoke Workflow File do not provide flow layout.

A variable is only visible inside the container where it is declared, so it must be declared in a parent container that encloses both Sequences. Redeclaring it creates a new empty variable, a Delay does not keep data available, and writing to the Output panel does not transfer a value into a variable.

An Out argument carries a value from the invoked workflow back to its caller, which matches returning a computed tax value. An In argument only sends data in, an In/Out argument expects the caller to supply a value it does not need to give, and a Text asset is shared storage rather than an argument.

A While activity evaluates its condition before each pass, so it can run zero times when the condition is false at the start. Do While checks after each pass and always runs at least once, For Each iterates over a collection, and Switch chooses a branch rather than looping.

Studio Web is the browser-based version of Studio, so it avoids installing desktop software. Studio Desktop needs installation, Orchestrator manages and runs automations rather than editing them, and attended robots run automations rather than providing a workflow editor.

Retry Scope repeats the wrapped activities a set number of times with an interval between attempts, which matches the requirement. Try Catch handles a failure once without repeating it, Rethrow passes an exception on without retrying, and Log Message records text without changing the flow.

Rethrow raises the currently caught exception again, so the outer handler receives the original error. Throw creates a new exception, Log Message only records information, and Retry Scope repeats the work instead of passing the error on.

Breakpoints pause execution so the developer can inspect variables, and stepping commands move through the workflow one activity at a time. Log Message also writes entries in normal runs, a breakpoint only pauses the debug session, and a local debug run does not change queue item statuses.

Trace is the lowest and most verbose level, so it captures the finest-grained detail during troubleshooting. Info records normal progress, Warn flags unexpected but non-fatal conditions, and Fatal marks failures that stop the process.

A dynamic descriptor with a wildcard handles the changing id, while the stable label keeps the match reliable. A static id fails on every new load, fixed coordinates break when the layout shifts, and Get Text reads a value without performing the click.

Get Text is an output activity that reads the visible text of a UI element into a variable. Type Into and Click send input to the interface, and Hover only moves the pointer, so none of them capture the balance.

The Unified Target property holds how a modern activity finds its UI element and can combine several identification methods. Display name, workflow arguments and logging level do not identify UI elements, so they cannot fix the lookup.

A shared UI Library holds reusable element definitions that many projects reference, so one update reaches all of them. Separate copies drift out of sync, separate jobs do not fix element lookup, and re-recording wastes effort in every project.

Modern Excel activities such as Read Range read the workbook directly and do not need Excel installed on the machine. Excel Application Scope and UI actions on the grid both depend on Excel being available, and reading each cell through the UI is slow for 5,000 rows.

SMTP sends outgoing mail, and POP3 retrieves messages so a client can download them. IMAP is used to read and manage mail rather than send it, and the Gmail and Microsoft 365 activities connect to cloud mail services, so the last two statements are wrong.

A scanned PDF holds only page images, so the figures must be recognised with OCR. Read PDF Text depends on an existing text layer, opening the file in Excel does not read it, and a regular expression on the file name never sees the figures.

Regex Builder is the tool for constructing and checking a regular expression before it is used in an activity. The other options open a worksheet, log messages or read tables from Excel, and none of them helps build a matching pattern.

A Git branch lets a developer work on changes separately and merge them after review. Robot runtimes, storage buckets and assets are Orchestrator or runtime concepts and do not isolate source changes.

A template gives each new project the same starting structure and standard components. A snippet covers only a small reusable fragment, an Orchestrator folder groups server-side resources rather than creating a project, and a Workflow Analyzer rule checks a project without setting one up.

A data-driven test case loops over rows of a DataTable, so one test workflow covers many input sets. Mock testing isolates dependencies rather than varying inputs, a Retry Scope only repeats failures, and manually starting attended robots is slow and hard to repeat.

Mock testing substitutes the real dependency with simulated responses so the workflow can be tested in isolation. Running against a live service risks real transactions, relying on production logs finds problems too late, and moving logic to a spreadsheet changes the design rather than testing it.

Assets, queues and storage buckets are folder-level resources in Orchestrator, so each one belongs to the folder where it is created. A tenant sits above folders rather than inside one, and Workflow Analyzer rule sets belong to Studio rather than to Orchestrator folders.

A Credential asset keeps the username and password outside the workflow, and it can be changed in Orchestrator without republishing. A text asset would expose the password in plain text, a Boolean cannot hold a password, and a local variable would embed the secret in the project.

A business exception marks the queue item as Failed with a business exception type, and the framework does not retry it automatically. Setting it back to New would retry it, marking it Successful hides a real failure, and leaving it In Progress keeps it locked to a robot that has finished.

A folder role with view access to queues and no edit rights on assets limits the user to what the task requires. Tenant administrator rights, robot credentials and edit rights on every folder all grant far more access than the task needs.