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.

• ✗

  Change the project's UI Automation framework to 'AA' and re-indicate the SAP transaction fields, because Active Accessibility exposes all SAP controls.

  Why it's wrong here

  SAP GUI does not expose its transaction fields through Microsoft Active Accessibility by default. Switching to the AA framework would not make the internal fields visible because the underlying accessibility provider is not implemented for them. The correct enabler is SAP GUI Scripting, not a change to the MSAA framework, which is relevant for other legacy applications.

• ✗

  Use the 'UiPath.SAP.Activities' package and replace all UI Automation activities with its dedicated SAP activities, because they do not require any server-side configuration.

  Why it's wrong here

  There is no official UiPath.SAP.Activities package that bypasses SAP GUI Scripting requirements. SAP automation in UiPath relies on the standard UI Automation activities combined with SAP GUI Scripting enabled. Claiming a package avoids server-side configuration is incorrect, as SAP's own security settings must permit scripting for any client to access transaction fields.

• ✗

  Set the UiPath.UIAutomation.Activities package to use the 'Java' framework and re-indicate the elements, because SAP GUI is built on Java.

  Why it's wrong here

  SAP GUI for Windows is a native Win32 application, not a Java application. The Java framework in UiPath targets Java Access Bridge-enabled applications such as those built with Swing or AWT. Applying the Java framework to SAP GUI will not expose the transaction fields and is based on an incorrect assumption about SAP's technology stack.

• ✓

  Enable the 'SAP GUI Scripting' setting on both the SAP server and the SAP GUI client, and ensure the UiPath.UIAutomation.Activities package is configured to use the SAP framework.

  Why this is correct

  SAP GUI Scripting must be enabled server-side and client-side to expose the internal transaction fields to automation tools. UiPath's UI Automation package includes a SAP framework that leverages this scripting interface to detect individual controls. Without both server and client scripting enabled, the transaction area remains a single opaque canvas, and no framework switch can expose its elements.