Amazon AWS Certified Solutions Architect - Professional SAP-C02 Bundle

For the separate situation A test stack leaves behind dozens of unattached EBS volumes after CloudFormation removal, Find detached volumes and remove or archive them after ownership and retention checks could be useful. Unattached EBS volumes incur storage charges while no workload is using them.

Enable appropriate EFS lifecycle management to move cold files to a lower-cost storage class solves the related scenario Several EFS file systems contain mostly old, rarely opened data but use the highest-cost class; eFS lifecycle reduces storage costs for infrequently accessed files within its supported tiers.

Recalculate lifecycle timing against each storage class's minimum duration constraints would address a different requirement: An S3 archival design ignores minimum storage duration and early deletion charges. Premature archival deletes can erase projected savings through minimum duration billing.

Reduce cross-AZ call volume through locality and batching without removing required failover would address a different requirement: A chatty stateful service performs thousands of cross-AZ remote procedure calls for each transaction. Cross-AZ bandwidth charges grow with unnecessary synchronous request chatter.

This alternative, Deliver static assets via S3 and CloudFront instead of forwarding through the API servers, is appropriate when A regional API proxies all downloadable image assets through expensive EC2 instances. Object-plus-CDN delivery lowers application fleet egress and repeated processing.

For the separate situation A hybrid design routes internet-bound traffic over Direct Connect for an application that could use local ISP egress, Measure Direct Connect port and data transfer costs against security requirements before hairpinning could be useful. Private-network routing can add expense without meeting a concrete security or latency need.

This alternative, Batch and compress cross-Region transfers and avoid unnecessary continuous replication, is appropriate when A workload copies terabytes daily across Regions although a weekly consolidated dataset would suffice. Transferred-byte volume directly affects inter-Region network charges.

For the separate situation A hybrid design routes internet-bound traffic over Direct Connect for an application that could use local ISP egress, Measure Direct Connect port and data transfer costs against security requirements before hairpinning could be useful. Private-network routing can add expense without meeting a concrete security or latency need.

Move eligible S3 API routes to a gateway VPC endpoint solves the related scenario A VPC routes all S3 data copies through one charged NAT gateway; gateway endpoint routing eliminates avoidable NAT processing for S3 traffic.

This alternative, Measure Direct Connect port and data transfer costs against security requirements before hairpinning, is appropriate when A hybrid design routes internet-bound traffic over Direct Connect for an application that could use local ISP egress. Private-network routing can add expense without meeting a concrete security or latency need.

For the separate situation A chatty stateful service performs thousands of cross-AZ remote procedure calls for each transaction, Reduce cross-AZ call volume through locality and batching without removing required failover could be useful. Cross-AZ bandwidth charges grow with unnecessary synchronous request chatter.

Batch and compress cross-Region transfers and avoid unnecessary continuous replication solves the related scenario A workload copies terabytes daily across Regions although a weekly consolidated dataset would suffice; transferred-byte volume directly affects inter-Region network charges.

Move eligible S3 API routes to a gateway VPC endpoint solves the related scenario A VPC routes all S3 data copies through one charged NAT gateway; gateway endpoint routing eliminates avoidable NAT processing for S3 traffic.

Although Reduce cross-AZ call volume through locality and batching without removing required failover can be valid when A chatty stateful service performs thousands of cross-AZ remote procedure calls for each transaction, it targets a different technical condition. Cross-AZ bandwidth charges grow with unnecessary synchronous request chatter.

Deliver static assets via S3 and CloudFront instead of forwarding through the API servers would address a different requirement: A regional API proxies all downloadable image assets through expensive EC2 instances. Object-plus-CDN delivery lowers application fleet egress and repeated processing.

Reduce cross-AZ call volume through locality and batching without removing required failover solves the related scenario A chatty stateful service performs thousands of cross-AZ remote procedure calls for each transaction; cross-AZ bandwidth charges grow with unnecessary synchronous request chatter.

Although Batch and compress cross-Region transfers and avoid unnecessary continuous replication can be valid when A workload copies terabytes daily across Regions although a weekly consolidated dataset would suffice, it targets a different technical condition. Transferred-byte volume directly affects inter-Region network charges.

Move eligible S3 API routes to a gateway VPC endpoint would address a different requirement: A VPC routes all S3 data copies through one charged NAT gateway. Gateway endpoint routing eliminates avoidable NAT processing for S3 traffic.

Model future database demand and evaluate appropriate renewal commitment options would address a different requirement: A critical database has one-year reserved capacity that will expire next week. Renewal should reflect forecasted database utilization rather than blindly copying prior capacity.

For the separate situation A cloud team needs automated finance notification when a new service exceeds a daily limit, Configure a scoped AWS Budget with appropriate notification destinations could be useful. Budget alerts translate threshold breaches into responsible owner communication.

Analyze baseline usage and evaluate an appropriately sized Compute Savings Plan solves the related scenario An organization has steady eligible EC2 and Fargate spend but no capacity commitments; flexible compute commitment discounts can cover stable eligible usage across platforms.

This alternative, Track normalized service usage, unit costs and savings against established baselines, is appropriate when An executive wants quarterly optimization proof rather than anecdotal reduction claims. Cost efficiency requires comparing consistent workload output and time windows.

Use AWS Budgets forecast alerts filtered to the required scope solves the related scenario A product owner wants forecast-based warning before an AWS account exceeds its monthly budget; forecast alerts flag expected overruns before final charges post.

Although Model future database demand and evaluate appropriate renewal commitment options can be valid when A critical database has one-year reserved capacity that will expire next week, it targets a different technical condition. Renewal should reflect forecasted database utilization rather than blindly copying prior capacity.

For the separate situation A product owner wants forecast-based warning before an AWS account exceeds its monthly budget, Use AWS Budgets forecast alerts filtered to the required scope could be useful. Forecast alerts flag expected overruns before final charges post.

Configure a scoped AWS Budget with appropriate notification destinations solves the related scenario A cloud team needs automated finance notification when a new service exceeds a daily limit; budget alerts translate threshold breaches into responsible owner communication.

Track normalized service usage, unit costs and savings against established baselines would address a different requirement: An executive wants quarterly optimization proof rather than anecdotal reduction claims. Cost efficiency requires comparing consistent workload output and time windows.

Model future database demand and evaluate appropriate renewal commitment options solves the related scenario A critical database has one-year reserved capacity that will expire next week; renewal should reflect forecasted database utilization rather than blindly copying prior capacity.

Although Track normalized service usage, unit costs and savings against established baselines can be valid when An executive wants quarterly optimization proof rather than anecdotal reduction claims, it targets a different technical condition. Cost efficiency requires comparing consistent workload output and time windows.

Analyze baseline usage and evaluate an appropriately sized Compute Savings Plan would address a different requirement: An organization has steady eligible EC2 and Fargate spend but no capacity commitments. Flexible compute commitment discounts can cover stable eligible usage across platforms.

Although Model future database demand and evaluate appropriate renewal commitment options can be valid when A critical database has one-year reserved capacity that will expire next week, it targets a different technical condition. Renewal should reflect forecasted database utilization rather than blindly copying prior capacity.

This alternative, Use AWS Budgets forecast alerts filtered to the required scope, is appropriate when A product owner wants forecast-based warning before an AWS account exceeds its monthly budget. Forecast alerts flag expected overruns before final charges post.

For the separate situation An organization has steady eligible EC2 and Fargate spend but no capacity commitments, Analyze baseline usage and evaluate an appropriately sized Compute Savings Plan could be useful. Flexible compute commitment discounts can cover stable eligible usage across platforms.