- Home
- UiPath
- UiPath Certified Professional - Infrastructure Engineer
- UiPath-IEPASv1
- UiPath-IEPASv1 - UiPath Certified Professional Infrastructure Engineer Professional - Automation Suite
UiPath UiPath-IEPASv1 UiPath Certified Professional Infrastructure Engineer Professional - Automation Suite Exam Practice Test
UiPath Certified Professional Infrastructure Engineer Professional - Automation Suite Questions and Answers
What is the main purpose of setting up a temporary Docker registry for offline UiPath Automation Suite installations?
Options:
To provide continuous integration and deployment.
To enable real-time monitoring.
To store container images and deployment Helm charts.
To facilitate automated testing.
Answer:
CExplanation:
In an air-gapped or offline deployment scenario where cluster nodes lack outbound internet connectivity to public registries and UiPath repositories, a temporary Docker/OCI-compliant registry is provisioned to serve as the local distribution point for all deployment artifacts. Offline installation bundles (shipped as massive compressed tar archives) contain hundreds of microservice container images, foundational infrastructure binaries, and deployment Helm charts required across the entire platform lifecycle. During the initialization phase, the installer script hydrates this temporary registry with these assets. During cluster bring-up, RKE2 nodes and the local Helm engine pull required container layers and chart configurations directly from this endpoint over port 30070 or internal ingress ports without touching external endpoints. Once the permanent local container registry or in-cluster registry infrastructure is established and cluster services stabilize, the temporary registry can be decommissioned or repurposed. This staging mechanism guarantees reproducible, hermetic deployments in secured operational environments. (Reference: UiPath Automation Suite Offline Installation Guide – Registry Architecture).
===============
What is recommended if you encounter problems while running the Automation Suite installation command?
Options:
Contact customer support immediately without further action.
Rerun the command installation commands with all the arguments and flags.
Delete all existing files and start the process from scratch.
Modify the input.json file to bypass the error.
Answer:
BExplanation:
The installation automation bundled with UiPath Automation Suite (whether executed via shell scripts or the `uipathctl` CLI binary) is designed to be idempotent. If an intermittent infrastructure glitch, temporary DNS hiccup, or transient network timeout halts the deployment, the recommended initial course of action is to rerun the installation command including all the original arguments, configuration parameters, and flags. The installer checks the current progress against the cluster state, skips tasks and Helm releases that have already reached a completed status, and resumes reconciliation precisely from the point of failure. Rebuilding the entire operating system, purging local directories, or modifying configuration files arbitrarily is unnecessary and risks introducing configuration drift. If the idempotent re-execution consistently fails at the identical task, engineers then analyze the deployment logs generated in `/opt/UiPathAutomationSuite` to resolve the root cause. (Reference: UiPath Automation Suite Installation Guide – Error Handling and Retries).
===============
For a multi-site deployment, what is the FQDN of the primary cluster?
Options:
automationsuite-primary.mycompany.com
fqdn-secondary.mycompany.com
fqdn-primary.mycompany.com
automationsuite-secondary.mycompany.com
Answer:
AExplanation:
In multi-site Active/Passive or Active/Active disaster recovery architectures, UiPath Automation Suite requires distinct Fully Qualified Domain Names (FQDNs) for each participating cluster. In UiPath's multi-site configuration documentation and deployment manifests, the primary cluster's FQDN is defined following the standard format: `automationsuite-primary.mycompany.com`. The secondary site is configured with a corresponding secondary FQDN (such as `automationsuite-secondary.mycompany.com`). In active-passive setups, an enterprise DNS traffic manager or global server load balancer routes traffic to the primary FQDN while redirecting to the secondary FQDN during failover events. Providing distinct FQDNs for each site avoids hostname routing conflicts, ensures proper SSL certificate matching, and allows independent monitoring of each cluster. (Reference: UiPath Automation Suite Multi-Site Disaster Recovery Architecture Guide).
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 of the following statements is accurate when deploying the Insights service in Automation Suite?
Options:
Insights is only compatible with SQL Server 2019 and higher, regardless of the Automation Suite version.
Microsoft SQL Server 2016, 2017, 2019, and 2022 Standard and Enterprise editions are supported.
Insights service does not require a database hence SQL server is not required for Insights.
Insights requires a dedicated instance of SQL Server.
Answer:
AExplanation:
UiPath Insights provides business intelligence and analytics for automated workflows, relying on analytical database operations within Microsoft SQL Server. While core Automation Suite services support various SQL Server versions, the Insights database service specifically requires Microsoft SQL Server 2019 or newer (Standard or Enterprise edition). Insights depends on features introduced in modern database engines, including JSON parsing capabilities and clustered Columnstore indexing for analytical query performance. Older releases like SQL Server 2016 and 2017 do not meet these technical requirements and are unsupported for Insights. Insights does not require a dedicated physical SQL instance and can share an instance with other platform databases provided performance needs are met. (Reference: UiPath Automation Suite Database Requirements – Product-Specific SQL Matrix).
===============
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).
===============
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).
===============
When upgrading to a new Automation Suite version, in which situations is an additional license required?
Options:
No additional license is required during the Automation Suite upgrade.
An additional license is required only during side-by-side upgrade.
An additional license is required, independent of the upgrade method used.
An additional license is required when you perform a clean upgrade.
Answer:
AExplanation:
Upgrading UiPath Automation Suite to a newer version does not require purchasing or applying an additional platform license, regardless of whether the organization implements an in-place upgrade or a parallel (side-by-side) upgrade strategy. In an in-place upgrade, existing platform license files remain active and bind continuously to the upgraded cluster services. In a side-by-side upgrade, UiPath licensing terms grant a temporary migration allowance that permits the existing production license to be shared between the legacy source cluster and the new target cluster during the data migration, validation, and cutover windows. Once verification succeeds and traffic is redirected to the target cluster, the legacy environment is decommissioned, ensuring the organization remains compliant within its licensed node and service capacities. UiPath platform licensing validates entitlement through host and tenant allocations rather than charging transitional fees for version upgrade procedures. (Reference: UiPath Automation Suite Upgrade Planning – Licensing and Entitlements).
===============
Which permission below is explicitly identified as unnecessary for the Automation Suite installer in an OpenShift environment?
Options:
cluster-admin privileges
Specific Security Context Constraints (SCCs)
permissions to create projects/namespaces
sudo or root access on the bastion machine
Answer:
DExplanation:
When installing UiPath Automation Suite on Red Hat OpenShift, the deployment CLI toolchain (`uipathctl`) communicates with the OpenShift cluster via the Kubernetes API server endpoint. Consequently, the workstation or bastion host executing the installer does not require root or `sudo` administrative operating system privileges; the installer can be invoked by a standard user account on Linux, macOS, or Windows machines equipped with network access and valid OpenShift credentials. The deployment does, however, require Kubernetes-level privileges, including `cluster-admin` role bindings to register Custom Resource Definitions (CRDs), create target namespaces/projects, and manage workload constraints. UiPath microservices adhere to standard OpenShift security baselines, using the built-in `restricted-v2` Security Context Constraint (SCC) for workload execution. Eliminating the need for OS root access on bastion jump-hosts enforces the principle of least privilege in enterprise environments. (Reference: UiPath Automation Suite on Red Hat OpenShift – Installation Prerequisites and Access Permissions).
===============
In which location are Istio certificates stored, and what name are they found under?
Options:
In the istio-system namespace under the name istio-ingressgateway-certs
In the kube-system namespace under the name ingress-certs
In the kube-public namespace under the name tls-secret
In the default namespace under the name istio-tls-certs
Answer:
AExplanation:
In UiPath Automation Suite, external transport security and reverse-proxy ingress routing are managed by an Istio-based service mesh. The Istio Ingress Gateway handles incoming HTTPS connections directed to the platform Fully Qualified Domain Name (FQDN). To terminate TLS/SSL traffic, the ingress gateway controller reads the public certificate hierarchy and private key directly from a designated Kubernetes Secret. By default and per technical standards, this Secret is maintained within the `istio-system` namespace under the exact name `istio-ingressgateway-certs`. During post-installation certificate renewals or rotations, administrators replace or update this specific Secret to apply updated certificates across all edge endpoints without requiring downtime. Storing certificates outside `istio-system` or using non-standard naming prevents the ingress gateway pod from mounting the TLS secret volumes, causing ingress handshake terminations. (Reference: UiPath Automation Suite Infrastructure and Network Configuration – Ingress and Istio Certificate Management).
===============
Which file must you modify to enable or disable products in UiPath Automation Suite on AKS/EKS/OpenShift?
Options:
services_config.yaml
cluster_config.json
uipath_settings.json
input.json
Answer:
DExplanation:
In managed Kubernetes environments—specifically Azure Kubernetes Service (AKS), Amazon Elastic Kubernetes Service (EKS), and Red Hat OpenShift—UiPath uses a declarative configuration blueprint centered around the `input.json` file. This manifest dictates the entire desired state of the platform, including FQDN endpoints, database connection strings, external object store references, and boolean service enablement flags. When administrators need to enable or disable specific UiPath capabilities (such as AI Center, Process Mining, Document Understanding, or Test Manager), they update the corresponding service flag values in `input.json`. Once modified, the configuration is applied to the active cluster by invoking `uipathctl manifest apply input.json --versions versions.json`. This command calculates drift and orchestrates the deployment or removal of Helm releases and pods, ensuring the cluster reconciles with the state declared in `input.json`. (Reference: UiPath Automation Suite on Managed Kubernetes – Configuration and Service Lifecycle).
===============
In a multi-node HA-ready production deployment, is the number of agent nodes fixed or optional?
Options:
Fixed.
Determined by the number of server nodes.
Must be equal to the number of server nodes.
Optional and based on actual usage.
Answer:
DExplanation:
In a multi-node High Availability (HA)-ready production deployment of UiPath Automation Suite, the quantity of server nodes is strictly constrained to maintain control-plane consensus (requiring a minimum of three server nodes to preserve etcd quorum). Conversely, the number of agent nodes is entirely optional and dynamic, scaled up or down based on actual tenant workload, transaction volume, and active product enablement. A baseline multi-node cluster can technically host core product services across the server nodes if compute capacity permits, making dedicated agent nodes optional for initial bring-up. As platform adoption expands or resource-intensive capabilities (such as Document Understanding, Process Mining, or Automation Suite Robots) are enabled, organizations scale the cluster horizontally by attaching standard or specialized agent nodes according to consumption metrics. The architecture allows enterprise infrastructure architects to size worker capacity without being bound by rigid, fixed agent node quotas. (Reference: UiPath Automation Suite Sizing and Capacity Planning Guide – Multi-Node Sizing Models).
===============
What is the purpose of enabling net.bridge.bridge-nf-call-iptables in Kubernetes deployments?
Options:
To disable IP forwarding.
To enhance security settings.
To improve network performance.
To allow Kubernetes to create virtual networks for pods.
Answer:
DExplanation:
Enabling the Linux kernel parameter `net.bridge.bridge-nf-call-iptables` (setting it to `1` via `sysctl`) is a mandatory networking requirement for running the RKE2 Kubernetes distribution within UiPath Automation Suite. By default, bridged Linux network packets pass through data-link layer bridges without being processed by network-layer `iptables` rules. Setting `bridge-nf-call-iptables = 1` forces packets traversing bridged virtual interfaces to be routed through host `iptables` chains. This enables the Container Network Interface (CNI) plugin (such as Canal/Flannel/Calico) and `kube-proxy` to implement pod networking, apply Network Policies, manage packet filtering, and perform Network Address Translation (NAT) for Kubernetes ClusterIP and NodePort Services. Without this setting enabled, inter-pod routing across virtual bridge devices fails, preventing pods from communicating within the cluster. (Reference: UiPath Automation Suite Linux Host Preparation – Kernel Parameters and Network Prerequisites).
At which stage of the Automation Suite deployment can you select either the online or offline deployment method?
Options:
From ArgoCD after installation.
After executing the prereq run command to validate the prerequisites required by the shared components installation.
After installing the infrastructure on the first server machine.
During the cluster_config.json generation or by editing the cluster_config.json before installation.
Answer:
DExplanation:
The deployment method—Online (direct connectivity to UiPath public container repositories) or Offline (air-gapped, leveraging a local private OCI container registry)—is an architectural setting that must be committed prior to cluster provisioning. This decision is established during the generation of the `cluster_config.json` file via the interactive installation wizard, or by manually declaring the install type directly within `cluster_config.json` prior to initiating the deployment. Defining this property early dictates how the installation engine fetches binaries, evaluates certificate trust, configures container runtime mirror endpoints, and deploys registry credentials. This setting cannot be altered post-installation through GitOps tools like ArgoCD, nor can it be deferred until after the infrastructure has been provisioned on the first server. The `cluster_config.json` file serves as the single source of truth for the RKE2 provisioning scripts and deployment manifests. (Reference: UiPath Automation Suite Installation Guide – Configuration File Parameters and Generation).
===============
While working with the Kubernetes cluster in an Automation Suite deployment and running kubectl, a “command not found” error occurs. Which command will resolve the issue?
Options:
unset KUBECONFIG
export HTTPS_PROXY=“”
export KUBECONFIG=“/etc/rancher/rke2/rke2.yaml” & & export PATH=“$PATH:/usr/local/bin:/var/lib/rancher/rke2/bin”
export PATH=$PATH:/var/lib/rancher/bin
Answer:
CExplanation:
On Linux distributions running Automation Suite on RKE2, Kubernetes administrative binaries and cluster credential configurations are not included in standard default system shell paths. The `kubectl` binary is installed in `/var/lib/rancher/rke2/bin`, while cluster administrative access configurations are generated in `/etc/rancher/rke2/rke2.yaml`. When an administrator logs into a host and attempts to execute `kubectl`, the shell throws a "command not found" error because the directory is absent from the `$PATH` environment variable. To resolve this, the administrator must append the directory to `$PATH` and export the `KUBECONFIG` path: `export KUBECONFIG="/etc/rancher/rke2/rke2.yaml" & & export PATH="$PATH:/usr/local/bin:/var/lib/rancher/rke2/bin"`. This ensures the shell finds the executable and authenticates with cluster credentials. (Reference: UiPath Automation Suite Administration – Environment Configuration and RKE2 Tools Access).
===============
What is Istio’s primary function in Automation Suite?
Options:
application lifecycle management (ALM) capabilities
querying and visualizing object storage data
deduplicating, grouping, and routing alerts
ingress, request routing, traffic monitoring
Answer:
DExplanation:
Istio serves as the core service mesh technology integrated within UiPath Automation Suite, functioning primarily to manage external ingress, request routing, and platform-wide traffic monitoring. Acting as the reverse-proxy ingress gateway, Istio terminates external TLS/SSL connections, routes incoming client traffic to appropriate backend services (such as Orchestrator, Identity Server, or Webhooks) based on URL hostnames and paths, and enforces mutual TLS (mTLS) for secure service-to-service communication. In addition to ingress traffic routing, Istio collects telemetry, latency measurements, and transaction metrics across distributed microservices, feeding observability data into Prometheus and Grafana for monitoring. Application lifecycle management is handled by ArgoCD, alerting is managed by Alertmanager, and metrics storage is handled by Prometheus, making traffic management and ingress Istio's primary responsibilities within the architecture. (Reference: UiPath Automation Suite Architecture Guide – Service Mesh and Ingress Networking).
===============
Is UiPath Insights supported on hosts with FIPS 140-2 enabled?
Options:
Not supported.
Yes, fully supported.
Supported with limited functionality.
Supported only on multi-node setup.
Answer:
AExplanation:
Federal Information Processing Standard (FIPS) 140-2 is a U.S. government computer security standard governing cryptographic modules. Within UiPath Automation Suite, host machines operating with FIPS 140-2 mode enabled are not supported for the UiPath Insights service. Insights utilizes third-party analytics and data visualization runtimes whose cryptographic algorithms and hashing libraries are not certified under or compatible with the strict kernel-level enforcement of FIPS 140-2. When Automation Suite is installed in a FIPS-compliant Linux host environment, the Insights service must be disabled in `input.json` or `cluster_config.json`. Attempting to run Insights with FIPS enabled results in container initialization crashes and service startup failures due to non-compliant cryptographic calls. Organizations requiring FIPS compliance must either exclude Insights from their deployment scope or run Insights in an isolated, non-FIPS environment. (Reference: UiPath Automation Suite Security and Compliance Guide – FIPS 140-2 Compatibility Matrix).
===============
Which deployment templates are available for deploying Automation Suite?
Options:
Azure, Linode, Oracle Cloud
AWS, Azure, Linode
AWS, Azure, GCP
AWS, Azure, Alibaba cloud
Answer:
CExplanation:
UiPath officially develops, validates, and maintains automated infrastructure deployment templates for the three major hyperscale public cloud providers: Amazon Web Services (AWS), Microsoft Azure, and Google Cloud Platform (GCP). These production-ready cloud templates utilize Infrastructure as Code (such as Azure Resource Manager / Bicep, AWS CloudFormation, and GCP Deployment Manager / Terraform modules) to automatically orchestrate virtual networks, subnets, Network Security Groups, load balancers, managed databases (e.g., Azure SQL, AWS RDS), external object stores, and appropriately sized virtual machine instances. Niche or alternative cloud providers—including Linode, Oracle Cloud Infrastructure (OCI), and Alibaba Cloud—do not have native, pre-packaged automation templates supplied by UiPath, meaning any deployment on those platforms would require custom, uncertified manual provisioning. Enterprise architects leverage the AWS, Azure, and GCP templates to accelerate deployment timelines and ensure cluster topology aligns strictly with UiPath's high-availability production best practices. (Reference: UiPath Automation Suite Deployment Guide – Cloud Infrastructure Templates).
===============
What must be ensured about the secondary site if a disaster occurs in one of the Automation Suite clusters?
Options:
It has sufficient capacity to handle the load.
It has identical hardware.
It has a better user interface.
It is located in a different country.
Answer:
AExplanation:
In an enterprise disaster recovery architecture for UiPath Automation Suite, the secondary site must be provisioned with sufficient compute, storage, and networking capacity to handle full operational workloads during a failover event. While identical hardware is beneficial for predictability, strict hardware uniformity is not mandatory as long as CPU, memory, IOPS, and network bandwidth satisfy platform baselines. If the secondary site lacks sufficient capacity, shifting user traffic and automated robot workloads during a primary site failure can cause resource starvation, pod evictions, and service downtime. Infrastructure architects must ensure that secondary sites match production sizing requirements to maintain continuous service delivery during failover scenarios. (Reference: UiPath Automation Suite Disaster Recovery Planning – Sizing and Capacity Assurance).
===============
Which of the following requirements must be satisfied before removing a node from an Automation Suite cluster?
Options:
The cluster must be running in a single-node evaluation profile with all pods in a Ready state.
The cluster must be a multi-node HA-ready production setup with a healthy state and at least three server nodes remaining.
The cluster must include at least two server nodes per availability zone and be in maintenance mode.
The node must be shut down and disconnected manually before the uipathctl rke2 node remove command can be executed.
Answer:
BExplanation:
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).
===============
What is the minimum TLS version supported by Automation Suite on Linux?
Options:
TLS 1.0
TLS 1.1
TLS 1.2+
TLS 1.3
Answer:
CExplanation:
UiPath Automation Suite on Linux enforces strict cryptographic security baselines across external ingress points, load balancers, and internal microservice communication channels. The platform mandates TLS 1.2 or higher (TLS 1.2+) as the baseline encryption standard. Legacy protocols, specifically TLS 1.0 and TLS 1.1, are deprecated and explicitly blocked due to known structural vulnerabilities (such as POODLE and BEAST attacks) and non-compliance with industry data security standards such as PCI-DSS and HIPAA. All incoming connections terminated by the reverse proxy ingress controller (powered by Istio) and external load balancers reject handshake negotiations requesting protocol versions below TLS 1.2. While TLS 1.3 is fully supported and negotiated when modern client cipher suites are present, TLS 1.2 remains the documented minimum supported protocol across all Automation Suite Linux architectures. Infrastructure engineers must ensure that external proxies, inspection firewalls, and connecting automation robot clients are configured to negotiate TLS 1.2 or TLS 1.3. (Reference: UiPath Automation Suite Security and Network Requirements – TLS and Cipher Suite Standards).
===============
After restoring from a snapshot, what steps must be completed to restore the data and settings for a cluster without AI Center enabled?
Options:
recover cluster_config.json,retrieving new monitoring password;
recovering cluster_config.json,adding CA certificates to the trust store,retrieving new monitoring password;
recover cluster_config.json,adding CA certificates to the trust store,retrieve a new cluster_config.json file;
adding CA certificates to the trust store,retrieving new monitoring password;
Answer:
BExplanation:
When executing a full platform restore from an infrastructure snapshot on a cluster where AI Center is not enabled, administrators must complete specific post-restoration procedures to re-establish platform integrity. The documented workflow comprises three mandatory operational steps: recovering the `cluster_config.json` configuration file, re-adding internal Certificate Authority (CA) certificates to the host operating system trust stores across all restored virtual machines, and retrieving the regenerated monitoring stack password for Prometheus and Grafana access. Recovering `cluster_config.json` restores cluster metadata and operational flags, while re-importing the CA certificates into the operating system certificate store prevents SSL/TLS handshake failures during intra-cluster and container communication. Because Dex credentials rotate or reset during snapshot restores, retrieving the new monitoring password restores administrative visibility into system metrics. Clusters with AI Center enabled require an additional specialized pipeline restoration step. (Reference: UiPath Automation Suite Backup and Restore Guide – Post-Restoration Configuration).
===============
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 deploying an enterprise-grade Automation Suite in offline mode, which of the following challenges must be handled that are normally abstracted or automatically managed in online deployments?
Options:
Manually managing package repositories, container images, and dependency resolution for orchestration components without access to remote registries.
Implementing asynchronous message queuing for distributed microservices using managed event brokers like AWS SNS/SQS or Azure Service Bus.
Ensuring low-latency connectivity between automation bots and the orchestrator via redundant WAN routing.
Utilizing federated identity protocols such as OpenID Connect (OIDC) to enforce real-time SSO policies via cloud-based IAM providers.
Answer:
AExplanation:
In an online Automation Suite deployment, the installation engine pulls container images, Linux RPM dependencies, and Helm charts directly from public UiPath and vendor repositories. In an offline or air-gapped deployment, all outbound internet traffic is blocked, requiring infrastructure teams to manually manage the artifact supply chain. Administrators must download multi-gigabyte bundle packages, transfer them to target hosts using secure media, configure a local OCI-compliant registry, mirror container layers, and stage operating system packages locally. Missing a single dependency or container image will halt the installation process. Online deployments manage these dependencies automatically, making manual dependency resolution a key requirement of air-gapped implementations. (Reference: UiPath Automation Suite Offline Deployment Guide – Enterprise Air-Gapped Operations).
===============
How many HAA licenses are needed to configure an Active/Passive deployment of Automation Suite?
Options:
Two licenses, one for each shard.
One license for each cluster.
Only one license is sufficient.
Two licenses, one for each cluster.
Answer:
DExplanation:
Configuring an Active/Passive multi-site disaster recovery deployment of UiPath Automation Suite requires two separate High Availability Add-on (HAA / Redis Enterprise) licenses: one for each participating cluster. In an Active/Passive topology, both the primary production cluster and the standby secondary cluster run independent instances of the Redis High Availability Add-on to provide session caching, state replication, and message brokering. Because each cluster operates as an independent Kubernetes deployment with its own control plane and network boundary, an independent license must be activated on each site. UiPath technical specifications dictate that each cluster must be licensed for a minimum of two shards. Attempting to share a single HAA license across clusters or omitting licensing on the standby site prevents cluster synchronization and breaks failover readiness. (Reference: UiPath Automation Suite Disaster Recovery Architecture – HAA Redis Licensing Model).
===============
Which format and minimum key length are required for a TLS certificate used with Automation Suite?
Options:
.crt format, at least 1024-bit key length
.cer format, at least 1024-bit key length
.key format, at least 1024-bit key length
.pern format, at least 2048-bit key length
Answer:
DExplanation:
Securing ingress communication into UiPath Automation Suite requires a valid, trusted SSL/TLS certificate. The platform mandates certificates in Base64-encoded DER format (standard `.pem` format, referred to with the documented typographical variation `.pern` in legacy question banks). The private key must use a minimum length of 2048 bits. Shorter keys (such as 1024-bit RSA keys) are rejected by security baselines and internal cryptographic policies due to known vulnerabilities. The certificate must include the full intermediate and root CA bundle alongside the server certificate, and its Subject Alternative Names (SANs) must cover the cluster FQDN and all service subdomains. Supplying an invalid format or insufficient key length will cause the ingress gateway to reject the TLS secret during deployment. (Reference: UiPath Automation Suite Infrastructure Pre-requisites – Certificate and TLS Guidelines).
===============
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).
===============
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).
===============
When installing Automation Suite with Azure, AWS, or GCP templates, what must you do regarding RPM packages?
Options:
Validate RPM packages.
Manually install RPM packages.
No action is needed.
Download RPM packages.
Answer:
CExplanation:
When deploying UiPath Automation Suite using the official cloud infrastructure templates developed for Azure, AWS, or GCP, no administrative action is needed regarding operating system RPM packages. These cloud-native Infrastructure as Code templates automate the complete provisioning lifecycle. Custom extension scripts and initialization mechanisms embedded within the cloud templates automatically configure OS package repositories, resolve dependencies, and install all mandatory Linux RPM packages (such as `lvm2`, container utilities, and networking tools) directly on the provisioned compute instances during startup. Manual package downloads, RPM dependency caching, and manual validation are required only for manual bare-metal or on-premises virtual machine installations, particularly in air-gapped environments. The automated cloud templates abstract host-level operating system package management entirely. (Reference: UiPath Automation Suite Cloud Deployment – Automated Template Architecture).
===============
While deploying an Automation Suite node, the installer reports that one mount point is absent from fstab. Which command lists the entire contents of the fstab file?
Options:
cat /etc/fstab
touch /etc/fstab
echo /etc/fstab
ls /etc/fstab
Answer:
AExplanation:
The standard file system table configuration in Linux is located at `/etc/fstab`, which dictates how disk partitions, logical volumes, and remote shares are mounted persistently during system boot cycles. To view and audit the entire textual contents of this configuration file on an active node, the command `cat /etc/fstab` is executed in the terminal. During Automation Suite pre-installation checks or disk preparation scripts (`uipathctl rke2 disk`), the installer verifies whether mandatory mount paths (such as `/var/lib/rancher/rke2`, `/uipath`, or etcd data mount points) are recorded within `/etc/fstab` with valid UUIDs, file system types (ext4 or xfs), and mount flags. If a required entry is absent, mounting will fail after a system restart, leading to control plane or storage engine failure. Commands such as `ls` or `echo` merely print directory listings or file path strings, and `touch` modifies file access timestamps. (Reference: UiPath Automation Suite Node Preparation and Linux Storage Administration).
===============
Which command should you run to obtain the password for accessing the monitoring tools?
Options:
kubectl get secrets/dex-static-credential -n uipath -o “jsonpath={.data[‘password’]}” | base64 -d
kubectl get deployment/dex-static-credential -n uipath -o “jsonpath={.data[‘password’]}” | base64 -d
kubectl get password/dex-static-credential -n uipath -o “jsonpath={.data[‘password’]}” | base64 -d
kubectl get config/dex-static-credential -n uipath -o “jsonpath={.data[‘password’]}" | base64 -d
Answer:
AExplanation:
Authentication to cluster-wide monitoring and observability dashboards (including Prometheus, Grafana, and Alertmanager) in Automation Suite is mediated through Dex, an OpenID Connect identity service running inside the Kubernetes cluster. The static administrative credentials used to authenticate to Dex are stored as an opaque Kubernetes Secret named `dex-static-credential` located within the `uipath` namespace. Because Kubernetes Secrets store sensitive key-value pairs as Base64-encoded strings, accessing the plaintext password requires querying the secret resource via `kubectl`, extracting the specific JSON path (`.data.password`), and piping the output through a decoding utility (`base64 -d` or `base64 --decode`). The precise syntax is `kubectl get secrets/dex-static-credential -n uipath -o "jsonpath={.data['password']}" | base64 -d`. Attempting to query non-existent Kubernetes resource types such as `password` or querying `deployment` resources will result in API lookup errors. (Reference: UiPath Automation Suite Administration – Managing Cluster Monitoring and Logging Access).
===============
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).
===============
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).
===============
What must be done when multiple Automation Suite instances are deployed on the same OpenShift cluster?
Options:
Install Redis in each relevant namespace and update input.json accordingly
Use Kubernetes ConfigMaps to link Redis across namespaces
Redis is not needed if Service Mesh is installed
Use a shared Redis installation across all namespaces
Answer:
AExplanation:
When consolidating multiple, isolated Automation Suite environments (e.g., Development, Staging, or multiple business units) within a shared Red Hat OpenShift cluster, tenant isolation and state boundary integrity are enforced at the namespace level. UiPath microservices depend on Redis for distributed caching, user session state storage, and transient queuing across services like Orchestrator and Identity Server. In a multi-instance scenario on a single cluster, engineers must install an independent Redis instance within each corresponding Automation Suite namespace and subsequently update the respective `input.json` deployment file with the distinct Redis host connection strings. Sharing a single, centralized Redis deployment across multiple distinct Automation Suite namespaces is unsupported because cache key collisions, session cross-talk, and unified cache flushes would compromise tenant data separation and operational availability. Namespace-isolated Redis deployments maintain predictable caching latencies and adhere to OpenShift security context constraints. (Reference: UiPath Automation Suite on OpenShift – Multi-Tenancy and Shared Cluster Topologies).
===============
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).
===============
Unlock UiPath-IEPASv1 Features
- UiPath-IEPASv1 All Real Exam Questions
- UiPath-IEPASv1 Exam easy to use and print PDF format
- Download Free UiPath-IEPASv1 Demo (Try before Buy)
- Free Frequent Updates
- 100% Passing Guarantee by Activedumpsnet
Questions & Answers PDF Demo
- UiPath-IEPASv1 All Real Exam Questions
- UiPath-IEPASv1 Exam easy to use and print PDF format
- Download Free UiPath-IEPASv1 Demo (Try before Buy)
- Free Frequent Updates
- 100% Passing Guarantee by Activedumpsnet