Answer-first summary for fast verification
Answer: Run a Git compare between the previous and current Cloud Build Configuration files to find and fix the bug.
The correct approach to resolve the issue following Site Reliability Engineering (SRE) practices involves identifying and fixing the root cause of the problem without resorting to manual processes or changing the artifact repository without necessity. Option D is the correct choice because it involves using version control to compare the previous and current configurations to identify what changes might have caused the pipeline to stop building new artifacts. This method is systematic, leverages existing tools (Git), and aligns with SRE practices by focusing on automation and reliability. Options A and B suggest manual intervention or unnecessary changes to the pipeline's configuration, which do not address the root cause. Option C, while it might help in identifying errors, does not directly leverage the version control system to pinpoint the configuration change that caused the issue.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
You have a CI/CD pipeline that uses Cloud Build to build Docker images and push them to Docker Hub, with Git for version control. After modifying the Cloud Build YAML configuration, you observe that no new artifacts are being generated by the pipeline. Following Site Reliability Engineering (SRE) best practices, how would you troubleshoot and resolve this issue?
A
Disable the CI pipeline and revert to manually building and pushing the artifacts.
B
Change the CI pipeline to push the artifacts is Container Registry instead of Docker Hub.
C
Upload the configuration YAML file to Cloud Storage and use Error Reporting to identify and fix the issue.
D
Run a Git compare between the previous and current Cloud Build Configuration files to find and fix the bug.
No comments yet.