Answer is D & E the version is an option only if multiple exist the project and deployment name is a mandatory selection. Procedure Click Catalog. The available catalog items are available to you based on your project membership. Locate the catalog item you plan to deploy. You can use the filter, search, or sorting options to find the catalog item. Click Request. Provide any required information. If the blueprint has more than one released version, select the version that you want to deploy. A deployment name is required, as is a project. The project list includes those that you are a member of. The form might have other options that you must configure, depending on how the blueprint was designed. Click Submit. The provisioning process begins and the Deployments tab opens with your current request at the top.

D. Project E. Deployment name A deployment name is required, as is a project. The project list includes those that you are a member of.

Toast and Jarratt are correct

Answer is DE VMware Aria Automation Consumption offers the default form with minimal options. Administrators can use the Custom Form feature to customize the request form. The minimal options are Version, Project, and Deployment. However, only Project and Deployment are shown with the symbol (*) in front which means the field is mandatory. Taken from Aria Automation ICM 8.10 Lesson Book -> Request Forms

I'm logged into vRA 8.3 on-prem, in Service Broker, performing a new request against a VM catalog item. I see the version number is already set (not marked as required), whereas 'Project' and 'Deployment Name' are marked as required. The reason this question can be tricky is that if you are in Assembly deploying a blueprint, the required options are Version and Deployment Name. The key here is the callout that you are deploying a "Catalog Item".

D and E

D and E

D and E