PROFESSIONAL-CLOUD-DEVELOPER · Question #131
You are developing a new application that has the following design requirements: - Creation and changes to the application infrastructure are versioned and auditable. - The application and deployment
The correct answer is A. 1. Store the application and infrastructure source code in a Git repository. 2. Use Cloud Build to. Storing both application code and infrastructure-as-code (e.g., Terraform or Cloud Deployment Manager configs) in a Git repository satisfies the versioning and auditability requirement - every change is tracked with author, timestamp, and diff. Using Cloud Build, a fully Google-m
Question
You are developing a new application that has the following design requirements:
- Creation and changes to the application infrastructure are versioned
and auditable.
- The application and deployment infrastructure uses Google-managed
services as much as possible.
- The application runs on a serverless compute platform.
How should you design the application's architecture?
Options
- A
- Store the application and infrastructure source code in a Git repository. 2. Use Cloud Build to
- B
- Deploy Jenkins from the Google Cloud Marketplace, and define a continuous integration
- C
- Create a continuous integration pipeline on Cloud Build, and configure the pipeline to deploy
- D
- Deploy the application infrastructure using gcloud commands. 2. Use Cloud Build to define a
How the community answered
(32 responses)- A75% (24)
- B16% (5)
- C3% (1)
- D6% (2)
Explanation
Storing both application code and infrastructure-as-code (e.g., Terraform or Cloud Deployment Manager configs) in a Git repository satisfies the versioning and auditability requirement - every change is tracked with author, timestamp, and diff. Using Cloud Build, a fully Google-managed CI/CD service, to automatically build and deploy on commits ensures no manual steps bypass the audit trail and relies on Google-managed infrastructure. Deploying to a serverless platform (like Cloud Run or Cloud Functions) meets the serverless compute requirement. Option B (Jenkins from Marketplace) is self-managed, not a Google-managed service. Option C omits infrastructure versioning. Option D uses ad-hoc gcloud commands that are not inherently versioned or auditable.
Topics
Community Discussion
No community discussion yet for this question.