2V0-31.23 · Question #51
The CTO updates the company's tagging policy to require that all newly deployed machines include a tag with the operating system type deployed (i.e. ostype:windows or ostype:linux ). Following new…
The correct answer is B. Unrelease version 1.0 of the blueprint. C. Update the correct content source. Releasing version 1.1 to the catalog did not automatically unrelease version 1.0 - in Aria Automation (vRA), each blueprint version is independently released, so both 1.0 and 1.1 appear as separate catalog options until the old one is explicitly unreleased. B fixes this by…
Question
The CTO updates the company's tagging policy to require that all newly deployed machines include a tag with the operating system type deployed (i.e. ostype:windows or ostype:linux ). Following new guidance, an administrator responsible for creating blueprints in the App-Dev project successfully updates the Multi-Cloud-Windows blueprint to include the ostype:windows tag on the Cloud.Machine resource. Following a successful test from the blueprint canvas, the administrator creates a new version of the blueprint and checks the "Release this version to the catalog" checkbox to release it to Service Broker. Finally, the administrator successfully updates the Service Broker content source so that the other members of the App-Dev project can deploy the latest version of the blueprint. The next day, project members report that there is an option to choose which of two versions (1.0 and 1.1) of the blueprint they wish to deploy. Which two tasks should the administrator complete to ensure only the latest released version of the catalog item is displayed? (Choose two.)
Options
- AUnrelease version 1.1 of the blueprint.
- BUnrelease version 1.0 of the blueprint.
- CUpdate the correct content source.
- DRestore version 1.0 of the blueprint.
- EEnsure the blueprint is shared with the App-Dev project.
How the community answered
(39 responses)- A10% (4)
- B85% (33)
- D3% (1)
- E3% (1)
Explanation
Releasing version 1.1 to the catalog did not automatically unrelease version 1.0 - in Aria Automation (vRA), each blueprint version is independently released, so both 1.0 and 1.1 appear as separate catalog options until the old one is explicitly unreleased. B fixes this by unreleasing 1.0, removing it from the catalog view. C is required because after changing the release state of a blueprint version, the Service Broker content source must be re-synced (imported/updated) so it reflects the current state - without this step, the catalog may still show stale version data.
A is wrong because unreleasing 1.1 removes the correct, updated version - the opposite of the goal. D is a distractor; restoring 1.0 would revert the blueprint itself and undo the tag work entirely. E is wrong because the sharing is already working - members can already see the item; the issue is they see too many versions, not an access problem.
Memory tip: Think "retire the old, refresh the source" - you must manually unrelease outdated versions (B) AND sync the content source (C), because neither happens automatically when you release a new version.
Topics
Community Discussion
No community discussion yet for this question.