VMware Advanced Deploy vRealize Automation 8.x (v2) 3V0-31.22 Dumps in PDF

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 2
As a Cloud Administrator you have two tasks to complete:
1. Onboard new interns into vRealize Automation and assign the correct access. The Interns are split into two Active Directory groups, interns-group-a and interns-group-b. The interns-group-a group requires access to Cloud Assembly and the interns-group-b group requires access to Service Broker. The interns should be allocated the most restrictive access available. 2 Assist in resolving issues reported by the following users who do not have the correct access permissions in vRealize Automation. Each user should have the minimum permissions required to fulfill their role:
- A User with logon id appdevuset2@corp.local is only responsible for creating new and deploying from cloud templates in Cloud Assembly.
The following additional information is provided to help complete both tasks:
- IDM URL: https://identity-manager.corp.tocal/SAAS/admin or use bookmark

- IDM System Domain Username: admin
- IDM Admin Password: VMware1!
- AD Organization Unit ON: OU=lnterns.DC=corp.DC=local - vRealize Automation URL: vr-automalion.corp.local - Cloud Administrator Username: vca pad mm @corp. local - Cloud Administrator Password: VMware1!

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.

A) Create the second Cloud template based on the imported Cloud Template with the following requirements:
B) 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

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

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:
C) 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:
D) key: sg
E) value: plutodatabase

4. Update the Pluto Networks Network Profile:
F) Ensure it only has the following networks assigned:
G) 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:
H) key: net ii. value: pluto