LEARN. PRACTICE. GROW.Concept and mechanism
The management plane configures resources and can change data-plane protections. Protecting a public API is insufficient if the console changing networks, identities, and logs retains excessive privilege. Assess tenant isolation through suitable controls and tests without assuming physical sharing proves failure or separate contracts prove isolation. In networking, review ingress and egress against necessary flows and dependencies. Broad egress may exceed requirements, but blocking everything without understanding DNS and integrations can also interrupt service. Changes should preserve legitimate communication and demonstrate denial of unauthorized paths.
Guided application
In the fictional conceptual lab, a generic ephemeral volume uses reclaimPolicy Retain. Removing the pod and PVC does not establish storage cleanup; the volume may need separate treatment. In DR, volume existence also does not demonstrate that the APS role can use the key or resolve dependencies. Measure accepted service: forty-five minutes of restoration, twenty of validation, and ten of reconciliation in sequence total seventy-five. Against a sixty-minute RTO, the gap is fifteen minutes. For RPO, failure at ten thirty with a recoverable point at ten eighteen means twelve minutes of potential loss. Keep metrics, execution identity, dependencies, and evidence together in acceptance planning.
Retain requires cleanup verification; 45 + 20 + 10 = 75 minutes to acceptance in the exercise.
Common pitfalls
Ephemeral as sanitization; distributed compute as complete DR; listed volume as recoverable; objective as measurement.
Related topics: Architecture, responsibilities, and portability · Versions, retention, and holds · Data protection, location, and classification
Demonstrate recovery with the access and dependencies RUN will actually have.
Reference: Contingency planning, RTO and RPO · CCSP examination outline effective 2026-08-01; January2026 V2 PDF