In what situations does an upgrade to a new Automation Suite version require a conditional license?
Answer : D
During the lifecycle upgrade of an offline (air-gapped) Automation Suite deployment that does not utilize a persistent external OCI container registry, the upgrade process relies on an ephemeral, temporary in-cluster Docker registry to stage and distribute updated container layers and Helm charts. In this specific operational situation, the machine orchestrating the upgrade requires network access over port 30070. UiPath documents port 30070 as a conditional firewall and network prerequisite specifically tied to accessing this temporary container registry during an upgrade or installation procedure. If port 30070 is blocked by internal operating system firewalls (`firewalld`/`iptables`) or network security group policies, the installer cannot hydrate or pull target container images, halting the upgrade workflow. While standard platform ingress operates on port 443 and Kubernetes management operates on port 6443, port 30070 represents the specific conditional requirement for offline upgrade registry interaction. (Reference: UiPath Automation Suite Upgrade Guide -- Network Port Requirements and Temporary Registry Configuration).
===============
Which uipathctl command generates the configurations required to install Automation Suite on AKS, EKS, or OpenShift?
Answer : D
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).
===============
Which permission below is explicitly identified as unnecessary for the Automation Suite installer in an OpenShift environment?
Answer : D
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).
===============
Which of the following actions is required when carrying out a parallel Automation Suite upgrade?
Answer : B
In an Automation Suite parallel (side-by-side) upgrade strategy, an entirely new target cluster is provisioned alongside the existing production environment running the legacy version. Because the target cluster starts as a fresh deployment, a mandatory action to complete the upgrade is migrating the data from the source cluster to the new target cluster. This process entails taking database backups or replicating state, transferring persistent object store contents, and migrating persistent volume data (often mediated via external object storage) to the target infrastructure. Unlike in-place upgrades that sequentially update Kubernetes binaries and Helm charts while nodes remain in maintenance mode, the parallel upgrade keeps the original cluster untouched and operational until data migration, data schema updates, and validation testing conclude successfully. Once the target cluster finishes data hydration and passes health checks, traffic cutover occurs via DNS or load balancer redirection. (Reference: UiPath Automation Suite Upgrade Guide -- Parallel vs. In-Place Upgrade Methodology).
===============
Which deployment templates are available for deploying Automation Suite?
Answer : C
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).
===============
Which syntax correctly enables snapshot backup every 55 minutes?
Answer : D
The Automation Suite command-line maintenance utility `./configureUiPathAS.sh snapshot config` configures scheduled cluster snapshots. In the CLI syntax, the `-s` flag accepts a standard cron expression string defining the execution schedule, while the `-r` flag designates the retention policy in hours. The cron expression `*/55 * * * *` (presented in the question's shortened string format as `'/55***'`) specifies an automated recurring backup cadence of every 55 minutes. Furthermore, UiPath snapshot configuration requires the retention period (`-r`) to be specified in integer hourly increments, making `'50h'` (50 hours of retained snapshot backups) a syntactically valid argument, whereas minute-based units (`'50m'` or `'55m'`) are invalid. The `-t nfs` flag defines the target storage type, `-e` enables the recurring schedule, and `-l` points to the designated backup mount directory. (Reference: UiPath Automation Suite Backup and Disaster Recovery -- Snapshot Scheduling Configuration).
===============
In a multi-node HA-ready production deployment, is the number of agent nodes fixed or optional?
Answer : D
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).
===============