This website uses cookies to ensure you get the best experience.
Learn more.
A planned routing change must not silently expose isolated development VPCs to production. Which validation approach best addresses this risk?
Published
- Check only that one production webpage returns HTTP 200.
- Disable all logging to avoid false alarms during the change.
- Analyze defined network access scopes and compare unintended-access findings before and after the change.
- Verify that every VPC Name tag contains its environment.
Comments — 0
Sign in to comment