- 12 Actual Exam Questions
- Compatible with all Devices
- Printable Format
- No Download Limits
- 90 Days Free Updates
Get All Advanced Deploy VMware vRealize Automation 8.x (v2) Exam Questions with Validated Answers
| Vendor: | VMware |
|---|---|
| Exam Code: | 3V0-31.22 |
| Exam Name: | Advanced Deploy VMware vRealize Automation 8.x (v2) |
| Exam Questions: | 12 |
| Last Updated: | August 24, 2026 |
| Related Certifications: | VMware Certified Advanced Professional, VCAP Cloud Management and Automation Deploy |
| Exam Tags: | Advanced |
Looking for a hassle-free way to pass the VMware Advanced Deploy VMware vRealize Automation 8.x (v2) exam? DumpsProvider provides the most reliable Dumps Questions and Answers, designed by VMware certified experts to help you succeed in record time. Available in both PDF and Online Practice Test formats, our study materials cover every major exam topic, making it possible for you to pass potentially within just one day!
DumpsProvider is a leading provider of high-quality exam dumps, trusted by professionals worldwide. Our VMware 3V0-31.22 exam questions give you the knowledge and confidence needed to succeed on the first attempt.
Train with our VMware 3V0-31.22 exam practice tests, which simulate the actual exam environment. This real-test experience helps you get familiar with the format and timing of the exam, ensuring you're 100% prepared for exam day.
Your success is our commitment! That's why DumpsProvider offers a 100% money-back guarantee. If you don’t pass the VMware 3V0-31.22 exam, we’ll refund your payment within 24 hours no questions asked.
Don’t waste time with unreliable exam prep resources. Get started with DumpsProvider’s VMware 3V0-31.22 exam dumps today and achieve your certification effortlessly!
TASK 9
As the Cloud Administrator. you have been tasked to troubleshoot and fix errors of an existing cloud template. You must ensure:
1. VM resource uses storage tag:
* Key: storage. Value: gold
2. Network resource uses network tag:
* Key: net
* Value: nsx-routed
3. Configure NSX Network Type: routed
4. A virtual machine can be successfully deployed from the cloud template using the information provided.
NOTE: One or more of the tasks above may take some time to complete For expediency, it is recommended that once the task has started successfully that you continue with the exam and return later to confirm the task has been completed successfully. There are no dependencies between any_questions and therefore the successful completion of this question does no! impact the ability to attempt any_others_guestion in this exam.
NOTE: Not all available tags will appear on the tag selection drop-down when you're editing the cloud template.
Information required to complete the tasks:
* vRealize Automation URL: vr-aulomation.oorp.local
* Cloud Admin Username: vcapadmin@corp.local
* Cloud Admin Password: VMware1!
* Project Name: Earth
* Cloud Template name: Earth-TS-Fix
* Deployment name: Earth-Fixed
* Hostname: earth-fixed
NOTE: Do not create any new profit or tags.
To troubleshoot and fix the errors in the existing cloud template and ensure the requirements are met, you can follow these steps:
Ensure VM Resource Uses Storage Tag:
Edit the cloud template named Earth-TS-Fix.
Locate the VM resource definition.
Add or update the storage tag to use the key storage with the value gold:
tags:
- key: storage
value: gold
Ensure Network Resource Uses Network Tag:
Within the same cloud template, find the network resource definition.
Add or update the network tag to use the key net with the value nsx-routed:
tags:
- key: net
value: nsx-routed
Configure NSX Network Type: Routed:
Still in the cloud template, ensure the network profile is set to a routed network type by specifying the appropriate network profile that has been pre-configured with the routed type.
networks:
- network: '${resource.Cloud_NSX_Network_1.id}'
networkType: routed
Deploy Virtual Machine from the Cloud Template:
Save the changes to the cloud template.
Initiate a deployment using the Earth-Fixed deployment name and verify that the virtual machine deploys successfully with the specified hostname earth-fixed.
Monitor the deployment process and ensure that the VM and network resources are correctly tagged and that the network is configured as routed.
TASK 3
As the Cloud Administrator, you have been tasked to do the following;
1. Create a new operating system image. 2 Create a new machine size. 3. Add two new Cloud templates:
a Import the first Cloud template from the provided file.
b. Create the second Cloud template based on the imported Cloud Template with the following requirements:
i. Allow the user to pick from a list of operating system images.
ii. Allow the user to pick from a list of machine sizes.
iii. Deployment must use the selected input values.
iv. Ensure you are able to review/compare any previous changes that have been made since the Cloud template was cloned in Cloud Assembly.
NOTE: Do not deploy the Cloud template
Information required to complete the tasks:
* vRealize Automation FODN: vr-automation.corp.local
* Cloud Admin Username: vcapadmin@corp.local
* Cloud Admin Password: VMwarel!
* vRA Project Name: Jupiter
* Flavor Mapping Name: extra large - Flavor Mapping Config:
o Account: vSphere Private Cloud Region: Local Datacenter o CPUs: 4 CPU o RAM: 16GB
* Image Mapping Name Windows Server 2019
* Image Mapping Configuration:
o Account: vSphere Private Cloud o Region: Local Datacenter o Image: windows2019
* Imported Cloud template Name: Jupiter Ubuntu Server
* Imported Cloud template File: C:VExam Files\Question 3\jupiter.yaml
* New Cloud template Name: Jupiter Cloned Server
* New Cloud template Size Input:
o Name: size
o Title: Select a Size
o Valid Options: small, medium, extra large
* New Cloud template Image Input:
o Name: image
o Title: Select an OS Image
o Valid Options: Windows Server 2019. Ubuntu18
To accomplish Task 3 as a Cloud Administrator, you would perform the following steps:
Create a new operating system image:
Log in to the vRealize Automation console using the Cloud Admin credentials.
Navigate toDesign > Image Mappingsand clickNew Image Mapping.
Enter the details for the new operating system image, including the name and the Account/Region.
Select the appropriate content library or image to use for the new image mapping12.
Create a new machine size (Flavor Mapping):
Go toDesign > Flavor Mappingsand clickNew Flavor Mapping.
Provide the configuration details for the new machine size, such as the number of CPUs and RAM size.
Assign the new flavor mapping to the vSphere Private Cloud account and the Local Datacenter region.
Add two new Cloud templates:
a.Import the first Cloud template:
Navigate toDesign > Cloud Templates.
ClickImportand select the provided filejupiter.yamlto import the Jupiter Ubuntu Server template.
b.Create the second Cloud template based on the imported Cloud Template:
After importing, clone the Jupiter Ubuntu Server template and rename it to Jupiter Cloned Server.
Modify the cloned template to include input options for the operating system image and machine size.
Ensure that the deployment uses the selected input values by referencing the input parameters in the resources section of the cloud template.
To review and compare any previous changes, utilize the version control features in Cloud Assembly to track changes made to the cloud template
TASK 1 CMA DEPLOY
As the Cloud Administrator. you have been tasked to
1. Create a new Cloud Zone
2 Create a new Project
3. Update the default pricing card.
Information requited to create the Cloud Zone and the Project;
. Account / Region: AWS - US West / us-west-2
* Name: Mercury AWS Cloud Zone
* Placement Policy: Default
* Include only Availability Zones us-west-2a and us-west-2c
* Capability Tags
o Key: region
o Value: us-west
* Project Name: Mercury
* Project Administrators: Project Mercury Admins group
* Project Members: Project Mercury Users group
* Cloud Zones: vRA-Managed vSphere Datacenter. Mercury AWS Cloud Zone
Information required to update the Pricing Card:
* Assign only for project "Mercury"
* Pricing is Rale based, as follows:
o vCPU cost is S10 per vCPU. charge monthly and only charge when powered on
o Memory cost is S5 per GB. charge monthly and only charge when powered on
o Storage cost is S1 per GB. charge monthly and always
Task 1: Create a New Cloud Zone
Log in to the vRealize Automation console as a Cloud Administrator.
Navigate toInfrastructure>Configure>Cloud Zones.
ClickNew Cloud Zone.
Enter the following details:
Account / Region: Select AWS - US West / us-west-2.
Name: Enter ''Mercury AWS Cloud Zone''.
Placement Policy: Choose Default.
Availability Zones: Include only us-west-2a and us-west-2c.
Capability Tags: Add a tag with Key as ''region'' and Value as ''us-west''.
Save the cloud zone.
Task 2: Create a New Project
In the vRealize Automation console, go toAdministration>Projects.
ClickNew Project.
Provide theProject Name: ''Mercury''.
UnderProject Administrators, add the ''Project Mercury Admins'' group.
UnderProject Members, add the ''Project Mercury Users'' group.
In theCloud Zonessection, select the previously created ''Mercury AWS Cloud Zone'' and any other required zones.
Save the project.
Task 3: Update the Default Pricing Card
Navigate toInfrastructure>Pricing Cards.
Select the default pricing card and clickEdit.
Assign the pricing card to the ''Mercury'' project by selecting it from the list.
Set the pricing details as follows:
vCPU Cost: Enter $10 and set the charge to monthly and only when powered on.
Memory Cost: Enter $5 per GB, charge monthly and only when powered on.
Storage Cost: Enter $1 per GB, charge monthly and always.
Save the changes to the pricing card.
TASK 7
The Saturn Project team has been tasked to develop a Virtual Machine Snapshot workflow. However, when completing initial testing, the workflow does not work. As the Cloud Administrator. you have been tasked with the following:
1. Ensure that the vCenter Server is included in the vRO inventory.
2. Review, troubleshoot and resolve any issues in the workflow.
3. Make sure the workflow runs successfully.
4. Make sure all snapshots created by the workflow follow the required naming standard.
Information required to complete the task:
* vRealize Automation URL. vr-automation.cofp.local
* Cloud Admin Username: vcapadmin@corp.local
* Cloud Admin Password: VMware1!
* vCenter Connection properties:
* vRealize Orchestrator Workflow: Create a Salurn Snapshot
o Workflow Details:
o Inputs:
* vm [VC:VirtualMachine]
* name [string)
o Outputs:
* snapshot (VC:VirtualMachineSnapshot]
* Workflow Run Details:
o Target Virtual Machine: core-A
o Name: q7
* Snapshot naming standard: [name]-|VM Name]-Saturn-snapshot
To address the tasks for the Saturn Project regarding the Virtual Machine Snapshot workflow, follow these steps:
Task 1: Ensure vCenter Server is in vRO Inventory
Log in to the vRealize Orchestrator Client as an administrator.
Navigate toLibrary > Workflowsand search for workflows related to vCenter configuration.
Task 2: Troubleshoot and Resolve Workflow Issues
Review the workflow namedCreate a Saturn Snapshotfor any errors or misconfigurations.
Ensure that all inputs and outputs are correctly defined and that the workflow logic is accurate.
Check the vRO logs for any errors related to the workflow execution.
Task 3: Ensure Workflow Runs Successfully
After resolving any issues, run the workflow with the target virtual machinecore-Aand the nameq7.
Verify that the workflow completes successfully and that the snapshot is created.
Task 4: Adhere to Naming Standard
Modify the workflow to ensure that the naming standard for snapshots follows the format:[name]-[VM Name]-Saturn-snapshot.
This can be done by adding a scriptable task in the workflow that constructs the snapshot name using the provided inputs and the naming standard.
Use the following code snippet in the scriptable task to set the snapshot name:
var snapshotName = name + '-' + vm.name + '-Saturn-snapshot';
// Use snapshotName variable when creating the snapshot
By following these steps, you should be able to ensure the vCenter Server is included in the vRO inventory, troubleshoot and resolve any issues with the workflow, run the workflow successfully, and adhere to the required snapshot naming standard.
TASK 10
As the Cloud Administrator you have been tasked to troubleshoot and resolve the following issues raised by the developers on the Uranus Project:
* Developers have reported that Deployments are not getting deleted as per the company lease policy.
* The Uranus Project Team Leader is responsible for approving all snapshot create requests for deployments based only on the Uranus Server blueprint, however, they have received no requests so far.
* Developers have reported that they do not have the option to revert to existing snapshots for vSphere deployments.
Once you have completed your changes, deploy the Uranus Server Catalog Item to verify all the issues have been resolved.
NOTE: One or more of the tasks above may take some time to complete. For expediency, it is recommended that once the task has started successfully that you continue with the exam and return later to confirm the task has been completed successfully. There are no dependencies between any questions and therefore the successful completion of this question does not impact the ability to attempt any other question in this exam.
Information required to complete the tasks:
General Information;
* vRealize Automation FQDN: vr-aulomation.corp.local
* Cloud Administrator Username: vcapadmin@corp. local
* Cloud Administrator Password: VMware1!
* Project: Uranus
* Project Team Leader: vcapadmin@corp. local
* Blueprint Name: Uranus Server
* Deployment Name: Uranus-Check-Policies
Policy Information:
* Lease Policy name: Uranus - Lease Policy
* Lease Policy maximum lease period: 30 days
* Lease Policy maximum total lease period: 30 days
* Lease Policy grace period: 0 days
* Lease Policy scope: Uranus Project
* Day 2 Action Policy name: Uranus - Day 2 Actions Policy
* Approval Policy name: Uranus - Snapshot Approval Policy
To troubleshoot and resolve the issues for the Uranus Project, you should take the following steps:
Deployments Not Getting Deleted as per Lease Policy:
Snapshot Create Requests Not Received for Approval:
Option to Revert to Existing Snapshots Not Available:
After making the necessary changes, deploy the Uranus Server Catalog Item with the deployment name ''Uranus-Check-Policies'' to verify that all issues have been resolved. Monitor the deployment process and check if the lease policy is enforced, snapshot approval requests are generated, and developers can revert to existing snapshots as expected.
Security & Privacy
Satisfied Customers
Committed Service
Money Back Guranteed