UiPath-IEPASv1: UiPath Infrastructure Engineer Professional - Automation Suite ExamDemo

UiPath Automation Suite supports disks formatted with ext4 or xfs for installation.

OpenSSL can establish a TLS connection to the load balancer and display the certificate chain and certificate details it presents.

For offline installations, the temporary registry is hydrated with the required container images and deployment Helm charts, making those installation artifacts available during deployment.

UiPath documents uipathctl config orchestrator upload as the command for uploading files to Orchestrator storage, including configuration-related files and extensions.

For an Automation Suite upgrade failure that cannot be recovered, the supported recovery action is to roll back to the previously installed version through the backup and restore capability. This returns the platform to its prior backed-up, working state.

An agent node runs UiPath products and shared components. Cluster management services run on server nodes, while specialized agent nodes run workloads such as GPU-dependent Document Understanding pipelines or Automation Suite Robots. UiPath Automation Suite deployment architecture

Automation Suite server nodes host the Kubernetes control plane, which provides cluster-management functions such as workload orchestration and cluster-state management. UiPath products and shared components may also run there when resources permit, but that is not their defining role. UiPath Automation Suite deployment architecture

Automation Suite installation operations can be resumed by rerunning the installation command with all required arguments and flags, preserving the intended installation configuration.

The -k flag performs a preinstallation validation of the Linux environment, including required dependencies and infrastructure prerequisites.

UiPath Automation Suite supports both AMD and Intel processors when the required architecture is met. ARM-based processors, including Graviton, are not supported by the Kubernetes distribution used for the deployment.

Document Understanding ML packages require the appropriate offline bundle in an air-gapped deployment. The bundle must be obtained separately and copied to the main machine of the cluster before it is uploaded to the private registry. UiPath: ML Packages Offline Installation

The uipathctl rke2 disk command configures the required installation disks by creating and managing the necessary partitions and mount points, typically using LVM. UiPath requires disk partitioning and configuration before an Automation Suite installation.

UiPath Automation Suite uses input.json to control product selection. Set the relevant service enable flags in this file and apply the updated configuration with uipathctl.

For Automation Suite backups, every cluster node must be able to reach the NFS server so the cluster can access the shared backup storage.

The external object-store CORS policy must allow POST and PUT for uploads and object writes, GET and HEAD for retrieval and metadata checks, and DELETE for object removal. UiPath’s documented CORS policy for an external S3-compatible object store specifies exactly POST, GET, HEAD, DELETE, and PUT as AllowedMethods.

A parallel Automation Suite upgrade requires migration of the source cluster’s databases and cluster data to the new target cluster. The target is ready to receive traffic only after data migration is complete and validation succeeds. UiPath: Performing a side-by-side upgrade

/etc/fstab contains the filesystem mount configuration, and cat /etc/fstab outputs all of that file’s contents to the terminal.

UiPath Automation Suite provides cloud deployment templates for AWS, Azure, and Google Cloud Platform (GCP).

The monitoring-tools password is stored in the dex-static-credential Kubernetes Secret in the uipath namespace. Reading its data.password JSONPath value and Base64-decoding it returns the password. UiPath documents this command using base64 --decode, which is equivalent to base64 -d.

AI Computer Vision runs on a GPU and requires a dedicated Automation Suite agent node with GPU support.

Multiple Automation Suite instances on one OpenShift cluster require Redis to be installed in each corresponding namespace. Each instance’s input.json must be updated with the Redis host appropriate to that installation, which preserves instance-specific Redis configuration.

For an Automation Suite in-place upgrade, Kubernetes and the other infrastructure components are upgraded with the uipathctl rke2 upgrade command, using cluster_config.json and the Helm charts version file.

Automation Suite deployment mode is configured during creation of cluster_config.json. The installer wizard offers Online and Offline deployment-mode options, and the generated configuration can be edited before installation.

Automation Suite Robots use the serverless.robot=true and serverless.daemon=true node labels together with the serverless-robot taint. UiPath states that the taint alone is insufficient for scheduling the Automation Suite Robot pods.