Free Google Apigee-API-Engineer Actual Exam Questions - Question 1 Discussion
root cause analysis found that key configurations were not promoted to production You want to
avoid similar release failures in your next release What should you do?
It’s B—automated smoke tests catch missing configs right after deployment fast.
B imo, smoke tests can catch these missing config issues right after deployment before users notice anything wrong. It’s a quick way to spot problems early, even if the configs are in source control or not.
Maybe D makes sense here because if the configurations aren’t checked into source control, then no amount of testing will catch them if they’re just missing from the deployment package. Without proper source control, the deployment process can’t promote everything needed. So making sure all config files are tracked and versioned in source control feels like the fundamental fix to prevent missing configs in production again. Automated tests (B) help but won't catch something that isn’t even in the build.
It’s B because running automated smoke tests can catch missing configs right after deployment, preventing those early errors from reaching users again.
Totally agree that just notifying operations (A) won’t fix the root cause. Automating checks with smoke tests (B) is key to catch missing configs before go-live. B feels more proactive here.
Option B makes sense here—running automated smoke tests would catch missing configs early in the release process instead of after users find errors. It’s a proactive way to spot issues fast.
D sounds right to me—if key configs aren’t in source control, they can easily get missed during deployment. That’s the root cause here.