Most Recent VMware 3V0-31.22 Exam Questions & Answers

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

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.

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.

To complete Task 6 for the Saturn Project, follow these steps:

Step 1: Create an ABX Action

Log in to the vRealize Automation console athttps://vr-automation.corp.localusing the provided credentials.

Navigate toExtensibility>Actions.

Click onNew Action.

Enter theAction Nameas ''Saturn-Python-Script''.

Select theScripting Languageas Python and theFaaS Provideras On-Prem.

Use theImport Packageoption to upload the content of the Python script from ''C:\Exam Files\Question 6\Satum Python Script.txt''.

Save the action.

Step 2: Create a Subscription

Go toExtensibility>Subscriptions.

Click onNew Subscription.

Enter theSubscription Nameas ''Execute-Python-Script''.

Set theEvent Topicto trigger after the compute resource gets provisioned, which is typically the ''Compute Provision'' event.

Define theConditionsfor the subscription:

The Cloud Template is ''Saturn Ubuntu 18'' only.

The action should trigger only for the current project.

Save the subscription.

Ensure that the conditions for the subscription match the exact criteria needed for the Saturn Project. The action will now be triggered automatically under the specified conditions after the compute resource is provisioned.

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.