Answer-first summary for fast verification
Answer: Cloud Build with Packer
The correct solution is Cloud Build with Packer (Option A) because Packer is designed to build identical machine images for multiple cloud platforms (e.g., Compute Engine, AWS, Azure) from a single configuration, which aligns with the requirement for custom VM image deployment in a multi-cloud environment. Cloud Build automates the CI/CD pipeline, executing Packer for image builds and enabling deployment steps (e.g., via scripts). This stack is adaptable to future changes, as Packer supports various cloud providers and can be easily updated for new environments. Options B, C, and D are incorrect: B and C are limited to Google Cloud and container-based deployments, and D is Kubernetes-specific and unrelated to VM images.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
You are setting up a CI/CD pipeline for your application in a multi-cloud environment. The application is deployed using custom Compute Engine images and their equivalents in other cloud providers. You need a solution that can build and deploy these images to your current environment while remaining adaptable to future changes. Which solution stack should you implement?
A
Cloud Build with Packer
B
Cloud Build with Google Cloud Deploy
C
Google Kubernetes Engine with Google Cloud Deploy
D
Cloud Build with kpt
No comments yet.