Amazon AWS Certified Solutions Architect - Professional SAP-C02 Bundle

This alternative, Use Spot capacity with resilient interruption processing and mixed-instance policies, is appropriate when A batch rendering fleet can checkpoint work every few minutes and has flexible deadlines. Interruptible discounts fit recoverable work that can resume on replacement nodes.

For the separate situation An underused application instance is twice as large as its measured peak requirements, Reduce instance size after load testing and monitor new headroom could be useful. Rightsizing removes paid idle CPU and memory before buying discounts.

Commit only the stable baseline to Savings Plans and keep bursts on elastic on-demand capacity solves the related scenario A new service has stable compute usage at night but highly volatile daytime traffic; splitting baseline and burst avoids overcommitting to uncertain peak usage.

Model per-object transition charges and minimum billable size before changing tiers solves the related scenario A dataset consists of tiny objects and lifecycle transitions appear more expensive than Standard storage; small-object overhead can outweigh archive per-GB discounts.

Set age-based AWS Backup lifecycle retention after compliance review would address a different requirement: A database retains monthly snapshots indefinitely without a legal or business requirement. Managed retention policies prevent indefinite accumulation of backup recovery points.

This alternative, Audit backup dependencies and expire snapshots after verified retention obligations, is appropriate when An application retains obsolete EBS snapshots after the underlying resources were retired. Snapshot cleanup avoids retained storage cost for unneeded recovery points.

Model per-object transition charges and minimum billable size before changing tiers would address a different requirement: A dataset consists of tiny objects and lifecycle transitions appear more expensive than Standard storage. Small-object overhead can outweigh archive per-GB discounts.

This alternative, Transition old S3 objects to an archival storage class after checking restore SLA, is appropriate when A data lake's raw archives must be retained for years but are rarely queried. Archive storage trades lower cost against retrieval latency and minimum retention.

For the separate situation An application retains obsolete EBS snapshots after the underlying resources were retired, Audit backup dependencies and expire snapshots after verified retention obligations could be useful. Snapshot cleanup avoids retained storage cost for unneeded recovery points.

Transition old S3 objects to an archival storage class after checking restore SLA would address a different requirement: A data lake's raw archives must be retained for years but are rarely queried. Archive storage trades lower cost against retrieval latency and minimum retention.

This alternative, Use S3 Intelligent-Tiering for qualifying objects with unknown access frequency, is appropriate when A photo-sharing app cannot predict which user objects will be read each month. Automatic access-tier movement adapts to unpredictable object popularity.

For the separate situation A database retains monthly snapshots indefinitely without a legal or business requirement, Set age-based AWS Backup lifecycle retention after compliance review could be useful. Managed retention policies prevent indefinite accumulation of backup recovery points.

This alternative, Audit backup dependencies and expire snapshots after verified retention obligations, is appropriate when An application retains obsolete EBS snapshots after the underlying resources were retired. Snapshot cleanup avoids retained storage cost for unneeded recovery points.

For the separate situation A database retains monthly snapshots indefinitely without a legal or business requirement, Set age-based AWS Backup lifecycle retention after compliance review could be useful. Managed retention policies prevent indefinite accumulation of backup recovery points.

Transition old S3 objects to an archival storage class after checking restore SLA solves the related scenario A data lake's raw archives must be retained for years but are rarely queried; archive storage trades lower cost against retrieval latency and minimum retention.

Model per-object transition charges and minimum billable size before changing tiers solves the related scenario A dataset consists of tiny objects and lifecycle transitions appear more expensive than Standard storage; small-object overhead can outweigh archive per-GB discounts.

Although Use S3 Intelligent-Tiering for qualifying objects with unknown access frequency can be valid when A photo-sharing app cannot predict which user objects will be read each month, it targets a different technical condition. Automatic access-tier movement adapts to unpredictable object popularity.

Audit backup dependencies and expire snapshots after verified retention obligations would address a different requirement: An application retains obsolete EBS snapshots after the underlying resources were retired. Snapshot cleanup avoids retained storage cost for unneeded recovery points.

Although Include AWS port-hour, data-transfer and partner cross-connect fees in total cost modeling can be valid when A team assumes Direct Connect costs are only the leased circuit price, it targets a different technical condition. Hybrid networking cost comprises AWS and provider charges beyond base connectivity.

This alternative, Configure the S3 gateway endpoint in the relevant VPC subnet routes, is appropriate when ECS tasks in private subnets download many gigabytes from S3 through a NAT gateway. Private gateway routing eliminates avoidable NAT processing for eligible S3 traffic.

For the separate situation An outbound enterprise service repeatedly uploads large data from AWS to a public endpoint, Model internet data-transfer-out and evaluate CDN or replication strategies could be useful. Outbound network charges must be considered separately from compute costs.

This alternative, Prefer AZ-local endpoints or caching where resilience requirements permit, is appropriate when Multiple services route east-west calls across AZ boundaries although each has local replica capacity. Zonal affinity can lower inter-AZ traffic charges without sacrificing failover paths.

For the separate situation An outbound enterprise service repeatedly uploads large data from AWS to a public endpoint, Model internet data-transfer-out and evaluate CDN or replication strategies could be useful. Outbound network charges must be considered separately from compute costs.

Include AWS port-hour, data-transfer and partner cross-connect fees in total cost modeling solves the related scenario A team assumes Direct Connect costs are only the leased circuit price; hybrid networking cost comprises AWS and provider charges beyond base connectivity.

This alternative, Configure the S3 gateway endpoint in the relevant VPC subnet routes, is appropriate when ECS tasks in private subnets download many gigabytes from S3 through a NAT gateway. Private gateway routing eliminates avoidable NAT processing for eligible S3 traffic.

For the separate situation An outbound enterprise service repeatedly uploads large data from AWS to a public endpoint, Model internet data-transfer-out and evaluate CDN or replication strategies could be useful. Outbound network charges must be considered separately from compute costs.

Although Process or cache data nearer its consumers and reduce repeated cross-Region transfer can be valid when An application copies huge objects between two AWS Regions unnecessarily on every request, it targets a different technical condition. Cross-Region egress charges add recurring cost to chatty distributed designs.

For the separate situation A team assumes Direct Connect costs are only the leased circuit price, Include AWS port-hour, data-transfer and partner cross-connect fees in total cost modeling could be useful. Hybrid networking cost comprises AWS and provider charges beyond base connectivity.

Process or cache data nearer its consumers and reduce repeated cross-Region transfer solves the related scenario An application copies huge objects between two AWS Regions unnecessarily on every request; cross-Region egress charges add recurring cost to chatty distributed designs.

Although Configure the S3 gateway endpoint in the relevant VPC subnet routes can be valid when ECS tasks in private subnets download many gigabytes from S3 through a NAT gateway, it targets a different technical condition. Private gateway routing eliminates avoidable NAT processing for eligible S3 traffic.

Process or cache data nearer its consumers and reduce repeated cross-Region transfer solves the related scenario An application copies huge objects between two AWS Regions unnecessarily on every request; cross-Region egress charges add recurring cost to chatty distributed designs.

Although Prefer AZ-local endpoints or caching where resilience requirements permit can be valid when Multiple services route east-west calls across AZ boundaries although each has local replica capacity, it targets a different technical condition. Zonal affinity can lower inter-AZ traffic charges without sacrificing failover paths.

Model internet data-transfer-out and evaluate CDN or replication strategies would address a different requirement: An outbound enterprise service repeatedly uploads large data from AWS to a public endpoint. Outbound network charges must be considered separately from compute costs.