- 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: | September 11, 2025 |
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 12
As the Cloud Administrator, you have been tasked to update the Atlas App cloud template in the Atlas project. Perform the following tasks:
1. Edit the existing cloud template Atlas App. such that it is a multi-tier application that meets the following requirements:
* 2 Web servers
* 1 Database server
* The Database server is always built before the Web servers
* 2 NSX Networks:
o The first network should use the NAT feature
* Resource Name: external
* Second network should be an existing network
* Resource Name: internal o All networks should be restricted to use only the Atlas project networks
o The internal network should be restricted to use only the nsx-atlas-existing NSX network
* Both the web and db VMs should be connected to the internal network
2. Add an NSX load balancer to provide access from the outside to the two Web servers:
* Resource Name: IbWeb
* Port: 443
* Protocol: HTTPS
3. Assign an existing Security Group to the Web servers:
* Resource Name: sgWeb
* Instances: Web Sewers
* Constraint Tag Key: sg
* Constraint Tag Value: atlasweb
To update the Atlas App cloud template to meet the specified requirements, you would perform the following steps in vRealize Automation:
Task 1: Edit the Cloud Template for Multi-tier Application
Access the vRealize Automation console and navigate to Design > Cloud Templates.
Open the existing cloud template named ''Atlas App''.
Modify the template to include:
2 Web Server Instances: Define two instances of the web server component.
1 Database Server Instance: Define a single instance of the database server component.
Build Order: Ensure the database server is set to be built before the web servers by adjusting the dependsOn property.
2 NSX Networks:
External Network (NAT): Create a network resource with the name external and configure it to use NAT.
Internal Network (Existing): Create a network resource with the name internal and link it to the existing nsx-atlas-existing network.
Restrict Networks: Apply constraints to ensure that only networks associated with the Atlas project are used.
Task 2: Add NSX Load Balancer
In the cloud template, add an NSX load balancer resource with the name lbWeb.
Configure the load balancer to distribute traffic to the web servers on port 443 using the HTTPS protocol.
Task 3: Assign Security Group to Web Servers
Define a security group resource with the name sgWeb.
Assign this security group to the web server instances.
Use constraint tags with the key sg and value atlasweb to ensure the security group is applied correctly.
Here is a simplified example of what the YAML configuration might look like:
resources:
dbServer:
type: Cloud.Machine
properties:
...
webServer1:
type: Cloud.Machine
properties:
dependsOn: dbServer
...
webServer2:
type: Cloud.Machine
properties:
dependsOn: dbServer
...
external:
type: Cloud.Network
properties:
networkType: nat
...
internal:
type: Cloud.Network
properties:
networkType: existing
constraints:
- tag: 'nsx-atlas-existing'
...
lbWeb:
type: Cloud.LoadBalancer
properties:
port: 443
protocol: HTTPS
...
sgWeb:
type: Cloud.SecurityGroup
properties:
instances: [webServer1, webServer2]
constraints:
- tag: 'sg:atlasweb'
...
Make sure to adjust the properties and configurations as needed to fit the specific details of your environment and the Atlas project. After updating the cloud template, validate the changes and ensure that the template meets all the requirements before saving.
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.
TASK 11
As the Cloud Administrator. you have been tasked with building a Continuous Integration/Continuous Development (CI/CD) pipeline for the Oberon Project. The requirements for this pipeline are:
* The pipeline should deploy the monolithic application. OberonWeb. only it approved by the project leader.
* The requestor should be able to specify the name of the deployment at the request time.
The following information is required to complete the task:
* vRealize Automation FODN: vr-automation.corp.local
* Cloud Administrator Username: vcapadmin@corp.local
* Cloud Administrator Password: VMware1!
Pipeline Information:
* Project Name: Oberon
* Pipeline Name: OberonWeb
* Pipeline inputs:
o deploymentName
* Stage Name: OberonWebApp
* Pipeline Tasks
o Deployment Task
o Approval Task
Approval Task Information:
* Task Name: Approval Task
* Approvers: vcapadmin@corp. local
* Summary: Approval Task
* Description:
o This is an approval for $(input. deploymentName)
Deployment Task Information:
* Task Name: Deployment Task
* Cloud Template Name: Oberon Web
* Version: 1
Deployment Name: Oberon Web App Test Important Notes:
* You must run the Pipeline, but do not approve the task
To build the CI/CD pipeline for the Oberon Project with the specified requirements, you would perform the following steps in vRealize Automation:
Log in to the vRealize Automation console at vr-automation.corp.local using the provided Cloud Administrator credentials.
Navigate to the Code Stream service to access the pipeline management features.
Create a new pipeline with the name ''OberonWeb'' within the ''Oberon'' project.
Define the pipeline inputs to include deploymentName, which allows the requestor to specify the name of the deployment at request time.
Add a stage to the pipeline named ''OberonWebApp''.
Within the stage, add two tasks:
Deployment Task: Configure this task to deploy the ''Oberon Web'' cloud template, specifying the version as 1.
Approval Task: Set up this task with the name ''Approval Task'', and assign vcapadmin@corp.local as the approver. The summary should be ''Approval Task'', and the description should include the dynamic reference to the input deployment name, such as ''This is an approval for $(input.deploymentName)''.
Ensure that the Approval Task precedes the Deployment Task within the pipeline to enforce that the deployment only occurs after approval by the project leader.
Save the pipeline configuration.
Run the pipeline by initiating a new pipeline execution and providing a test deployment name when prompted, such as ''Oberon Web App Test''.
Do not approve the deployment when the Approval Task is triggered, as per the instructions.
By following these steps, you will have configured a CI/CD pipeline that meets the requirements of deploying the OberonWeb application only after approval by the project leader, and allows the requestor to specify the deployment name at the time of the request.
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.
Security & Privacy
Satisfied Customers
Committed Service
Money Back Guranteed