Limited-Time Offer: Enjoy 50% Savings! Coupon code: 50OFF Use it at checkout
Skip to content

Free UiPath Infrastructure Engineer Professional - Automation Suite UiPath-IEPASv1 Exam Questions

Page: 1 / 12 Total 118 questions

Want more questions? Get Premium Access.

Question 1

Which processors are supported for deploying UiPath Automation Suite on Linux?

Correct Answer: B. Both AMD and Intel processors are supported if architecture requirements are met.
Explanation:

UiPath Automation Suite on Linux explicitly supports both AMD and Intel 64-bit processors, provided the systems meet core architecture and clock speed requirements. The containerized software suite is compiled for x86_64/AMD64 instruction set architectures. Both enterprise Intel Xeon and AMD EPYC families provide the microarchitecture capabilities, hardware virtualization features, and vector instruction support required to execute Automation Suite container workloads. ARM-based processor platforms, including AWS Graviton, Ampere Altra, and Apple Silicon, are strictly unsupported due to underlying architectural incompatibilities with compiled product binaries and container base layers. When deploying across virtual machines or physical hosts, engineers must verify that CPU features are exposed transparently by the hypervisor and that minimum aggregate cluster compute thresholds (e.g., 96 cores across multi-node production clusters) are met across Intel or AMD hardware pools. (Reference: UiPath Automation Suite Infrastructure Requirements -- CPU Architecture Support).

Question 2

Which of the following is a consideration for implementing a backup mechanism in Automation Suite?

Correct Answer: A. The NFS server must be reachable from all the cluster nodes.
Explanation:

When configuring scheduled snapshot backups on an Automation Suite cluster on Linux, UiPath utilizes an external Network File System (NFS) share as the primary target repository for persistent volume snapshots and platform state files. A mandatory architectural prerequisite for this backup mechanism is that the external NFS server must be network-reachable from all cluster nodes (both server and agent nodes). Because container workloads and backup agents (e.g., Velero or local snapshot daemon pods) run distributed across any node within the Kubernetes cluster, every single node must be able to mount the NFS target storage. If firewall barriers, routing policies, or subnets restrict access to only a subset of nodes, snapshot operations will fail intermittently depending on which node hosts the backup pod. The NFS server should be provisioned outside the cluster to ensure backup persistence in the event of total cluster hardware loss. (Reference: UiPath Automation Suite Backup and Disaster Recovery -- Backup Storage Prerequisites).

Question 3

When configuring dedicated nodes for Automation Suite Robots, which labels must be added together with the appropriate taint to enable correct pod scheduling?

Correct Answer: B. serverless.robot=true and serverless.daemon=true
Explanation:

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 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).

Question 4

Which configuration setting allows ArgoCD to operate in cluster-wide mode?

Correct Answer: A. ARGOCD_CLUSTER_CONFIG_NAMESPACES:
Explanation:

ArgoCD serves as the internal GitOps declarative engine managing product lifecycle, synchronization, and Helm releases within Automation Suite. By default, ArgoCD operates within constrained namespace parameters. To configure ArgoCD with cluster-wide management permissions---allowing it to reconcile cluster-scoped resources, Custom Resource Definitions (CRDs), and manage workloads across all platform namespaces---the environment variable ARGOCD_CLUSTER_CONFIG_NAMESPACES must be declared. Setting ARGOCD_CLUSTER_CONFIG_NAMESPACES: specifies that the ArgoCD controller instance running in the argocd namespace possesses authorization to manage cluster-level resources. This configuration grants the declarative engine the authority required to orchestrate ingress definitions, role-based access controls, and multi-namespace deployments across the platform. (Reference: UiPath Automation Suite GitOps Architecture -- ArgoCD Configuration and Cluster Permissions).

Question 5

Which of the following requirements must be satisfied before removing a node from an Automation Suite cluster?

Correct Answer: B. The cluster must be a multi-node HA-ready production setup with a healthy state and at least three server nodes remaining.
Explanation:

Decommissioning or removing a node from an active Automation Suite cluster requires meeting strict operational safeguards to protect platform availability. First, node removal is supported only on multi-node High Availability (HA)-ready production clusters; it is unsupported on single-node evaluation setups. Second, the cluster must be in a confirmed healthy state prior to removal. Third, if a server node is being removed, the remaining cluster must retain at least three healthy server nodes. Automation Suite utilizes an etcd-based distributed control plane that enforces Raft consensus, which requires an odd number of server nodes (minimum of three) to maintain quorum and prevent split-brain conditions. Prematurely shutting down nodes manually prior to cluster deregistration risks breaking quorum. Administrators must execute node draining and removal through documented CLI tools to rebalance the cluster cleanly. (Reference: UiPath Automation Suite Node Operations -- Node Removal and Cluster Scaling Rules).

Question 6

What does a single-node evaluation deployment involve within the Automation Suite?

Correct Answer: B. Setting up a single-server node for evaluation purposes and demo scenarios.
Explanation:

A single-node evaluation deployment of UiPath Automation Suite consists of provisioning a single server node that hosts the Kubernetes control plane alongside platform microservices for evaluation, demonstration, and proof-of-concept testing. This deployment profile does not necessarily mean that every workload runs on a single physical machine; specialized workloads (such as GPU-dependent Document Understanding pipelines or Task Mining analysis) still require dedicated specialized agent nodes to be attached if those specific capabilities are enabled. However, from a control-plane perspective, it uses a single server node without the redundancy required for production. Consequently, this configuration does not provide high availability: if the single server node encounters a hardware or operating system failure, the entire platform becomes unavailable. Production environments require multi-node deployments with at least three server nodes to maintain control-plane quorum. (Reference: UiPath Automation Suite Architecture Overview -- Evaluation Profiles).

Question 7

Which disk size is correct for the etcd disk during configuration?

Correct Answer: A. 16 GB
Explanation:

When provisioning storage volumes for server nodes running Automation Suite on Linux (RKE2), UiPath mandates an isolated, dedicated block storage disk sized at 16 GB for the etcd datastore. The etcd component functions as the distributed key-value store holding the complete state, secrets, and metadata for the Kubernetes cluster. Because etcd operations are highly sensitive to write latency, separating etcd onto a dedicated 16 GB solid-state disk (SSD) delivering a sustained performance baseline of at least 240 IOPS prevents write starvation caused by generic application container I/O. Larger disk allocations---such as 256 GB or 512 GB---are designated for the root operating system, cluster runtime binaries, or application persistent data volumes. Provisioning a dedicated 16 GB SSD for etcd ensures predictable disk commit performance, protecting the control plane from consensus timeouts and cluster partition issues. (Reference: UiPath Automation Suite Hardware and Storage Requirements -- Server Node Storage Layout).

Question 8

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?

Correct Answer: A. The Fully Qualified Domain Name (FQDN) or IP address of the registry server.
Explanation:

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).

Question 9

What minimum hardware specifications are recommended for a Microsoft SQL Server that hosts Automation Suite databases?

Correct Answer: C. 8 vCPU, 32 GB RAM, 256 GB SSD
Explanation:

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).

Question 10

When setting up the Load Balancer for Automation Suite, which types of nodes must be included in the Node Pool?

Correct Answer: C. Server nodes and non-specialized agent nodes.
Explanation:

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).