3V0-31.22 Exam Questions & Answers
Advanced Deploy VMware vRealize Automation 8.x (v2) • VMware
100% money-back guarantee
Sample 3V0-31.22 Questions
Practice with real exam-style questions, each with the verified correct answer and explanation.
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 6
As the Cloud Administrator for the Saturn Project, you have been tasked to:
1. Create an ABX Action
2. Create a subscription to trigger the action only if the following conditions are met:
a. The Cloud Template is Saturn Ubuntu 18 only.
b The action should fire immediately after the compute resource gets provisioned.
c. The action should trigger only for the current project.
Additional Information required to complete the tasks:
* URL: https://vr-automation.corp.local
* Username: vcapadmin@corp.local
* Password: VMware1!
* Action Name: Saturn-Python-Script
* Python Script Content: "C:\Exam Files\Question 6\Satum Python Script.txt'
* FaaS Provider: On-Prem
* Subscription Name: Execute-Python-Script
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.
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
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.
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.
TASK 8
As the Cloud Administrator, you must ensure that each virtual machine deployed by the Neptune Project is configured to a standard state.
You have already created a state file in the environment that can be used to meet this requirement.
The following tasks need to be completed:
Update the existing Neptune VMware Cloud Template to ensure that:
* The vRealize Automation SaltStack Config minion is installed during deployment.
* The base configuration state file is always run during deployment. The minion id of the machine should be dynamically assigned using the machine name.
* A secret should be used to ensure the remote access password is not visible within the cloud template.
NOTE: Do not deploy the Cloud template.
The following information has been provided to assist you in these tasks:
The following information has been provided to assist you in these tasks:
* vRA FQDN: vt-aulomation.corp.local
* Cloud Admin Username: vcapadmin@corp.local
* Cloud Admin Password: VMwarel!
* vRA Project Name: Neptune
* Existing Cloud Template Name: Neptune Ubunlu
* vRA-SSC Master Minion Id: saltstack
* vRA-SSC Master Id: saltstack_enterprise_installer
* vRA-SSC Environment: sse
* State File Location: /neptune/base/init.sls
* Remote Access Username: salt-user
* Remote Access Password: VMware1
* Password Secret name: salt-password
To update the existing Neptune VMware Cloud Template with the requirements for the Neptune Project, you would follow these steps:
Install the vRealize Automation SaltStack Config Minion During Deployment:
Open the existing Neptune Ubuntu Cloud Template in the vRealize Automation Cloud Assembly.
In the code pane, add the following properties to the SaltStack Config resource:
Cloud_SaltStack_1:
type: Cloud.SaltStack
properties:
masterId: saltstack_enterprise_installer
hosts:
- '${resource.Cloud_VM_1.id}'
saltEnvironment: sse
stateFiles:
- /neptune/base/init.sls
Dynamically Assign the Minion ID Using the Machine Name:
By default, the machine's name is passed in as the minion ID in SaltStack Config. Ensure that the machine names are appropriately set to be used as minion IDs.
Use a Secret for the Remote Access Password:
Refer to the secret directly in your Cloud Assembly cloud template by using the prefixsecret.and the name of your property:
inputs:
...
resources:
Cloud_Machine_1:
type: Cloud.Machine
properties:
...
remoteAccess:
authentication: usernamePassword
username: salt-user
password: '${secret.salt-password}'
By incorporating these changes, the Neptune VMware Cloud Template will install the SaltStack Config minion during deployment, run the base configuration state file, and use a secret to secure the remote access password.
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
Get access to all 12 verified questions with detailed answers.
Unlock All 3V0-31.22 Questions