VMware 2V0-31.24 Practice Exams
Last updated on Nov 16,2026- Exam Code: 2V0-31.24
- Exam Name: VMware Aria Automation 8.10 Professional V2
- Certification Provider: VMware
- Latest update: Nov 16,2026
Which statement is true for VMware Aria Automation multi-organization tenant configuration’
- A . Providers set up multiple tenants, each tenant manages its own projects but resources, and deployments are managed globally
- B . Providers can set up multiple tenants and allocate infrastructure within each deployment and providers manage projects, resources, and deployments
- C . Providers set up multiple tenants, each tenant manages its own projects, resources, and deployments
- D . Providers can set up multiple tenants and allocate infrastructure within each deployment, providers manage tenant infrastructure remotely
C
Explanation:
In a VMware Aria Automation multi-organization tenant configuration, the setup allows for multiple tenants, where each tenant has the autonomy to manage its own projects, resources, and deployments. This configuration is essential for organizations that require segregation of duties and resources among different departments, business units, or customers. Each tenant operates independently, which provides flexibility and security, ensuring that the resources and deployments of one tenant do not interfere with another. This setup supports a scalable and manageable approach to infrastructure and service management across large and complex environments.
Reference
VMware Aria Automation Multi-Organization Configuration Documentation
What is the purpose of Kubernetes Zones in VMware Aha Automation?
- A . Allows an administrator to define policy-based placement of Kubernetes clusters, namespaces and supervisor namespaces.
- B . Allows an administrator to define Kubernetes clusters in VMware Aria Automation Assembler deployments.
- C . Allows administrators to support multi-tennancy for kubernetes clusters and namespaces.
- D . Allows an administrator to define supervisor namespaces used in VMware vSphere.
A
Explanation:
In VMware Aria Automation, Kubernetes Zones allow administrators to define policy-based placement of Kubernetes clusters, namespaces, and supervisor namespaces. This feature helps ensure that Kubernetes resources are deployed in accordance with organizational policies and governance requirements, facilitating efficient and compliant resource management within the cloud infrastructure.
Reference: VMware Aria Automation Documentation
Using capability tags in Automation Assembler
An administrator configures a lease policy with the following settings:
• Maximum lease (days): 10
• Maximum total lease (days): 30
• Grace period (days): 5
If a user does not respond to any emails, after how many days will the deployment be destroyed?
- A . 40
- B . 10
- C . 15
- D . 35
D
Explanation:
In VMware Aria Automation, lease policies dictate how long a deployment remains active.
The lease policy consists of three primary parameters:
Maximum lease (days): 10 – This is the maximum number of days a deployment can stay active before it must be renewed.
Maximum total lease (days): 30 – This is the cumulative maximum number of days a deployment can be renewed to stay active.
Grace period (days): 5 – This is the number of additional days provided after the lease expires for the user to take action before the deployment is destroyed.
With the above settings, the deployment will follow this timeline:
Initially, the deployment is active for the maximum lease period of 10 days.
After 10 days, if not renewed, the deployment enters the grace period.
During the grace period, which lasts for 5 days, the deployment remains active but is marked for deletion.
If the user does not respond or renew the lease, the deployment is destroyed at the end of the grace period.
Therefore, after the 30-day maximum total lease (10 days initially + maximum 20 days of renewals), an additional 5-day grace period is provided. The total period before the deployment is destroyed is 35 days (30 days + 5 days).
Reference
VMware Aria Automation: Demystifying Lease Policy
VMware Aria Automation Lease Policies
Getting Started with Automation Assembler using the VMware Aria Automation Launchpad
When creating a subscription in VMware Aria Automation Assembler, what are the two types of runnable items available for executing code? (Choose two.)
- A . Python
- B . PowerShell
- C . ABX Action
- D . Node.js
- E . VMware Aria Automation Orchestrator Workflow
C, E
Explanation:
When creating a subscription in VMware Aria Automation Assembler, the two types of runnable items available for executing code are:
ABX Action (C): Action-Based Extensibility (ABX) allows users to write small pieces of code (actions) in various languages such as Python, Node.js, and PowerShell to handle specific events and workflows within VMware Aria Automation.
VMware Aria Automation Orchestrator Workflow (E): VMware Aria Automation Orchestrator provides a comprehensive platform for automating complex IT tasks and workflows. Workflows can be created and orchestrated to interact with various VMware and third-party systems, and they can be triggered by subscriptions to automate processes in VMware Aria Automation.
These runnable items enable the automation and customization of workflows and actions based on specific events and triggers within the VMware Aria Automation environment.
Reference
VMware Aria Automation ABX Documentation
VMware Aria Automation Orchestrator Documentation
An administrator must assign an existing role to a group of users who should be able to create VMware Aria Automation templates.
Which role should be assigned following the least privilege rule?
- A . VMware Aria Automation Orchestrator Workflow designer
- B . VMware Aria Automation Assembler Administrator
- C . VMware Aria Automation Assembler User
- D . VMware Aria Automation Organization Owner
C
Explanation:
In the context of VMware Aria Automation, adhering to the principle of least privilege means granting users the minimum level of access necessary to perform their roles. For users who need to create VMware Aria Automation templates, the appropriate role is the "VMware Aria Automation Assembler User."
This role provides sufficient permissions to create and manage blueprints (templates) without granting broader administrative rights that are unnecessary for their tasks. This ensures that users have the capabilities they need while maintaining a secure and controlled environment.
Reference: VMware Aria Automation Documentation
VMware Aria Suite Overview
What is the location of the VMware Aria Automation Orchestrator log files within the VMware Aria Automation appliance?
- A . /var/syslog/syslog.d
- B . /var/log/vmware/vco
- C . /opt/charts/vco/templatea/logs
- D . /data/vco/usr/lib/vco/app-aerver/logs/
D
Explanation:
VMware Technical Support routinely requests diagnostic information when you submit a support request. This diagnostic information contains product-specific logs and configuration files from the host on which the product runs.
Automation Orchestrator Appliancelogs are stored in the/data/vco/usr/lib/vco/app-server/logs/directory. You export the logs of yourAutomation Orchestrator Appliance deployment by logging in to the appliance command line and running thevracli log-bundlecommand. The generated log bundle is saved on the root folder of yourAutomation Orchestrator Appliance.
https://docs.vmware.com/en/VMware-Aria-Automation/8.17/Installing-Configuring-Automation-Orchestrator/GUID-0BA1B08B-7A94-45AD-ADFF-3440529E5F59.html#:~:text=Automation%20Orchestrator%20Appliance%20logs%20are,%2Dserver%2Flogs%2F%20directory.
An administrator is tasked with creating a new vSphere and NSX VMware Aria Automation template for the App-Dev team. The administrator successfully configures multiple network profiles that will create different types of on-demand networks. The App-Dev team wants the VMware Aria Automation template to create an on-demand network that can be connected externally.
Which two network types should the administrator consider using in the VMware Aria Automation template? (Choose two.)
- A . Public
- B . Existing
- C . Outbound
- D . Private
- E . Routed
A, E
Explanation:
To create an on-demand network that can be connected externally in a VMware Aria Automation template, the administrator should consider using the following network types:
Public: This network type allows the creation of networks that have direct access to the internet, making them suitable for externally accessible applications.
Routed: This network type provides the ability to create networks that can route traffic between different subnets and external networks, enabling external connectivity.
Both network types facilitate external access, making them ideal for the App-Dev team’s requirements.
Reference
VMware Aria Automation Network Profiles
VMware Aria Automation Network Configuration
Exhibit.

