VCP7-CMA Study Guide

This is my notes that I used to take my VCP7-CMA. Straight from the Exam Blueprint.

Section 1 – Create and Modify vRealize Automation Blueprints

Section 2 – Configure and Manage Tenants and Business Groups

Section 3 – Install and Configure vRealize Automation and Related Components

Section 4 – Configure and Manage the vRealize Automation Catalog

Section 5 – Configure and Administer Fabric Groups and Endpoints

Section 6 – Extend a vRealize Automation Implementation


VCP7-CMA – Objective 1.2

Disclaimer: These are my notes from taking the 2V0-731 exam. If something doesn’t make sense, please feel free to reach out.

The goal of this objective is to understand the XaaS functionality within vRA

Objective 1.2 – Create and Manage XaaS Blueprints with Custom Resource Mappings

  • Create and manage XaaS resources in vRealize Automation based on the design
    • Configure Active Directory plugin
    • Configure REST plugin
    • Configure PowerShell plugin
    • Configure SOAP plugin
    • Configure vCenter Server plugin
  • Create and manage custom resources
  • Create and manage XaaS Service Blueprints
    • Create a service blueprint form
    • Configure output parameters
    • Publish the blueprint
  • Create and manage XaaS resource actions
    • Create a service blueprint form
    • Configure output parameters
    • Publish the blueprint
  • Create and manage resource mappings with specific conditions


XaaS is a means of presenting vRO workflows through vRA.

When adding endpoints it’s important to use the vRA interface rather than vRO.

Administration – vRO Configuration – Endpoints – Add

You can only have one AD plugin configured, once the first one is added it disappears from the list and a message is displayed on the Type selection page.

AD Plugin Configured

Default timeouts for REST plugin are:

  • Connection – 30s
  • Operation – 60s

A Custom Resource is a definition of an object that is linked to an existing vRO object type, E.g. AD:User.

Once created you can create a blueprint to provision the object, ensuring the output is set to the custom resource.

Once vRO has provisioned the resource & vRA knows what resource it is. Resource actions can be run against those objects. E.g.

  • Disable user
  • Enable user
  • Destroy user

When creating workflows, set it to be available if certain conditions are met. So only allow disable if the user is enabled etc.

When destroying a provisioned resource, ensure the Disposal check box is ticked, otherwise can end up with orphaned items.

First thing to do when creating XaaS Blueprints is to select the vRO workflow that you’ll be running. Make a note of the Input/Output values for later.

On the General tab, give the Blueprint a sensible name & description. On the form, the bare minimum you need are the Input values from earlier, as without these the workflow will fail. Add anything else you need/want to the form and click next. Once you’re on the Provisioned Resource tab, select a defined Custom Resource as the output r choose No Provisioning.

A defined Custom Resource will give you the ability to perform Resource Actions on the provisioned object. No Provisioning will mean that you don’t have the ability to manage the object through vRA.

To create a Resource Action, you need to have created the Custom Resource first.


VCP7-CMA – Objective 1.1

Disclaimer: These are my notes from taking the 2V0-731 exam. If something doesn’t make sense, please feel free to reach out.

The goal behind this objective is to be familiar with Blueprint creation.

Objective 1.1 – Create, Modify and Publish Blueprints Based on a Given Design

  • Select the provisioning workflow, virtual machine template, and customization specification
  • Configure expiration and archive durations
  • Configure machine prefixes
  • Configure and manage networking components
  • Specify compute, memory, and storage resources
  • Configure custom properties and property groups
  • Create nested blueprints
  • Create and add software components
  • Publish blueprints


Permissions – A role with ‘architect’ in the title

Design – Blueprints, New.

Blueprint Creation

Give the blueprint a name and ID. Configure the lease duration – this is the time that the blueprint will be provisioned for before the archive period takes effect. If you choose different values for minimum and maximum then when requesting the blueprint it can be selected.

Lease – Duration the machine will be powered on and available

Archive – Duration the machine will be retained (powered off) once the lease period expires

NSX Settings are to define the transport zone and routing reservation policy. Properties is to define custom properties for the blueprint.

All the above can be edited after creation by clicking on the cog icon next to the blueprint name.

Edit Blueprint

Once created, choose the relevant component to drag the machine onto the design canvas. You can click on each item on the canvas to configure the appropriate settings.

On the machine itself you give the item a name, choose the reservation policy, machine prefix & number of VMs to provision. The machine prefix can be chosen as a specific item from a list or it can be set to the business group default.

Under Build information there’s a number of provisioning workflows depending on the action selected. The actions are:

  • Create
    • BasicVMWorkflow
    • ExternalProvisioningWorkflow
    • ImportOvfWorkflow
    • LinuxKickstartWorkflow
    • VirtualSccmProvisioningWorkflow
    • WIMImageWorkflow
  • Clone
    • CloneWorkflow
  • LinkedClone
    • CloneWorkflow
  • NetApp FlexClone
    • CloneWorkflow

When using Cloneworkflow – click on the ellipsis button to select the template to clone from & enter the customisation specification (NB: This is case sensitive)

Next is to configure the machine resources. These are the minimum and maximums that a user can select when requesting the blueprint.

Can add additional storage on the storage tab, configure the network on the network tab & add custom properties on the properties tab.

When Blueprints are saved they are in a draft state until they are published.

You can nest Blueprints to build up an application composed of other Blueprints. There are some behaviours that you should be familiar with when nesting. The high level is listed below, refer to the documentation link under references for more detail.

  • Settings defined in the outer Blueprint take precedence over settings in nested Blueprints
  • I couldn’t find any hard limits on how many levels of nesting you can use, however the recommendation is to keep to 3 levels to minimise complexity. This makes sense to me – Outer Blueprint, Machine Blueprint, Application Components
  • If a user is entitled to a Blueprint, they’re entitled to all the nested Blueprints contained within