VMware Aria Automation 8.x Professional — Question 1
An administrator successfully creates a new VMware Aria Automation template in VMware Aria Automation Assembler for the DevOps project. The administrator is ready to publish the automation template so that the DevOps team can use the catalog for self-service requests.
The administrator is trying to import the automation template into VMware Aria Automation Consumption through the correct content source type. After creating the content source, the administrator cannot find the new automation template listed in order to import it.
What might be the cause of this issue?
Answer options
- A. The administrator did not test the automation template provisioning logic.
- B. The administrator did not select the ‘Release this version to the catalog’ checkbox.
- C. The administrator did not change the automation template to a shared automation template.
- D. The administrator did not create a version of the automation template.
Correct answer: B
Explanation
The correct answer is B because failing to select the ‘Release this version to the catalog’ checkbox means the template is not marked for public use, making it unavailable for import. Options A, C, and D do not directly affect the visibility of the template in the catalog for import, as the template can still exist without testing or being shared.