UiPath-ADPv1 Advanced UI Automation Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  CV activities automatically generate stable selectors that are stored in the Object Repository and can be reused without re-indication.

  Why it's wrong here

  CV activities use descriptors based on image and text patterns, not traditional selectors stored in the Object Repository. While CV descriptors can be saved and reused, they are not equivalent to UI Automation selectors and are not automatically generated in the Object Repository. Reusability requires explicit configuration and may still be sensitive to resolution or theme changes.

• ✓

  CV activities can interact with elements inside a Citrix session because they analyze pixels from screenshots rather than relying on the operating system's accessibility tree.

  Why this is correct

  Computer Vision works by capturing screenshots of the target application and using OCR and image analysis to identify elements. This approach bypasses the accessibility tree entirely, which is why it can see elements inside a Citrix session where standard UI Automation cannot. It is the primary reason CV is recommended for virtualized environments like Citrix.

• ✗

  CV activities eliminate the need for the Citrix session to be visible on the screen, because they can capture hidden windows.

  Why it's wrong here

  Computer Vision requires the target application to be visible on the screen so that screenshots can be captured. If the Citrix session is minimized or hidden, CV cannot see the elements. This is a common misconception; CV does not work with hidden or off-screen windows, and the session must be active and visible.

• ✓

  CV activities require the UiPath Computer Vision server and a valid API key configured in Orchestrator or in the activity properties.

  Why this is correct

  Computer Vision activities rely on the UiPath Computer Vision server, which can be cloud-hosted or on-premises. A valid API key must be configured either in Orchestrator settings or directly in the CV activities' properties. Without this key, the activities cannot send screenshots for analysis and will fail. This is a fundamental requirement for using CV in any environment, including Citrix.

• ✗

  CV activities are always faster than standard UI Automation activities because they process screenshots in parallel.

  Why it's wrong here

  Computer Vision is generally slower than standard UI Automation because it involves capturing screenshots, sending them to a server for analysis, and receiving element coordinates. This round-trip introduces latency. The claim that CV is always faster is incorrect; it is chosen for compatibility, not speed, and performance depends on network and server responsiveness.