最新的VMware Advanced Deploy VMware vRealize Automation 8.6 - 3V0-31.22免費考試真題
問題1
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: [email protected]
* 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
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: [email protected]
* 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
正確答案:
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 to Library > Workflows and search for workflows related to vCenter configuration.
Run the workflow named Add a vCenter Server instance to include the vCenter Server in the vRO inventory123.
Task 2: Troubleshoot and Resolve Workflow Issues
Review the workflow named Create a Saturn Snapshot for 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 machine core-A and the name q7.
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.
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 to Library > Workflows and search for workflows related to vCenter configuration.
Run the workflow named Add a vCenter Server instance to include the vCenter Server in the vRO inventory123.
Task 2: Troubleshoot and Resolve Workflow Issues
Review the workflow named Create a Saturn Snapshot for 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 machine core-A and the name q7.
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.
問題2
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
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
正確答案:
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 to Infrastructure > Configure > Cloud Zones.
Click New 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 to Administration > Projects.
Click New Project.
Provide the Project Name: "Mercury".
Under Project Administrators, add the "Project Mercury Admins" group.
Under Project Members, add the "Project Mercury Users" group.
In the Cloud Zones section, select the previously created "Mercury AWS Cloud Zone" and any other required zones.
Save the project.
Task 3: Update the Default Pricing Card
Navigate to Infrastructure > Pricing Cards.
Select the default pricing card and click Edit.
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.
Explanation:
Task 1: Create a New Cloud Zone
Log in to the vRealize Automation console as a Cloud Administrator.
Navigate to Infrastructure > Configure > Cloud Zones.
Click New 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 to Administration > Projects.
Click New Project.
Provide the Project Name: "Mercury".
Under Project Administrators, add the "Project Mercury Admins" group.
Under Project Members, add the "Project Mercury Users" group.
In the Cloud Zones section, select the previously created "Mercury AWS Cloud Zone" and any other required zones.
Save the project.
Task 3: Update the Default Pricing Card
Navigate to Infrastructure > Pricing Cards.
Select the default pricing card and click Edit.
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.
