Cisco
CompTIA
ISC
EC-Council
EXIN
Fortinet
ITIL
Juniper
Microsoft
VMware
Avaya
SAP
Google
NVIDIA
Salesforce
Amazon
Palo Alto Networks
ISC2
Splunk
ServiceNow
All Vendors
  2. Home
  3. Exams
  4. UiPath
  5. UiPath-ADAv1

UiPath UiPath-ADAv1 Exam
UiPath Automation Developer Associate v1 (Page 8 )

Updated On: 1-Feb-2026
Page 8 of 52
PDF with 254 Questions

If you are inserting activities into a Sequence in UiPath Studio, in which panel do the activities appear?

  1. Snippets
  2. Designer
  3. Imports
  4. Outline

Answer(s): B

Explanation:

The Designer panel is the central panel in UiPath Studio, where you can design your automation workflows by dragging and dropping activities.
When you insert activities into a Sequence, they appear in the Designer panel as a linear representation that flows from top to bottom. The Snippets panel contains ready-made workflows that you can reuse in your projects. The Imports panel allows you to import namespaces and libraries that you can use in your workflows. The Outline panel shows the hierarchical structure of your project and its components.


Reference:

The User Interface, Sequences



In which situation will a Ul Automation activity generate a partial selector?

  1. When included after a Find Element activity
  2. When included in an Attach Browser activity
  3. When included in an Excel Application Scope activity
  4. When included in a Trigger Scope activity

Answer(s): B

Explanation:

A partial selector is a selector that does not contain the information about the top-level window. A partial selector is usually generated when a UI Automation activity is included in a container activity, such as Attach Browser or Attach Window, that has a full selector of the outer window. This way, the UI Automation activity can use the partial selector relative to the container, instead of the full selector from the root. Therefore, the answer is B. When included in an Attach Browser activity.


Reference:

Full Versus Partial Selectors, Attach Browser



DRAG DROP (Drag and Drop is not supported)
A developer finished creating an automation project in UiPath Studio 2021 10 What is the recommended sequence of steps that should be performed to publish the package to Orchestrator 2021.10?
Instructions: Drag the Description found on the left and drop on the correct Step found on the right

  1. See Explanation section for answer.

Answer(s): A

Explanation:




The recommended sequence of steps that should be performed to publish the package to Orchestrator 2021.10 is:
Step 1 = Navigate to the Design Ribbon and then click the "Publish" button Step 2 = Select an Orchestrator feed as the "Publish to" location and then click the "Publish" button Step 3 = Add the Release Notes and ensure the version is incremented Step 4 = Validate that the "Info" dialog box displays and shows the package version number This sequence will ensure that the developer can publish the automation project to the Orchestrator feed of their choice, add some notes about the changes made, and verify that the package is successfully published with the correct version number. https://docs.uipath.com/orchestrator/standalone/2021.10/user-guide/about-packages



In the Catches section of the Try Catch activity a developer selected ArgumentException in the exception handler.

What happens when the activity encounters a NullReferenceException?

  1. The Finally block is not executed and a runtime error occurs.
  2. The Finally block executes and no exception is thrown.
  3. The Catches section catches the exception and the Finally block is executed.
  4. The Catches section catches the exception and the Finally block is skipped.

Answer(s): A

Explanation:

When the activity encounters a NullReferenceException, the Finally block is not executed and a runtime error occurs. This is because the Catches section of the Try Catch activity only handles the ArgumentException type, which is a specific type of exception that occurs when one of the arguments provided to a method is not valid. A NullReferenceException is a different type of exception that occurs when there is an attempt to dereference a null object reference. Since the Catches section does not have a handler for the NullReferenceException type, the exception is not caught and the execution is stopped with a runtime error. The Finally block, which contains the activities that are always executed regardless of the outcome of the Try Catch activity, is also skipped.


Reference:

ArgumentException Class, NullReferenceException Class, and Try Catch from UiPath documentation.



A developer executes the following workflow in Debug mode with "Continue on Exception " enabled.



How many times will the workflow pause the execution?

  1. 0
  2. 1
  3. 2
  4. 3

Answer(s): B

Explanation:

The workflow will pause the execution only once when it is executed in Debug mode with "Continue on Exception" enabled. Debug mode is a mode of execution that allows the developer to test and troubleshoot the workflow by using various debugging tools, such as breakpoints, step actions, and output messages. "Continue on Exception" is a debugging option that enables the execution to continue even if an exception is encountered, without displaying the error message or stopping at the faulty activity. In the workflow, there are two activities that can throw exceptions: the "Throw" activity, which throws a custom exception with the message "This is an exception", and the "Write Line" activity, which writes the value of the "Var" variable to the Output panel. The "Var" variable is not initialized, so it has a null value by default.
When the "Write Line" activity tries to write the null value, it throws a NullReferenceException, as explained in the previous question. However, since the "Continue on Exception" option is enabled, the execution does not stop at the "Write Line" activity, but continues to the next activity, which is the "Throw" activity. The "Throw" activity throws the custom exception, which is caught by the "Catch" section of the "Try Catch" activity. The "Catch" section contains a "Log Message" activity, which writes the exception message to the Output panel. The execution then moves to the "Finally" section, which contains a "Write Line" activity with the text "This is the end". The workflow then ends successfully. The only time the execution pauses is when it reaches the breakpoint that is set at the "Throw" activity. A breakpoint is a debugging tool that allows the developer to pause the execution at a specific activity and inspect the values of the variables and arguments, as well as the output messages. The developer can then resume the execution by using the step actions or the continue button. Therefore, the workflow will pause the execution only once at the breakpoint, and not at the exceptions, as they are ignored by the "Continue on Exception" option.


Reference:

Debugging a Workflow, Debugging Actions, Breakpoints, and Continue on Exception from UiPath documentation.



Viewing page 8 of 52
Viewing questions 36 - 40 out of 254 questions



Post your Comments and Discuss UiPath UiPath-ADAv1 exam prep with other Community members:

Join the UiPath-ADAv1 Discussion