PROFESSIONAL-CLOUD-DEVOPS-ENGINEER Question #1: Real Exam Question with Answer & Explanation

Question

You have a CI/CD pipeline that uses Cloud Build to build new Docker images and push them to Docker Hub. You use Git for code versioning. After making a change in the Cloud Build YAML configuration, you notice that no new artifacts are being built by the pipeline. You need to resolve the issue following Site Reliability Engineering practices. What should you do?

Options

• ADisable the CI pipeline and revert to manually building and pushing the artifacts.
• BChange the CI pipeline to push the artifacts is Container Registry instead of Docker Hub.
• CUpload the configuration YAML file to Cloud Storage and use Error Reporting to identify and fix
• DRun a Git compare between the previous and current Cloud Build Configuration files to find and

Explanation

When a CI/CD pipeline fails after a configuration change, SRE best practice is to use version control to identify the problematic change. This allows for quick diagnosis or rollback to restore functionality.

Common mistakes.

• A. Disabling the CI pipeline and reverting to manual processes goes against automation principles and is not a resolution, but a workaround that reduces reliability and efficiency.
• B. Changing the artifact destination is irrelevant to a pipeline not building artifacts due to a configuration error and does not address the root cause of the build failure.
• C. Uploading the YAML to Cloud Storage and using Error Reporting might help with general logging but doesn't specifically target comparing versions of a configuration file to pinpoint a recent change as effectively as Git.

Concept tested. SRE incident management, version control, troubleshooting CI/CD

Reference. https://git-scm.com/docs/git-diff

No community discussion yet for this question.