VMware Advanced Deploy VMware vRealize Automation 8.6 - 3V0-31.22 Exam Practice Test
Question 1
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
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
Correct Answer:
See the Explanation for complete Solution
Explanation:
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 to Design > Image Mappings and click New 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 to Design > Flavor Mappings and click New 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 to Design > Cloud Templates.
Click Import and select the provided file jupiter.yaml to 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.
Use the YAML code editor to add an inputs section where users can select the machine size and operating system image at deployment time34.
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
Explanation:
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 to Design > Image Mappings and click New 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 to Design > Flavor Mappings and click New 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 to Design > Cloud Templates.
Click Import and select the provided file jupiter.yaml to 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.
Use the YAML code editor to add an inputs section where users can select the machine size and operating system image at deployment time34.
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
Question 2
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
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:
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.
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.
