UiPath Certified Professional Infrastructure Engineer Professional - Automation Suite Questions and Answers
How much storage does a large-sized robot require on an Automation Suite Robots node?
Options:
4 GiB
6 GiB
8 GiB
10 GiB
Answer:
DExplanation:
Automation Suite Robots (serverless containerized execution engines) can be provisioned across different standardized capacity tiers (e.g., Small, Medium, Large) based on workload requirements. UiPath hardware sizing documentation specifies that a "Large" robot configuration requires 10 GiB of dedicated local storage on the Automation Suite Robots agent node. Large robot configurations are designed for complex automations involving heavy dependencies, local document caching, multi-step browser interactions, and large data payloads. The 10 GiB storage allocation provides sufficient disk headroom for ephemeral container overlays, temporary execution artifacts, application logs, and runtime packages without triggering local disk throttling or container evictions. Infrastructure engineers must account for these per-robot storage allocations when sizing the root volumes and data disks of dedicated robot agent nodes to support target concurrent execution densities. (Reference: UiPath Automation Suite Sizing Guide – Automation Suite Robots Hardware Specifications).
===============
What is needed for both Active/Passive and Active/Active configurations in Automation Suite?
Options:
Redis High Availability Add-on license.
Single-node deployment.
Low-cost servers.
Separate user authentication modules.
Answer:
AExplanation:
Configuring multi-site disaster recovery models for UiPath Automation Suite—whether implemented in an Active/Passive failover setup or a concurrent Active/Active configuration—requires a Redis High Availability Add-on (HAA) license for both clusters. Redis serves as the distributed cache, session state manager, and synchronization engine for platform microservices, including Orchestrator and Identity Server. In multi-site topologies, cache states, user sessions, and connection brokering must be synchronized across clusters to ensure seamless failover and state consistency. The Redis High Availability Add-on provides cross-site replication and data consistency, requiring appropriate licensing across both participating clusters. Standard single-node Redis deployments are not supported for multi-site deployments. (Reference: UiPath Automation Suite High Availability – Redis Licensing and Multi-Site Requirements).
===============
After updating the input.json file to enable or disable products in UiPath Automation Suite for AKS/EKS/OpenShift, which command should you run to apply the updated configuration to the cluster?
Options:
uipathctl deploy --config input.json
uipathctl config apply input.json
uipathctl update cluster --config input.json
uipathctl manifest apply input.json --versions versions.json
Answer:
DExplanation:
In managed Kubernetes environments—such as Amazon EKS, Azure AKS, and Red Hat OpenShift—UiPath Automation Suite utilizes a declarative deployment model. The desired state of the suite, including enabled capabilities, database connections, and ingress rules, is defined within `input.json`. Whenever changes are made to this configuration, administrators must execute `uipathctl manifest apply input.json --versions versions.json` to reconcile the active cluster state with the declared specifications. This command evaluates discrepancies between the existing Helm releases and the updated `input.json` file, generates execution plans, and provisions or removes target microservices accordingly. Commands like `uipathctl deploy` or `uipathctl config apply` do not exist within the toolchain CLI parser and will return command syntax errors. (Reference: UiPath Automation Suite on AKS/EKS/OpenShift – Service Lifecycle and Manifest Reconciliation).
===============
For an OpenShift Automation Suite deployment, which command generates the support bundle?
Options:
./support-bundle.sh
./configureUiPathAS.sh support bundle generate
./configureUiPathDisks.sh
./uipathctl health bundle input.json --versions version.json
Answer:
DExplanation:
When troubleshooting errors or escalating issues to UiPath Technical Support for an Automation Suite deployment running on Red Hat OpenShift, engineering teams are required to compile and export a comprehensive diagnostic package. The standardized command to produce this package is `./uipathctl health bundle input.json --versions versions.json` (or referencing the active versions file, e.g., `version.json`). Executing this command triggers automated diagnostic routines that collect cluster-level logs, pod events, container standard output/error streams, Helm release histories, OpenShift route configurations, and platform configuration summaries based on the parameters specified in `input.json`. Older bash scripts like `configureUiPathAS.sh` have been superseded on managed Kubernetes and OpenShift platforms by the unified `uipathctl` CLI toolchain. The resulting compressed bundle contains sanitized telemetry, allowing support architects to isolate pod evictions, storage volume detachments, or database timeouts. (Reference: UiPath Automation Suite on OpenShift – Health Checks and Diagnostic Bundles).
===============
What are the main differences in deployment architecture between online and offline UiPath Automation Suite installations?
Options:
Both online and offline installations require the same network configuration and hardware specifications.
Online installation uses a predefined set of components with limited customization options, whereas offline installation allows full customization.
Online installation requires a direct internet connection to download necessary components during setup, while offline installation does not.
Offline installation supports automatic updates and real-time support, whereas online installation does not.
Answer:
CExplanation:
The core architectural distinction between online and offline UiPath Automation Suite deployments centers on network perimeter connectivity and the mechanism used for artifact distribution. An online installation requires nodes to have outbound internet connectivity (directly or through an enterprise forward proxy) to dynamically download container images, OS packages, and Helm charts directly from UiPath cloud registries and official package repositories during deployment. Conversely, an offline (air-gapped) installation operates in isolated network environments without internet access. In this mode, deployment media must be staged manually: installation bundles are downloaded on an external internet-connected machine, transferred via secure jump-hosts, and hydrated into a local, in-cluster, or customer-managed OCI-compliant container registry. While both deployment types support identical product features and require similar hardware profiles, offline architectures require additional operational planning for package mirroring, local certificate authorities, and offline bundle synchronization. (Reference: UiPath Automation Suite Deployment Methods – Online vs. Offline Architectural Models).
===============
When setting up the Load Balancer for Automation Suite, which types of nodes must be included in the Node Pool?
Options:
Only specialized agent nodes only.
Only server nodes.
Server nodes and non-specialized agent nodes.
Only agent nodes but not Specialized agent nodes.
Answer:
CExplanation:
When provisioning the enterprise reverse-proxy load balancer for UiPath Automation Suite, the backend Node Pool must contain all server nodes and all non-specialized agent nodes. In an Automation Suite cluster, the ingress service mesh gateway (Istio) and application pods run distributed across the server nodes and standard worker (non-specialized agent) nodes. Including both node types in the load balancer pool ensures incoming traffic on ports 443 and 80 is balanced across all nodes hosting ingress controllers and application services. Conversely, specialized agent nodes—such as dedicated GPU nodes for Document Understanding and dedicated nodes for Automation Suite Robots—are tainted to prevent generic pod scheduling and must be excluded from the load balancer pool. Routing external web traffic to specialized nodes causes request drops because those nodes do not host ingress routing components. (Reference: UiPath Automation Suite Network and Load Balancing Configuration – Backend Pool Composition).
===============
When configuring storage for Automation Suite, which of the following is a critical consideration to ensure data persistence and availability in a production environment?
Options:
Limiting storage capacity to the bare minimum to save costs initially.
Redundancy and fault tolerance of the storage solution.
Choosing a storage solution that does not support backups to improve performance.
Using the fastest possible ephemeral disks.
Answer:
BExplanation:
In an enterprise production deployment of UiPath Automation Suite, data availability and durability take precedence over cost-reduction measures. A critical architectural consideration is ensuring that the underlying persistent storage solution offers built-in hardware and software redundancy and fault tolerance. Automation Suite relies heavily on stateful storage for SQL transactional logs, etcd consensus quorum state, distributed application volumes (via Longhorn or CSI drivers), and external object storage buckets. Production environments must utilize storage layers designed with enterprise RAID arrays, multi-zone volume replication, synchronous mirroring, and automated snapshot capabilities. Relying on ephemeral disks or non-redundant local disks introduces catastrophic single points of failure: a single hypervisor or physical disk crash would lead to unrecoverable cluster state divergence and data corruption. Resilient, fault-tolerant storage architectures ensure sustained service continuity during node or rack failures. (Reference: UiPath Automation Suite Infrastructure Design – High Availability Storage Considerations).
When using the wizard to generate a cluster configuration, which setting is chosen for a demo installation?
Options:
Single node with database provisioning
Multi-node with external object store
External OCI registry
Online with Kerberos
Answer:
AExplanation:
During the interactive cluster configuration wizard (`./install-uipath.sh` or configuration generation tools), selecting a "demo" or evaluation profile configures a single-node deployment with database provisioning. This demo installation profile is designed for rapid onboarding and functional validation without requiring an external infrastructure footprint. In this mode, the installer provisions lightweight, in-cluster SQL database instances directly on the single server node, eliminating the need to connect to an external enterprise SQL Server cluster or provision external cloud object stores. While this configuration minimizes prerequisite setup for demonstrations, it is unsupported for production workloads due to the lack of control-plane redundancy and stateful data isolation. Production profiles require multi-node configurations with external databases and resilient storage. (Reference: UiPath Automation Suite Installation Guide – Configuration Wizard Deployment Profiles).
===============
What is the role of the ./bin/uipathctl rke2 disk command during the installation process?
Options:
To install RPM packages for UiPath
To configure Kubernetes settings
To format and mount required disk partitions
To validate user credentials during setup
Answer:
CExplanation:
During Automation Suite installation on bare-metal or virtualized Linux machines, storage provisioning is handled via automated scripting utilities. The specific command `./bin/uipathctl rke2 disk` prepares, formats, and mounts the dedicated disk partitions and logical volumes mandated by UiPath's storage layout. Automation Suite enforces a strict multi-disk architecture separating the root operating system, cluster runtime binaries, etcd datastore, and persistent application data into distinct volumes formatted with supported file systems (ext4 or xfs). The `uipathctl rke2 disk` command automates creating physical volumes, volume groups, and logical volumes via LVM, formats them with required parameters, mounts them to their target mount paths (such as `/var/lib/rancher/rke2` and `/uipath`), and records them in `/etc/fstab`. Executing this command ensures reliable disk layout without the human error inherent in manual partitioning. (Reference: UiPath Automation Suite Linux Deployment Guide – Storage and Disk Automation).
===============
Can the secondary cluster be switched off when it is not being used in an Active-Passive deployment?
Options:
Yes, completely.
Yes, but only for maintenance.
Only partially.
No.
Answer:
AExplanation:
In an Active/Passive disaster recovery topology for UiPath Automation Suite, the secondary standby cluster can be switched off completely when not in use. In this deployment model, all live automation workloads, robot connections, and user web requests are directed to the primary cluster, while stateful database and object store data are replicated to the standby environment. Powering down the virtual machines or compute instances of the secondary cluster reduces cloud consumption costs and infrastructure spend during normal operations. However, shutting down the secondary cluster increases the platform Recovery Time Objective (RTO) during a disaster, as administrators must power on nodes, verify control-plane quorum, and run health validation scripts before redirecting traffic. Organizations balance operational cost savings against target RTO requirements when determining standby cluster power states. (Reference: UiPath Automation Suite Disaster Recovery Guide – Active/Passive Operation Modes).
===============
Which uipathctl command generates the configurations required to install Automation Suite on AKS, EKS, or OpenShift?
Options:
uipathctl check
uipathctl prereq run
uipathctl install
uipathctl prereq create
Answer:
DExplanation:
Deploying UiPath Automation Suite on managed Kubernetes distributions (AKS, EKS, or Red Hat OpenShift) requires configuring external platform prerequisites, including relational databases in Microsoft SQL Server and container buckets in external object storage. The automated command utilized to generate these requisite external configurations and resources is uipathctl prereq create. When executed with the deployment manifest (uipathctl prereq create input.json --versions versions.json), the command checks the flags enabled in input.json and automatically provisions the required SQL databases and object-storage buckets. Conversely, uipathctl prereq run is strictly a read-only validation check that confirms prerequisites without provisioning them. The prereq create subcommand standardizes the preparation of the external infrastructure tier. (Reference: UiPath Automation Suite on Managed Kubernetes – Automated Prerequisite Provisioning).
===============
In a multi-node Automation Suite deployment, which component is generally hosted by server nodes?
Options:
Only UiPath products and shared components.
Automation Suite Robots only.
Specialized workloads like Task Mining analysis requiring GPU.
Kubernetes control plane services.
Answer:
DExplanation:
Server nodes in a multi-node Automation Suite cluster are designated primarily to host the Kubernetes control plane services. These core services include the etcd distributed datastore, the API server (`kube-apiserver`), the controller manager (`kube-controller-manager`), and the cluster scheduler (`kube-scheduler`). Working together, these control-plane components orchestrate the desired state of the cluster, manage consensus across nodes, schedule container pods, and handle cluster-wide control loops. While standard UiPath product microservices may also be co-located and scheduled across server nodes in environments with sufficient spare compute capacity, the server node's defining and primary architectural responsibility is providing high availability and stability for the underlying control plane. High-demand specialized workloads (such as GPU pipelines or Automation Suite Robots) are explicitly isolated onto dedicated agent nodes to avoid compromising control-plane performance. (Reference: UiPath Automation Suite Multi-Node Architecture Guide – Server Node Specifications).
===============
In a Production environment using a mix of server and agent nodes, what is the primary risk if two server nodes are lost?
Options:
Data loss may occur, making it difficult to rebuild without backups.
There will be no impact.
All nodes will stop functioning.
The cluster will be unavailable.
Answer:
DExplanation:
In an Automation Suite production environment, server nodes host the Kubernetes control plane and run the distributed etcd datastore. Maintaining a functional cluster requires an active etcd quorum, which follows the Raft consensus algorithm where a strict majority of voting members ($(N/2) + 1$) must remain online and communicating. In a standard three-server HA architecture, quorum requires at least two functional server nodes. If two server nodes fail simultaneously, only one server remains, breaking quorum and causing the control plane to transition into a read-only or completely halted state. Consequently, the entire cluster becomes unavailable: API requests fail, pod scheduling halts, and the cluster cannot reconcile state. While agent nodes may continue running existing compute tasks temporarily, losing control-plane consensus renders the cluster non-operational until quorum is restored. (Reference: UiPath Automation Suite High Availability Design – Control Plane Quorum and Failure Scenarios).
===============
Which of the following represents a valid sequence for a multi-node installation?
Options:
Configure disks -- > Generate cluster config -- > Install infrastructure
Install RPM packages -- > Configure disks -- > Join agent nodes
Access servers -- > Join server nodes -- > Validate prerequisites
Install Fabric -- > Configure registry -- > Prepare servers
Answer:
AExplanation:
Deploying a multi-node UiPath Automation Suite cluster on Linux requires following a structured installation sequence to maintain cluster stability. The correct sequence begins with configuring disks, followed by generating the cluster configuration, and then installing the infrastructure. Disk configuration formats raw block storage into required partitions and mounts (e.g., `/uipath`, etcd). Next, the deployment engineer generates `cluster_config.json`, defining FQDNs, installation modes (online/offline), node assignments, and credentials. Once the storage and configuration files are prepared, the installer initializes the RKE2 Kubernetes control-plane infrastructure. Attempting to install infrastructure before partitioning disks or declaring configuration files will cause the installation scripts to abort during prerequisite checks. (Reference: UiPath Automation Suite Multi-Node Installation Lifecycle – Execution Order).
===============
Which command can you run to check the availability of the nodes?
Options:
kubectl get nodes
kubectl list nodes
kubectl verify nodes
kubectl check nodes
Answer:
AExplanation:
Within the underlying Kubernetes environment of UiPath Automation Suite, standard Kubernetes administrative utilities are leveraged to inspect cluster infrastructure health. The standard, authoritative CLI command used to evaluate the operational availability and status of cluster machines is `kubectl get nodes`. Executing this command queries the `kube-apiserver` and returns a tabular output listing all registered server, agent, and specialized agent nodes along with their current status, roles, age, and Kubernetes version. The primary health metric displayed in this view is the `STATUS` column, where a healthy machine actively heartbeating to the control plane displays the `Ready` condition. If a node suffers from network partitions, runtime engine failures, or kubelet crashes, the status transitions to `NotReady` or `SchedulingDisabled`. Alternative verbs such as `list`, `verify`, or `check` are invalid subcommands in the `kubectl` CLI grammar and return command syntax errors. (Reference: UiPath Automation Suite Troubleshooting and Node Operations – Node Health Verification).
===============
Automation Suite Multi Node is deployed in your environment. The FQDN of the primary server node is used for joining nodes to the cluster. What must be done if the primary server is down or has been deleted?
Options:
Remap the FQDN of the primary server to a different machine.
Reconfigure the backend pool.
Close the Temporary Registry Pool.
Restart the load balancer.
Answer:
AExplanation:
In a multi-node Automation Suite deployment, joining additional server or agent nodes to an active cluster requires workers to communicate with an active control-plane registration endpoint using the cluster join token and endpoint FQDN. If the primary server node that originally anchored this FQDN suffers an unrecoverable hardware failure or is permanently decommissioned, incoming node join requests will fail to establish connection. To restore cluster join operations, administrators must update internal DNS records or load balancer mappings to remap the primary server FQDN to another healthy, available server node within the cluster. Because all surviving server nodes host synchronized replicas of the control-plane API and registration services, remapping the FQDN directs joining nodes to a functional endpoint, allowing worker addition routines to complete without rebuilding the cluster. (Reference: UiPath Automation Suite Node Administration – Node Join Operations and Endpoint Remapping).
===============
What defines an agent node in the Automation Suite Platform context?
Options:
An agent node can host any of the UiPath products, shared components, or special workloads.
An agent node is responsible for running the UiPath products and shared components only.
An agent node runs special workloads like Task Mining analysis, Document Understanding pipelines that require GPU capability, or Automation Suite Robots.
An agent node hosts cluster management services.
Answer:
BExplanation:
In the Automation Suite architecture, worker instances are segmented into standard agent nodes and specialized agent nodes. A standard agent node is architected specifically to run UiPath core products (such as Orchestrator, Identity Server, and Data Service) and common shared components (like RabbitMQ, Redis, or Elasticsearch). Agent nodes do not host Kubernetes control-plane components (such as etcd, kube-apiserver, or kube-controller-manager), which reside strictly on server nodes. Furthermore, standard agent nodes are distinct from specialized agent nodes, which are provisioned with dedicated hardware profiles (e.g., NVIDIA GPUs or dedicated execution pools) and configured with Kubernetes taints and tolerations to host isolated, compute-intensive workloads such as Document Understanding ML training, Task Mining, and Automation Suite Robots. Maintaining this functional separation protects foundational business applications from resource starvation caused by heavy background data extraction or robot execution. (Reference: UiPath Automation Suite Architecture Overview – Node Roles and Workload Scheduling).
===============
Which AllowedMethods parameters must be configured when creating the CORS policy for the external object store?
Options:
GET, POST, DELETE
POST, DELETE, OPTIONS, HEAD
POST, GET, HEAD, DELETE, OPTIONS
GET, POST, DELETE, HEAD, PUT
Answer:
DExplanation:
When configuring an external S3-compatible or Azure Blob object store for UiPath Automation Suite, setting up an accurate Cross-Origin Resource Sharing (CORS) policy is mandatory to facilitate secure, direct browser-to-storage and service-to-storage communication. The documented CORS configuration explicitly requires the AllowedMethods parameters to include `GET`, `POST`, `DELETE`, `HEAD`, and `PUT`. These methods correspond directly to essential storage actions executed across the suite's microservices. Specifically, `PUT` and `POST` enable direct multi-part uploads of large automation packages, execution media, and Document Understanding datasets; `GET` enables retrieval of packages and artifacts; `HEAD` allows the service endpoints to verify object presence and metadata headers without downloading payloads; and `DELETE` permits lifecycle cleanup routines to remove deprecated artifacts. Excluding any of these five methods—most notably `PUT` or `HEAD`—results in HTTP 403 Forbidden errors during execution artifact publishing or client downloads in products such as Orchestrator, AI Center, and Data Service. (Reference: UiPath Automation Suite Infrastructure Pre-requisites – Object Store Configuration and CORS Policy Rules).
===============
In the context of Automation Suite Platform, how is a server node defined?
Options:
A server node runs the UiPath products and shared components only.
A server node hosts cluster management services that perform important cluster operations, such as workload orchestration, cluster state management, load balance incoming requests, etc.
A server node runs special workloads like Task Mining analysis, Document Understanding pipelines that require GPU capability, Automation Suite Robots, etc.
A server node can host any of the UiPath products, shared components, or special workloads.
Answer:
BExplanation:
Within the UiPath Automation Suite architecture, a server node is defined as a host that provides the Kubernetes control plane services responsible for cluster management and core operational functions. These essential services include cluster state management via the distributed etcd datastore, API request validation through the `kube-apiserver`, workload scheduling via `kube-scheduler`, controller reconciliation loops via `kube-controller-manager`, and request distribution to platform microservices. In environments where compute resources permit, server nodes may also host certain UiPath product pods and shared platform components; however, this capacity sharing does not alter their primary architectural definition. Server nodes are distinguished from agent nodes (which focus on running business products) and specialized agent nodes (which are isolated for GPU workloads and Automation Suite Robots). Preserving the performance and quorum of server nodes is vital for platform reliability. (Reference: UiPath Automation Suite Architecture Overview – Server Node Capabilities and Responsibilities).
===============
Which command correctly performs an in-place upgrade of Kubernetes and the other infrastructure components?
Options:
./bin/uipathctl rke2 upgrade cluster_config.json --versions versions/helm-charts.json
./install-uipath.sh --upgrade -i ./cluster_config.json -o ./output.json -k --accept-license-agreement
./bin/uipathctl manifest apply cluster_config.json --versions versions/helm-charts.json
./configureUiPathAS.sh --upgrade -i ./cluster_config.json -o ./output.json -j server --accept-license-agreement
Answer:
AExplanation:
When executing an in-place upgrade on an Automation Suite cluster on Linux, the upgrade workflow separates the infrastructure layer from the application service layer. Upgrading the underlying Kubernetes distribution (RKE2), container runtime, and foundational infrastructure charts requires executing `./bin/uipathctl rke2 upgrade cluster_config.json --versions versions/helm-charts.json`. This command uses the target version definitions specified in `versions/helm-charts.json` and evaluates the existing parameters inside `cluster_config.json` to sequentially update the control plane, cordoning and draining nodes in a rolling fashion to preserve control-plane quorum. Legacy script parameters (such as `install-uipath.sh --upgrade` or `configureUiPathAS.sh`) were deprecated in favor of modern `uipathctl` subcommands, which orchestrate both infrastructure engine rollouts and Helm management. Once the infrastructure upgrade completes successfully, platform engineers proceed with upgrading the core application services. (Reference: UiPath Automation Suite Upgrade Procedures – Infrastructure and Kubernetes Upgrade Lifecycle).
===============
What type of storage is necessary to support a successful migration between Automation Suite clusters?
Options:
Ephemeral Storage.
Persistent volume.
An external objectstore.
External database.
Answer:
CExplanation:
Migrating stateful data and persistent volumes between distinct Automation Suite clusters (such as parallel cluster migrations or side-by-side upgrades) requires an external objectstore. The source cluster cannot directly stream local persistent volume data or internal container blocks to the target cluster across private software-defined networks. Instead, the migration process uses an external S3-compatible or Azure Blob storage service as an intermediate repository. Persistent volume contents, package feeds, and state snapshots from the source cluster are exported to this external object store. The target Automation Suite cluster then accesses this shared external objectstore to retrieve the state data, initialize its own persistent volumes, and restore application state. Without an external object store, cross-cluster migration cannot be completed. (Reference: UiPath Automation Suite Cluster Migration and Disaster Recovery Procedures).
===============
What minimum hardware specifications are recommended for a Microsoft SQL Server that hosts Automation Suite databases?
Options:
4 vCPU, 16 GB RAM, 128 GB SSD
6 vCPU, 24 GB RAM, 200 GB SSD
8 vCPU, 32 GB RAM, 256 GB SSD
10 vCPU, 40 GB RAM, 512 GB SSD
Answer:
CExplanation:
External relational databases play a critical role in state persistence for UiPath Automation Suite. The official infrastructure specifications recommend a hardware baseline of 8 (v-)CPUs, 32 GB of RAM, and a 256 GB enterprise SSD for a dedicated Microsoft SQL Server hosting platform databases. UiPath Automation Suite consolidates relational data for multiple services—including Orchestrator, Identity Server, Action Center, Data Service, and Test Manager—onto this SQL database engine. This hardware sizing ensures the database engine can maintain adequate buffer cache memory, execute complex transactional queries, manage parallel index maintenance, and provide sustained I/O throughput with low latency. Sizing below these specifications can lead to high database CPU utilization, memory pressure, connection pool exhaustion, and performance bottlenecks under peak automation loads. (Reference: UiPath Automation Suite Database Requirements – External Microsoft SQL Server Sizing).
===============
Which statement correctly explains the process and constraints for adding nodes to an Automation Suite deployment?
Options:
Adding nodes is supported in both deployment profiles, but adding nodes to a single-node environment does not convert it into an HA-ready setup.
Adding nodes to a single-node evaluation profile will automatically convert it to a multi-node HA-ready production environment.
To add a new node, you must reconfigure the deployment profile and regenerate a new cluster configuration from scratch.
You can only add agent nodes post-installation; server nodes must be defined before the initial deployment.
Answer:
AExplanation:
UiPath Automation Suite supports adding both server and agent nodes post-installation to scale compute and memory capacity across either single-node evaluation or multi-node production deployment profiles. However, adding nodes to a single-node evaluation cluster does not convert it into a multi-node High Availability (HA)-ready production deployment. Converting a single-node environment into a certified HA-ready setup requires specific architectural changes: migrating in-cluster databases to external SQL instances, configuring external object stores, provisioning a zone-redundant load balancer, deploying an odd number of server nodes (minimum three) to establish etcd quorum, and reconfiguring storage replication. Adding nodes to a single-node cluster merely provides additional compute capacity for specialized workloads (such as attaching a GPU agent node) while leaving the single control plane as a single point of failure. (Reference: UiPath Automation Suite Administration – Cluster Scaling and Node Addition Constraints).
When configuring dedicated nodes for Automation Suite Robots, which labels must be added together with the appropriate taint to enable correct pod scheduling?
Options:
uipath.robot=true and uipath.daemon=true
serverless.robot=true and serverless.daemon=true
robot.pool=dedicated and daemon.enabled=true
robot.node=enabled and robot.daemon=true
Answer:
BExplanation:
Automation Suite Robots (serverless cross-platform robot execution containers) run on dedicated agent worker nodes to ensure isolation from shared platform microservices. To schedule robot execution pods accurately and run the supporting node daemon, administrators must apply specific Kubernetes labels and taints to the designated worker nodes. While the dedicated node is tainted with `serverless.robot=present:NoSchedule`, applying this taint alone is insufficient for pod admission. UiPath requires explicitly tagging the node with two mandatory labels: `serverless.robot=true` and `serverless.daemon=true` (e.g., using `kubectl label node < node-name > serverless.robot=true serverless.daemon=true` or OpenShift's `oc label node ...`). The internal Kubernetes scheduler evaluates these exact node selectors alongside corresponding tolerations defined in the Automation Suite Robots helm deployments. Omitting these labels prevents the robot executor pods and required daemon pods from binding to the node, resulting in unschedulable pod states. (Reference: UiPath Automation Suite Documentation – Kubernetes Cluster and Nodes, Automation Suite Robots Setup).
===============
For a complete product selection, what minimum data-disk capacity is required for both single-node and multi-node deployments?
Options:
256 GiB SSD
512 GiB SSD
1 TB SSD
2 TB SSD
Answer:
DExplanation:
UiPath Automation Suite categorizes hardware and storage baseline requirements based on product selection profiles: Basic (or Minimal) vs. Complete. When deploying the "Complete" product selection—which encompasses data-heavy services such as Process Mining, Task Mining, AI Center, and Document Understanding alongside core platform components—the required data disk capacity on server nodes is a minimum of a 2 TiB (or 2 TB) SSD with a sustained performance profile of at least 1100 IOPS. This requirement applies to both single-node evaluation and multi-node HA-ready production profiles. The 512 GiB SSD disk size is only permitted for a restricted "Basic" profile deployment containing minimal services (such as standalone Orchestrator, Action Center, and Identity Server). Provisioning less than 2 TB for a complete installation leads to disk exhaustion and cluster failure as services generate persistent state. (Reference: UiPath Automation Suite Sizing Guide – Complete Product Selection Storage Requirements).
===============
Why is latency important when designing an Active/Active model for Automation Suite?
Options:
It reduces the complexity of configuration.
It impacts the cost of deployment.
It reduces the risk of data loss during an outage.
It improves user satisfaction.
Answer:
CExplanation:
In an Active/Active multi-site deployment of UiPath Automation Suite, both primary and secondary geographic clusters actively process production workloads, accept API requests, and handle automation state changes simultaneously. This design relies on continuous, synchronous or near-synchronous data replication across distributed transactional components—specifically Microsoft SQL Server Always On Availability Groups, distributed Redis caching layers, and external object stores. Ultra-low network round-trip time (RTT latency strictly below 10 ms) is a critical requirement because it reduces the replication lag to near zero. Minimal latency directly minimizes the Recovery Point Objective (RPO) and significantly mitigates the risk of transactional data loss during an unannounced data center failover or network partition. High network latency causes replication queue backlog, distributed lock starvation, database commit stalls, and split-brain scenarios, exposing inflight business transactions to unrecoverable data loss. (Reference: UiPath Automation Suite High Availability and Disaster Recovery – Active/Active Design Principles).
===============
Which of the following is a required configuration step when setting up the environment for use with a proxy server?
Options:
Use a self-signed certificate for HTTPS proxy
Disable http_proxy and https_proxy variables
Add proxy settings to cluster_config.json for both online and offline installation types
Adding proxy settings to ./etc/environment file
Answer:
DExplanation:
When deploying UiPath Automation Suite within enterprise networks requiring outbound web traffic to traverse a forward proxy, proxy environment variables must be declared system-wide across every cluster node. Administrators must configure `/etc/environment` (or `/etc/profile.d/` proxy scripts) to export `http_proxy`, `https_proxy`, and `no_proxy` settings. Configuring `/etc/environment` ensures system daemons, container runtimes, RKE2 services, and installation scripts automatically inherit proxy parameters. The `no_proxy` variable must explicitly include the cluster CIDR blocks, service CIDRs, local machine hostnames, and `.internal` domains to prevent internal node-to-node communication from routing through the proxy. Self-signed proxy certificates for HTTPS inspection are strictly unsupported unless officially signed by an enterprise CA integrated into the Linux trust store. (Reference: UiPath Automation Suite Network Configuration – Proxy Configuration and Linux Environment Settings).
===============
Following a disaster recovery, which essential components must be included in the cluster_config.json file when attempting to restore an online deployment from backup?
Options:
fixed_rke_addess,fqdn,rke_token,cluster_profile,external_object_storage,install_type;
fixed_rke_addess,fqdn,rke_token,apps_deployment,profile,external_object_storage,install_type;
fixed_rke_addess,fqdn,rke_token,profile,external_storage,install_type;
fixed_rke_addess,fqdn,rke_token,profile,external_object_storage,install_type;
Answer:
DExplanation:
Restoring an online UiPath Automation Suite cluster from a backup after a disaster recovery event requires a minimal, valid `cluster_config.json` manifest. The recovery process requires the following specific components in the configuration file: `fixed_rke_addess` (or `fixed_rke_address`), `fqdn`, `rke_token`, `profile`, `external_object_storage`, and `install_type`. Each parameter supports a specific aspect of cluster reconstruction: `fixed_rke_address` establishes the primary control-plane endpoint, `fqdn` defines the platform domain, `rke_token` supplies the node join security secret, `profile` designates the sizing tier, `external_object_storage` connects to persistent buckets, and `install_type` specifies an online deployment. Omitting any of these key-value pairs or using invalid property names will cause the restoration toolchain to fail during initial manifest validation. (Reference: UiPath Automation Suite Disaster Recovery Guide – Cluster Restore Configuration Parameters).
===============
Which tool is used in the single-tenant migration process to move Orchestrator data to Automation Suite?
Options:
There is no UiPath internal tool used for this migration process.
Automation Cloud Migration Tool.
UiPath Orchestrator Tenant Migration Tool.
Orchestrator Manager Tool.
Answer:
BExplanation:
When executing a single-tenant data migration from an existing standalone Windows Orchestrator instance to a multi-tenant Automation Suite cluster, UiPath specifies the use of the Automation Cloud Migration Tool. In single-tenant migration workflows, performing a direct database-level backup and restore is not feasible because the target Automation Suite Orchestrator database operates in a shared multi-tenant schema with existing system tables and platform services. The Automation Cloud Migration Tool utilizes public and administrative REST APIs to export tenant-specific entities—including folder hierarchies, assets, environments, packages, process configurations, and user assignments—from the standalone source instance and hydrate them directly into the target Automation Suite tenant. This ensures safe data migration without risking data collisions or corrupting other tenants within the cluster. (Reference: UiPath Automation Suite Migration Guide – Single-Tenant Migration Approaches).
===============
What root-volume capacity is required for both EKS and AKS agent (worker) nodes?
Options:
minimum 20 GB
minimum 50 GB
minimum 150 GB
minimum 256 GB
Answer:
DExplanation:
When preparing worker agent node pools on managed public cloud Kubernetes engines—specifically Amazon Elastic Kubernetes Service (EKS) and Azure Kubernetes Service (AKS)—UiPath specifies an OS root-volume capacity of at least 256 GB. In managed Kubernetes environments, container base images, ephemeral emptyDir volumes, runtime log buffers, and local Docker/containerd build caches are placed directly on the root volume filesystem. Given the large footprints of UiPath microservices, Machine Learning container layers, and platform monitoring daemons, standard cloud default root disks (such as 30 GB or 100 GB) risk triggering node disk pressure conditions. Disk pressure causes the kubelet to initiate eviction procedures, terminating pods and degrading cluster availability. Sizing agent root volumes to a minimum of 256 GB with enterprise SSD storage provides necessary operational headroom for complex workloads. (Reference: UiPath Automation Suite on AKS/EKS – Agent Node Pool Sizing and Disk Requirements).
===============
Which Automation Suite component commonly uses an S3-compatible object store or Azure Blob storage to store large artifacts, packages, or datasets?
Options:
The local browser cache of a user accessing the suite.
Core services like the Orchestrator, AI Center, or Data Service for their operational data or user-generated content.
The command-line interface used for installation.
The Kubernetes master node’s operating system.
Answer:
BExplanation:
UiPath Automation Suite leverages a distributed architecture that decouples compute workloads from persistent binary data storage. Core platform services—including Orchestrator, AI Center, and Data Service—rely on an external or in-cluster S3-compatible object store (such as AWS S3, Azure Blob Storage, or Ceph Object Storage) to store heavy artifacts, unstructured packages, and user-generated assets. Orchestrator uses the object store for published NuGet automation packages, workflow execution media, and queue attachments; AI Center persists trained machine learning models, training datasets, and inference pipelines; and Data Service stores entity file attachments and binary payloads. Relational databases (SQL Server) are reserved strictly for transactional state and structured metadata to maintain query performance. Offloading large, unstructured payloads to object storage provides scalability, high durability, and simplifies cluster-wide snapshot backups and multi-region disaster recovery replication. (Reference: UiPath Automation Suite Storage Architecture – Object Storage Integrations).
===============
When setting up an external OCI-compliant registry for Automation Suite, what information is necessary for the suite to connect to it and pull images?
Options:
The Fully Qualified Domain Name (FQDN) or IP address of the registry server.
The number of CPU cores on the registry server.
The physical location of the registry server.
The brand of the storage used by the registry.
Answer:
AExplanation:
To enable an Automation Suite cluster to pull container images from an external OCI-compliant container registry, the configuration must declare the network endpoint: the Fully Qualified Domain Name (FQDN) or IP address of the registry server. During cluster bootstrapping and subsequent pod provisioning, the containerd runtime and Kubernetes image pull secrets resolve this FQDN or IP over HTTPS (or HTTP via insecure registry flags) to authenticate and pull container layers. Infrastructure details such as CPU core counts, datacenter locations, or backend storage vendors are abstracted by the registry's OCI API and are irrelevant to client connection configurations. Supplying a valid, network-accessible FQDN or IP address—along with required authentication credentials and CA trust chains—ensures nodes can download container images during installation and pod scheduling. (Reference: UiPath Automation Suite Pre-requisites – OCI Registry Connection Parameters).
===============
Which uipathctl command lets you upload configuration files to Orchestrator?
Options:
uipathctl orchestrator config upload
uipathctl config orchestrator upload
uipathctl config orchestrator apply-config
uipathctl apply orchestrator-config
Answer:
BExplanation:
The platform CLI utility `uipathctl` exposes dedicated administrative syntax for manipulating service-level storage and parameters. To push configuration-related files, custom extensions, or settings into Orchestrator storage, the documented command syntax is `uipathctl config orchestrator upload`. Within containerized Automation Suite deployments, Orchestrator instances rely on centralized object stores or backend database stores rather than localized node file systems for state and configuration persistence. The `uipathctl config orchestrator upload` command securely interacts with the platform's internal APIs and storage abstractions to stream configuration files directly to the designated Orchestrator destination bucket or config secret store. Attempting to use inverted command verbs, such as placing the target service prior to the subcommand, results in command parsing syntax errors within the CLI. Mastery of `uipathctl` CLI sub-trees is mandatory for infrastructure engineers responsible for cluster operations and service lifecycle management. (Reference: UiPath Automation Suite Administration – uipathctl Command-Line Reference Guide).
===============
For an Automation Suite deployment on Linux using in-cluster storage, which deployment configuration is recommended when the goal is resilience against data loss?
Options:
Specialized agent nodes only.
A mix of server and agent nodes.
All server nodes.
All agent nodes.
Answer:
CExplanation:
When deploying UiPath Automation Suite on Linux utilizing built-in in-cluster persistent storage (Longhorn/Ceph) rather than an external enterprise SAN or cloud-managed block store, maximizing resilience against data loss is achieved using an all-server-node deployment configuration. In an in-cluster storage architecture, persistent volumes are replicated across the underlying cluster nodes to ensure data durability. When all nodes are designated as server nodes, every node participates in both control-plane consensus and storage volume replication. This symmetric architecture allows volume replicas to remain distributed across all machines. If a node fails, the surviving server nodes retain storage replicas and continue servicing I/O operations without breaking control-plane quorum. In contrast, in mixed configurations, agent node failures can compromise storage replicas without providing the redundancy benefits of an all-server topology. (Reference: UiPath Automation Suite Storage Architecture – In-Cluster Storage Resilience Guidelines).
===============
Which of the following statements is accurate when deploying the Orchestrator service in Automation Suite?
Options:
Only SQL server Enterprise editions are supported
Requires SQL Server version 2019 or higher for optimal performance
Requires a dedicated Microsoft SQL Server 2016, 2017, 2019, and 2022 Standard and Enterprise editions
Orchestrator does not require an SQL server because it is deployed as a service as part of Automation Suite
Answer:
BExplanation:
When provisioning the Orchestrator service within UiPath Automation Suite, external Microsoft SQL Server 2019 or higher is required for optimal performance and full feature compatibility. Orchestrator acts as the central transaction hub for job scheduling, queue management, asset security, and robot execution logs, generating high transactional volumes. The modern database schemas utilized by containerized Orchestrator leverage SQL Server 2019 engine enhancements, including optimized row-level locking, intelligent query processing, and native JSON functions. UiPath supports both Microsoft SQL Server Standard and Enterprise editions, but requires version 2019 or newer to ensure performance and prevent schema compatibility issues. Orchestrator cannot operate without an external SQL Server, but it does not mandate a physically dedicated SQL instance, allowing it to share database instances with other compatible platform services. (Reference: UiPath Automation Suite Database Requirements – Orchestrator Database Prerequisites).
===============