Sample question 1 · Troubleshooting (22%)
Pinnacle Mutual, a small specialty insurance firm operating in a single region, recently migrated its policy administration workloads to a cloud provider using a GitOps model. During a scheduled DR tabletop, the team attempts to execute a rollback of the policy-rating microservice to the previous stable release after a simulated failed deployment. The rollback pipeline triggers but fails with: 'Image tag v2.1.4 not found in registry.' The team discovers that the container image registry has a 30-day retention policy that automatically purged the v2.1.4 image, which was 34 days old. The current broken deployment (v2.1.5) cannot process claims correctly, and the next stable image available is v2.0.9, which is 90 days old and predates a critical regulatory data-masking update. Given the registry retention gap and the regulatory constraint on the v2.0.9 image, which rollback strategy BEST balances operational recovery with compliance requirements?
- A. Deploy v2.0.9 immediately to restore service availability, accepting the regulatory data-masking gap as a temporary risk until v2.1.4 can be rebuilt.
- B. Rebuild the v2.1.4 image from the tagged Git commit in source control, push it to the registry with a protected retention policy, validate it in a staging environment, then deploy it as the rollback target.
- C. Roll forward by hotfixing v2.1.5 in production directly without a staging validation step to minimize claims processing downtime.
- D. Restore the v2.1.4 image from the cloud provider's object storage backup of the registry without verifying the image digest against the original build artifact.
View answer & explanation
Correct answer: B. Rebuild the v2.1.4 image from the tagged Git commit in source control, push it to the registry with a protected retention policy, validate it in a staging environment, then deploy it as the rollback target.
[Domain 5 - Troubleshooting, Subtopic 5 - Troubleshooting - Area 1 - Pipeline errors] Core Concept: Troubleshoot deployment and automation failures. centers on pipeline errors as defined in the official (ISC)² exam outline. Correct Answer (B): Rebuild the v2.1.4 image from the tagged Git commit in source control, push it to the registry with a protected retention policy, validate it in a staging environment, then deploy it as the rollback target. Why the other options are incorrect: Option A: Deploying v2.0.9 restores service availability but violates the regulatory data-masking requirement, creating a compliance exposure that may trigger regulatory penalties for Pinnacle Mutual during an already-scrutinized DR exercise. Option C: Hotfixing v2.1.5 directly in production without staging validation introduces additional risk to an already broken deployment and does not constitute a rollback — it is a forward fix that may compound the original defect if the root cause is not fully understood. Option D: Restoring an image from object storage without verifying the digest against the original build artifact cannot confirm the image has not been tampered with or corrupted, violating supply chain integrity principles and potentially deploying an unvalidated binary to production.