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 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 4
As the Cloud Administrator, you have received the following request to make the changes in vRealize Automation to support new service capabilities.
1. Create a Storage Tier to support encryption.
2. Create a Network Profile for Phobos Project.
* Choose the NSX-T network from the available list.
3. The existing Phobos Zone should offer the following capabilities
* Initial workload placement should use VMware vRealize Operations and all workloads should be placed into a specific virtual machine folder by default.
The following information has been provided to assist you in these tasks:
The following information has been provided to assist you in these tasks:
* vRealize Automation URL: vr-automation.corp.local
* Cloud Admin Username: vcapadmin@corp.local
* Cloud Admin Password: VMware1!
Storage Profile Settings:
* Name: Encrypted Storage Tier
* Disk Type: Standard disk
* Region: vSphere Private Cloud / Local Dat
. Datastore/Cluster: RegionAOUSCSIOI-CC3'
* Provisioning Type: Thin
* Supports Encryption: Yes
* Capability Tag:
o Key: storage
o Value: encrypted
Network Profile Settings:
* Name: Phobos Networks
* Region: vSphere Private Cloud / Local Datacenter
* Network Segment: nsx-phobos-external
* Network IPv4 CIDR: 172.16.15.0/24
* Network Default Gateway: 172.16.15.1
* Domain: cofp.local
* IP Range Name: Phobos-range
* IP Range: 172.16.15.5-172.16.15.250
* Network Profile Capability Tag:
o Key: net
o Value: phobos
Cloud Zone Settings:
* Name: Phobos
* Folder: Workloads
To support the new service capabilities in vRealize Automation, you will need to perform the following tasks:
Task 1: Create a Storage Tier to Support Encryption
Log in to the vRealize Automation console using the provided Cloud Admin credentials.
Navigate toInfrastructure>Configure>Storage Profiles.
ClickNew Storage Profile.
Enter theNameas ''Encrypted Storage Tier''.
Set theDisk Typeto ''Standard disk''.
Choose theRegionas ''vSphere Private Cloud / Local Datacenter''.
Select theDatastore/Clusteras ''RegionA01USCSIOI-CC3''.
ForProvisioning Type, select ''Thin''.
EnsureSupports Encryptionis set to ''Yes''.
Add aCapability Tagwith Key as ''storage'' and Value as ''encrypted''.
Save the storage profile.
Task 2: Create a Network Profile for Phobos Project
In the vRealize Automation console, go toInfrastructure>Configure>Network Profiles.
ClickNew Network Profile.
Provide theNameas ''Phobos Networks''.
Set theRegionto ''vSphere Private Cloud / Local Datacenter''.
UnderNetwork Segment, choose ''nsx-phobos-external''.
Enter theNetwork IPv4 CIDRas ''172.16.15.0/24''.
Set theNetwork Default Gatewayto ''172.16.15.1''.
Specify theDomainas ''corp.local''.
Go to theIP Rangestab and add a new range named ''Phobos-range'' with the range ''172.16.15.5-172.16.15.250''.
Add aNetwork Profile Capability Tagwith Key as ''net'' and Value as ''phobos''.
Save the network profile.
Task 3: Configure Workload Placement for Phobos Zone
In the vRealize Automation console, navigate toInfrastructure>Cloud Zones.
Locate and edit the existing cloud zone named ''Phobos''.
In thePlacement Policysection, set it to use VMware vRealize Operations.
Specify the default virtual machine folder for workload placement as ''Workloads''.
Save the changes to the cloud zone.
By completing these steps, you will have created a storage tier that supports encryption, a network profile for the Phobos Project, and configured the Phobos Zone to offer advanced capabilities using VMware vRealize Operations. Always ensure to follow your organization's best practices and security policies when making changes to the infrastructure.
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 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.
