UIASAPV1: UiPath Automation Solution Architect Professional Exam

UiPath Automation Cloud APIs support Personal Access Tokens, OAuth 2.0 for External Apps, and API Keys. Certificate-based authentication, Windows Authentication, and Basic Authentication are not listed as supported Automation Cloud API authentication methods.

UiPath Automation Hub is a collaborative tool for identifying automation opportunities and managing them through the automation pipeline, including review, prioritization, and implementation tracking.

UiPath Connector Builder supports creating custom connectors for APIs and defining their operations, authentication, and parameters. The resulting API operations are exposed as custom activities that can be used in UiPath workflows, making a custom connector the appropriate way to support an unsupported endpoint.

A decoupled Document Understanding process with one job per input file isolates failures and retries to the affected document, reducing unnecessary reprocessing and associated consumption. Separate jobs also provide clearer workload and robot-utilization visibility and allow the document-processing capacity to scale independently. UiPath documents that this architecture separates upstream input handling and downstream use of extracted information, while processing each input file as its own job.

When sizing the robot fleet, the Solution Architect must plan for the worst case: peak data/transaction volume drives how much processing capacity is needed within the SLA window, while the size of the operations (business) team represents the current manual workload/FTE effort the automation is expected to absorb. Together these determine how many robots are required. Option C is wrong because you size for volume peaks, not lows, and shift timings alone do not set capacity. BCP, application performance, and technical approach are relevant design concerns but are not the primary drivers of the robot count.