Amazon AWS Certified Solutions Architect - Professional SAP-C02 Bundle

Inventory detached volumes and delete or archive them after confirming recoverability would address a different requirement: Old unattached EBS volumes remain billed after test environments are torn down. Unattached EBS storage continues accruing capacity charges until removed.

For the separate situation Two compute tiers in the same Region exchange heavy traffic while spread across AZs, Model and reduce unnecessary cross-AZ transfers while retaining required fault isolation could be useful. Inter-AZ network charges can dominate high-volume chatty application traffic.

Use Compute Optimizer and telemetry to rightsize instances after testing performance headroom solves the related scenario An EC2 fleet runs at 5% utilization and serves a steady but smaller load; rightsizing removes idle compute capacity without requiring a purchase commitment.

For the separate situation A stack with application resources must recover automatically when a deployment fails validation, Use CloudFormation rollback behavior with predeployment change review could be useful. Stack rollback attempts to return the provisioned stack to its previous stable state.

Generate and inspect a CloudFormation change set before execution solves the related scenario A production stack update might replace a database unexpectedly and change approval is mandatory; change sets show intended stack resource modifications including potential replacements.

Although Apply DeletionPolicy Retain to protected resources in the template can be valid when An operations team needs to prevent accidental deletion of stateful CloudFormation resources during stack removal, it targets a different technical condition. Retain keeps specified physical resources when the stack is deleted.

Use parameterized CloudFormation stacks through StackSets for target accounts and Regions solves the related scenario A regulated platform team must provision identical VPC and compute baselines across three Regions; stackSets distribute controlled infrastructure definitions to multiple destinations.

Although Detect stack drift and reconcile changes through managed template updates can be valid when A central pipeline must keep CloudFormation from accidentally overwriting manual configuration changes, it targets a different technical condition. Drift detection highlights differences between expected template configuration and live resources.

Use CloudFormation rollback behavior with predeployment change review would address a different requirement: A stack with application resources must recover automatically when a deployment fails validation. Stack rollback attempts to return the provisioned stack to its previous stable state.

Detect stack drift and reconcile changes through managed template updates would address a different requirement: A central pipeline must keep CloudFormation from accidentally overwriting manual configuration changes. Drift detection highlights differences between expected template configuration and live resources.

This alternative, Use CloudFormation rollback behavior with predeployment change review, is appropriate when A stack with application resources must recover automatically when a deployment fails validation. Stack rollback attempts to return the provisioned stack to its previous stable state.

For the separate situation A production stack update might replace a database unexpectedly and change approval is mandatory, Generate and inspect a CloudFormation change set before execution could be useful. Change sets show intended stack resource modifications including potential replacements.

This alternative, Apply DeletionPolicy Retain to protected resources in the template, is appropriate when An operations team needs to prevent accidental deletion of stateful CloudFormation resources during stack removal. Retain keeps specified physical resources when the stack is deleted.

For the separate situation A regulated platform team must provision identical VPC and compute baselines across three Regions, Use parameterized CloudFormation stacks through StackSets for target accounts and Regions could be useful. StackSets distribute controlled infrastructure definitions to multiple destinations.

Generate and inspect a CloudFormation change set before execution solves the related scenario A production stack update might replace a database unexpectedly and change approval is mandatory; change sets show intended stack resource modifications including potential replacements.

This alternative, Use parameterized CloudFormation stacks through StackSets for target accounts and Regions, is appropriate when A regulated platform team must provision identical VPC and compute baselines across three Regions. StackSets distribute controlled infrastructure definitions to multiple destinations.

For the separate situation A production stack update might replace a database unexpectedly and change approval is mandatory, Generate and inspect a CloudFormation change set before execution could be useful. Change sets show intended stack resource modifications including potential replacements.

Detect stack drift and reconcile changes through managed template updates solves the related scenario A central pipeline must keep CloudFormation from accidentally overwriting manual configuration changes; drift detection highlights differences between expected template configuration and live resources.

Use CodeDeploy Lambda canary deployment with an alias and CloudWatch rollback alarm solves the related scenario A Lambda function update must be exposed to 10% of users before broader rollout; traffic shifting and alarm hooks limit impact of a faulty function revision.

Although Configure ECS rolling deployment minimum healthy percent and maximum percent can be valid when A container platform must deploy a new image without terminating all old tasks simultaneously, it targets a different technical condition. Rolling task replacement maintains defined healthy capacity during deployments.

Use an expand-migrate-contract schema rollout with backwards-compatible transitional fields would address a different requirement: A database schema change must coexist with both old and new application versions during rollout. Backward-compatible schema transitions avoid breakage when old and new app versions overlap.

Although Configure ECS rolling deployment minimum healthy percent and maximum percent can be valid when A container platform must deploy a new image without terminating all old tasks simultaneously, it targets a different technical condition. Rolling task replacement maintains defined healthy capacity during deployments.

This alternative, Bind deployment lifecycle alarms to rollback and bake-period monitoring, is appropriate when An application release must stop automatically when the error rate rises above a predefined threshold. Metric-gated rollback prevents continuing a demonstrably unhealthy release.

For the separate situation A web fleet update must allow immediate routing back to the previous version after failed health checks, Adopt a blue-green deployment using separate target groups and health-based traffic shifting could be useful. Two independently serving versions permit fast traffic reversal.

Bind deployment lifecycle alarms to rollback and bake-period monitoring would address a different requirement: An application release must stop automatically when the error rate rises above a predefined threshold. Metric-gated rollback prevents continuing a demonstrably unhealthy release.

This alternative, Adopt a blue-green deployment using separate target groups and health-based traffic shifting, is appropriate when A web fleet update must allow immediate routing back to the previous version after failed health checks. Two independently serving versions permit fast traffic reversal.

For the separate situation A database schema change must coexist with both old and new application versions during rollout, Use an expand-migrate-contract schema rollout with backwards-compatible transitional fields could be useful. Backward-compatible schema transitions avoid breakage when old and new app versions overlap.

This alternative, Use CodeDeploy Lambda canary deployment with an alias and CloudWatch rollback alarm, is appropriate when A Lambda function update must be exposed to 10% of users before broader rollout. Traffic shifting and alarm hooks limit impact of a faulty function revision.

For the separate situation A container platform must deploy a new image without terminating all old tasks simultaneously, Configure ECS rolling deployment minimum healthy percent and maximum percent could be useful. Rolling task replacement maintains defined healthy capacity during deployments.

Although Bind deployment lifecycle alarms to rollback and bake-period monitoring can be valid when An application release must stop automatically when the error rate rises above a predefined threshold, it targets a different technical condition. Metric-gated rollback prevents continuing a demonstrably unhealthy release.

For the separate situation A Lambda function update must be exposed to 10% of users before broader rollout, Use CodeDeploy Lambda canary deployment with an alias and CloudWatch rollback alarm could be useful. Traffic shifting and alarm hooks limit impact of a faulty function revision.

Although Configure ECS rolling deployment minimum healthy percent and maximum percent can be valid when A container platform must deploy a new image without terminating all old tasks simultaneously, it targets a different technical condition. Rolling task replacement maintains defined healthy capacity during deployments.

Adopt a blue-green deployment using separate target groups and health-based traffic shifting would address a different requirement: A web fleet update must allow immediate routing back to the previous version after failed health checks. Two independently serving versions permit fast traffic reversal.