An administrator configures a lease policy. ("1 Day Lease"), for the App-Dev project so that machines have a starting and a maximum lease of five days.
The following week, the administrator is assigned a ticket to address an issue with machines being deleted without an being received. The administrator requests a new machine deployment through the App-Dev project’s service catalog, day lease period, the administrator expects to receive an automated "Lease Expiring” system immediately following a deployment; however, the email is not received. The administrator checks the deployment that has just been created the exhibit) and confirms that the "1 Day Lease" policy has been correctly applied.
Which action should the administrator take to resolve this issue?
- A . Configure the notification email Server.
- B . Add an email endpoint.
- C . Ensure the users have notifications enabled.
- D . Run the Configure mail workflow.
C
Explanation:
The issue of not receiving the "Lease Expiring" email notification likely stems from user notification settings. Ensuring that users have notifications enabled in their profile settings is crucial for them to receive automated emails regarding lease expirations and other important events. Administrators should verify and configure these settings to ensure that users are properly informed about their deployments.
Reference: VMware Aria Automation Notification Configuration
Configuring Notifications in VMware Aria Automation
Although an organization has sufficient capacity within the on-premises VMware SDDC, the CTO has decided to evolve the public cloud strategy into a "Right Cloud First" strategy. To support this, the administrator has suggested the use of VMware Aria Automation to provide a consistent portal with a multi-cloud service catalog to enable the users to use self-service to deploy workloads into different clouds. The administrator needs to configure cloud accounts for public clouds to support the new strategy.
Which two of the public clouds are supported platforms? (Choose two.)
- A . Microsoft Azure
- B . Oracle Cloud
- C . IBM Cloud
- D . OVH Cloud
- E . Google Cloud Platform
A, E
Explanation:
VMware Aria Automation supports multiple public cloud platforms for integration, allowing administrators to create a consistent multi-cloud service catalog.
Among the supported platforms are:
Microsoft Azure: This integration enables administrators to manage and deploy workloads on Azure using the VMware Aria Automation portal, taking advantage of Azure’s extensive cloud services and infrastructure.
Google Cloud Platform (GCP): Similarly, GCP integration allows users to deploy and manage their resources on Google’s cloud infrastructure through the same unified VMware Aria Automation interface.
These integrations are crucial for organizations adopting a "Right Cloud First" strategy, providing flexibility and consistency across different cloud environments.
Reference: VMware Aria Automation Documentation
VMware Cloud Management Blog
Which type of tag does VMware Aria Automation Assembler automatically apply during provisioning to some deployments to support the analysis, monitoring, and grouping of deployed resources?
- A . Constraint tag
- B . Capability tag
- C . Standard tag
- D . Storage tag
C
Explanation:
In VMware Aria Automation Assembler, tags are critical for managing, analyzing, monitoring, and grouping deployed resources. Among the various types of tags, the standard tag is automatically applied during the provisioning of some deployments. These standard tags are essential for supporting the analysis, monitoring, and grouping of deployed resources.
Standard tags in VMware Aria Automation are system-generated and stored as custom properties. They are used primarily for tracking and managing resources post-deployment. Unlike user-defined tags, standard tags are automatically applied and are not used during the deployment configuration to enforce constraints or capabilities. Instead, they facilitate operational functions such as monitoring resource usage, ensuring compliance, and optimizing resource management.
Other types of tags, like constraint tags and capability tags, are user-defined and are crucial during the deployment process for determining resource allocation and meeting specific requirements or constraints. However, standard tags serve a distinct purpose by providing a consistent way to monitor and group resources after they have been provisioned. Reference
Using Automation Assembler project tags and custom properties Tagging Design for VMware Aria Automation Assembler
How do I use tags to manage Cloud Assembly resources and deployments