At ValidExamDumps, we consistently monitor updates to the VMware 3V0-31.22 exam questions by VMware. Whenever our team identifies changes in the exam questions,exam objectives, exam focus areas or in exam requirements, We immediately update our exam questions for both PDF and online practice exams. This commitment ensures our customers always have access to the most current and accurate questions. By preparing with these actual questions, our customers can successfully pass the VMware Advanced Deploy VMware vRealize Automation 8.x (v2) exam on their first attempt without needing additional materials or study guides.
Other certification materials providers often include outdated or removed questions by VMware in their VMware 3V0-31.22 exam. These outdated questions lead to customers failing their VMware Advanced Deploy VMware vRealize Automation 8.x (v2) exam. In contrast, we ensure our questions bank includes only precise and up-to-date questions, guaranteeing their presence in your actual exam. Our main priority is your success in the VMware 3V0-31.22 exam, not profiting from selling obsolete exam questions in PDF or Online Practice Test.
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 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 5
As the Cloud Administrator, you have been tasked lo complete the following tasks tor the Pluto Project.
1. Configure the following on the network nsx-pluto-existing in the network profile called Pluto Networks
a. IPv4 CIDR: 172.16.17.0/24
b. IPv4 Gateway: 172.16.17.1
c Default Domain: corp.local d. Assign a Capability Tag:
* key: net
* value: existing
2. Define a new IP Range on the nsx-pluto-existing network that has the following configuration:
a. Network IP Range Name: pluto-existing-range b IP Range: 172.16.17.5-172.16.17.250
3. Assign a new capability tag to the sgPlutoDatabase Security Group:
a. key: sg
b. value: plutodatabase
4. Update the Pluto Networks Network Profile:
a. Ensure it only has the following networks assigned:
i. nsx-pluto-extemal
ii. nsx-pluto-existing
iii. nsx-pluto-outbound b Configure nsx-pluto-outbound as the external network for the network policy c. Assign a new capability tag to the Pluto Networks network profile:
i. key: net ii. value: pluto
To complete the tasks for the Pluto Project as a Cloud Administrator, you would follow these steps:
Task 1: Configure Network nsx-pluto-existing in Pluto Networks Profile
Access the vRealize Automation console.
Navigate toInfrastructure>Configure>Network Profiles.
Select the ''Pluto Networks'' profile.
Configure the network nsx-pluto-existing with the following settings:
IPv4 CIDR:172.16.17.0/24
IPv4 Gateway:172.16.17.1
Default Domain:corp.local
Assign a Capability Tag with key:netand value:existing.
Task 2: Define a New IP Range
Within the ''Pluto Networks'' profile, select the nsx-pluto-existing network.
Add a new IP Range with the following configuration:
Network IP Range Name:pluto-existing-range
IP Range:172.16.17.5-172.16.17.250
Task 3: Assign Capability Tag to sgPlutoDatabase Security Group
Locate the sgPlutoDatabase Security Group within the vRealize Automation console.
Assign a new capability tag to the security group with key:sgand value:plutodatabase.
Task 4: Update the Pluto Networks Network Profile
Ensure the Pluto Networks profile includes only the following networks:
nsx-pluto-external
nsx-pluto-existing
nsx-pluto-outbound
Configure nsx-pluto-outbound as the external network for the network policy.
Assign a new capability tag to the Pluto Networks network profile with key:netand value:pluto.
Please ensure to follow the specific steps and configurations as per your organization's standards and the vRealize Automation documentation for detailed instructions on each task
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 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.
