Limited-Time Offer: Enjoy 50% Savings! Ends in 00h 00m 00s Coupon code: 50OFF
Skip to content
Login Sign up

Free VMware Advanced Deploy VMware vRealize Automation 8.x (v2) 3V0-31.22 Exam Questions

Page: 1 / 2 Total 12 questions

Want more questions? Get Premium Access.

Question 1

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

Correct Answer: A. See the Explanation for complete Solution
Explanation:

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.


Question 2

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

Correct Answer: A. See the Explanation for complete Solution
Explanation:

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

Ensure that VMware vRealize Operations is integrated with vRealize Automation for advanced workload placement1.

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.


Question 3

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

Correct Answer: A. See the Explanation for complete Solution
Explanation:

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.


Question 4

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

Correct Answer: A. See the Explanation for complete Solution
Explanation:

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.

Run the workflow namedAdd a vCenter Server instanceto include the vCenter Server in the vRO inventory123.

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.


Question 5

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

Correct Answer: A. See the Explanation for complete Solution
Explanation:

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


Question 6

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!

Correct Answer: A. See the Explanation for complete Solution
Explanation:

To complete the tasks as a Cloud Administrator, follow these steps:

Task 1: Onboard New Interns into vRealize Automation

Log in to the Identity Manager (IDM) using the provided URL and credentials.

Navigate toIdentity & Access Management.

UnderEnterprise Groups, find and selectinterns-group-aandinterns-group-b.

Assigninterns-group-awith the role ofCloud Assembly User, which is the most restrictive access for Cloud Assembly.

Assigninterns-group-bwith the role ofService Broker User, which is the most restrictive access for Service Broker.

Ensure that the AD Organization Unit is correctly set toOU=Interns,DC=corp,DC=localfor proper group synchronization.

Task 2: Resolve Access Permissions Issues

Log in to the vRealize Automation URL using the Cloud Administrator credentials.

Go toIdentity & Access Management.

Locate the user with the logon idappdevuser2@corp.local.

Assign this user the role ofCloud Assembly Userto allow creating and deploying from cloud templates in Cloud Assembly.

Verify that the user has the minimum permissions required and does not have any additional roles that exceed their responsibility.

By following these steps, you should be able to onboard the interns with the correct access and resolve the access permissions issues for the specified user. Always ensure to adhere to the principle of least privilege, granting users the minimum level of access necessary to perform their roles.


Page: 1 / 2 Total 12 questions