Key details for this exam, checked against the published exam outline
Each question shows the correct answer and an explanation of why it is right
TASK 11
As the Cloud Administrator. you have been tasked with building a Continuous Integration/Continuous Development (CI/CD) pipeline for the Oberon Project. The requirements for this pipeline are:
* The pipeline should deploy the monolithic application. OberonWeb. only it approved by the project leader.
* The requestor should be able to specify the name of the deployment at the request time.
The following information is required to complete the task:
* vRealize Automation FODN: vr-automation.corp.local
* Cloud Administrator Username: [email protected]
* Cloud Administrator Password: VMware1!
Pipeline Information:
* Project Name: Oberon
* Pipeline Name: OberonWeb
* Pipeline inputs:
o deploymentName
* Stage Name: OberonWebApp
* Pipeline Tasks
o Deployment Task
o Approval Task
Approval Task Information:
* Task Name: Approval Task
* Approvers: vcapadmin@corp. local
* Summary: Approval Task
* Description:
o This is an approval for $(input. deploymentName)
Deployment Task Information:
* Task Name: Deployment Task
* Cloud Template Name: Oberon Web
* Version: 1
Deployment Name: Oberon Web App Test Important Notes:
* You must run the Pipeline, but do not approve the task
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 [email protected] 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.
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: [email protected]
* 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 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: [email protected]
* 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.
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: [email protected]
* 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 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: [email protected]
* 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 10
As the Cloud Administrator you have been tasked to troubleshoot and resolve the following issues raised by the developers on the Uranus Project:
* Developers have reported that Deployments are not getting deleted as per the company lease policy.
* The Uranus Project Team Leader is responsible for approving all snapshot create requests for deployments based only on the Uranus Server blueprint, however, they have received no requests so far.
* Developers have reported that they do not have the option to revert to existing snapshots for vSphere deployments.
Once you have completed your changes, deploy the Uranus Server Catalog Item to verify all the issues have been resolved.
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 not impact the ability to attempt any other question in this exam.
Information required to complete the tasks:
General Information;
* vRealize Automation FQDN: vr-aulomation.corp.local
* Cloud Administrator Username: vcapadmin@corp. local
* Cloud Administrator Password: VMware1!
* Project: Uranus
* Project Team Leader: vcapadmin@corp. local
* Blueprint Name: Uranus Server
* Deployment Name: Uranus-Check-Policies
Policy Information:
* Lease Policy name: Uranus - Lease Policy
* Lease Policy maximum lease period: 30 days
* Lease Policy maximum total lease period: 30 days
* Lease Policy grace period: 0 days
* Lease Policy scope: Uranus Project
* Day 2 Action Policy name: Uranus - Day 2 Actions Policy
* Approval Policy name: Uranus - Snapshot Approval Policy
To troubleshoot and resolve the issues for the Uranus Project, you should take the following steps:
Deployments Not Getting Deleted as per Lease Policy:
Snapshot Create Requests Not Received for Approval:
Option to Revert to Existing Snapshots Not Available:
After making the necessary changes, deploy the Uranus Server Catalog Item with the deployment name ''Uranus-Check-Policies'' to verify that all issues have been resolved. Monitor the deployment process and check if the lease policy is enforced, snapshot approval requests are generated, and developers can revert to existing snapshots as expected.
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: [email protected]
* 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.
Exam domains verified against: Official VMware 3V0-31.22 exam guide, last checked October 2026.
No testable objectives for this topic.
No testable objectives for this section.
No testable objectives for this section.
Learn how to perform clustered vRealize Automation deployments and modify directory settings. This domain covers adding cloud accounts, cloud zones, and configuring pricing cards for your deployment.
Sample question from this domain above: Q3
No testable objectives for this section.
Diagnose and resolve vRealize Automation deployment issues, catalog and blueprint provisioning errors, and integration problems. This domain includes troubleshooting projects, cloud resources, organization and service roles, and extensibility features.
Sample question from this domain above: Q4
Manage public clouds and cloud accounts, configure extensibility and cloud zones, and set up vRealize Operations workload placement. This domain also covers consuming NSX-T features within your automation environment.
Common questions about the exam itself
