2V0-31.23 · Question #49
An administrator creates a new multi-cloud blueprint for the App-Dev team. The initial requirements for the multi-cloud blueprint were: - All components must connect to a single network. - The…
The correct answer is A. Restore version 1.0 of the blueprint. Restoring version 1.0 is the correct first step because Cloud Assembly's blueprint versioning allows administrators to instantly revert to any previously published stable version directly from the design canvas, making it the fastest path back to a known-good state without…
Question
An administrator creates a new multi-cloud blueprint for the App-Dev team. The initial requirements for the multi-cloud blueprint were:
- All components must connect to a single network.
- The requestor must be able to select the image to be deployed.
- The requestor must be able to select to which cloud to deploy.
- The requestor must be able to select the number of machines to be deployed.
The administrator creates the blueprint and releases version 1.0 to the catalog. The App-Dev team decides to make some changes to the multi-cloud blueprint to include the following additional requirement:
- All machines must be deployed behind a load balancer.
An App-Dev administrator makes the required changes and publishes a new version of the blueprint. Upon receiving reports of issues, the administrator opens the multi-cloud blueprint and finds changes have been made. Testing of the newest version fails. From within the Cloud Assembly blueprint design canvas, which step should the administrator take first to get the blueprint back to a stable state?
Options
- ARestore version 1.0 of the blueprint.
- BCreate a new version of the blueprint.
- CDownload the blueprint in YAML.
- DClone the blueprint to a new blueprint.
How the community answered
(66 responses)- A79% (52)
- B12% (8)
- C6% (4)
- D3% (2)
Explanation
Restoring version 1.0 is the correct first step because Cloud Assembly's blueprint versioning allows administrators to instantly revert to any previously published stable version directly from the design canvas, making it the fastest path back to a known-good state without trial-and-error debugging. Option B (creating a new version) would only snapshot the current broken state, not fix it. Option C (downloading the YAML) is useful for backup or external editing, but doesn't resolve the instability on its own. Option D (cloning to a new blueprint) creates a copy of the broken version, which doesn't help restore stability in the original.
Memory tip: Think "restore before rebuild" - when a published version breaks, always check version history first. Cloud Assembly keeps a full audit trail of published versions, so rolling back is faster than rewriting.
Topics
Community Discussion
No community discussion yet for this question.