Amazon AWS Certified Solutions Architect - Professional SAP-C02 Bundle

This alternative, Enforce a standard activated cost allocation tag and report untagged assets, is appropriate when A development team claims its spend cannot be assigned because application names differ across resources. Consistent activated tags allow cost attribution across otherwise disparate services.

For the separate situation A cost dashboard suddenly reports lower spend because a new linked account was excluded, Verify Cost Explorer account and charge-type filters before concluding savings occurred could be useful. Reporting scope changes can mimic genuine changes in resource consumption.

Query Cost and Usage Report usage-type line items for transfer categories and accounts solves the related scenario A monthly invoice shows unexplained data transfer growth that Cost Explorer groups too broadly; cUR provides usage dimensions needed for granular charge-root-cause investigation.

For the separate situation An organization purchases new EC2 reservations despite holding underused reservations after a migration, Audit RI and Savings Plans utilization and coverage before committing more could be useful. Overlapping commitments can increase cost when eligible usage is insufficient.

Although Reduce the minimum task count and implement appropriate utilization-based autoscaling can be valid when An overprovisioned ECS service always maintains 60 tasks despite single-digit utilization, it targets a different technical condition. Lower baseline desired capacity reduces paid idle compute while retaining failover margins.

Shift interruption-tolerant workers to Spot with checkpointing and retries would address a different requirement: A fault-tolerant batch service runs entirely on full-price On-Demand capacity with flexible deadlines. Spare-capacity pricing reduces cost when the workload tolerates termination.

Audit RI and Savings Plans utilization and coverage before committing more solves the related scenario An organization purchases new EC2 reservations despite holding underused reservations after a migration; overlapping commitments can increase cost when eligible usage is insufficient.

Although Use Compute Optimizer recommendations and benchmark smaller instance families can be valid when A fleet of m-family EC2 instances reports 8% CPU and low memory usage for months, it targets a different technical condition. Compute Optimizer suggests potential rightsizing based on utilization telemetry.

Shift interruption-tolerant workers to Spot with checkpointing and retries would address a different requirement: A fault-tolerant batch service runs entirely on full-price On-Demand capacity with flexible deadlines. Spare-capacity pricing reduces cost when the workload tolerates termination.

Although Use Compute Optimizer recommendations and benchmark smaller instance families can be valid when A fleet of m-family EC2 instances reports 8% CPU and low memory usage for months, it targets a different technical condition. Compute Optimizer suggests potential rightsizing based on utilization telemetry.

Schedule instance shutdown during approved idle windows and preserve restart automation would address a different requirement: A test environment runs EC2 instances all weekend with no traffic. Turning off idle eligible compute removes avoidable instance-hours.

For the separate situation An overprovisioned ECS service always maintains 60 tasks despite single-digit utilization, Reduce the minimum task count and implement appropriate utilization-based autoscaling could be useful. Lower baseline desired capacity reduces paid idle compute while retaining failover margins.

Shift interruption-tolerant workers to Spot with checkpointing and retries would address a different requirement: A fault-tolerant batch service runs entirely on full-price On-Demand capacity with flexible deadlines. Spare-capacity pricing reduces cost when the workload tolerates termination.

This alternative, Reduce the minimum task count and implement appropriate utilization-based autoscaling, is appropriate when An overprovisioned ECS service always maintains 60 tasks despite single-digit utilization. Lower baseline desired capacity reduces paid idle compute while retaining failover margins.

Use Compute Optimizer recommendations and benchmark smaller instance families solves the related scenario A fleet of m-family EC2 instances reports 8% CPU and low memory usage for months; compute Optimizer suggests potential rightsizing based on utilization telemetry.

This alternative, Audit RI and Savings Plans utilization and coverage before committing more, is appropriate when An organization purchases new EC2 reservations despite holding underused reservations after a migration. Overlapping commitments can increase cost when eligible usage is insufficient.

For the separate situation A test environment runs EC2 instances all weekend with no traffic, Schedule instance shutdown during approved idle windows and preserve restart automation could be useful. Turning off idle eligible compute removes avoidable instance-hours.

Although Shift interruption-tolerant workers to Spot with checkpointing and retries can be valid when A fault-tolerant batch service runs entirely on full-price On-Demand capacity with flexible deadlines, it targets a different technical condition. Spare-capacity pricing reduces cost when the workload tolerates termination.

Move appropriate persistent backups to lifecycle-managed S3 or AWS Backup storage solves the related scenario A team stores 50 GB of rarely used backups in expensive provisioned EC2 instance disks; durable shared backup services separate retention needs from high-cost always-mounted compute storage.

Although Set lifecycle rules to expire old noncurrent versions subject to retention policy can be valid when A bucket retains noncurrent versions of frequently updated transient logs indefinitely, it targets a different technical condition. Versioned-object history consumes storage until lifecycle cleanup or manual deletion.

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.

Enable appropriate EFS lifecycle management to move cold files to a lower-cost storage class would address a different requirement: 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.

This alternative, Recalculate lifecycle timing against each storage class's minimum duration constraints, is appropriate when An S3 archival design ignores minimum storage duration and early deletion charges. Premature archival deletes can erase projected savings through minimum duration billing.

For the separate situation A team stores 50 GB of rarely used backups in expensive provisioned EC2 instance disks, Move appropriate persistent backups to lifecycle-managed S3 or AWS Backup storage could be useful. Durable shared backup services separate retention needs from high-cost always-mounted compute storage.

This alternative, Set lifecycle rules to expire old noncurrent versions subject to retention policy, is appropriate when A bucket retains noncurrent versions of frequently updated transient logs indefinitely. Versioned-object history consumes storage until lifecycle cleanup or manual deletion.

For the separate situation An S3 archival design ignores minimum storage duration and early deletion charges, Recalculate lifecycle timing against each storage class's minimum duration constraints could be useful. Premature archival deletes can erase projected savings through minimum duration billing.

Find detached volumes and remove or archive them after ownership and retention checks solves the related scenario A test stack leaves behind dozens of unattached EBS volumes after CloudFormation removal; unattached EBS volumes incur storage charges while no workload is using them.

For the separate situation A team stores 50 GB of rarely used backups in expensive provisioned EC2 instance disks, Move appropriate persistent backups to lifecycle-managed S3 or AWS Backup storage could be useful. Durable shared backup services separate retention needs from high-cost always-mounted compute storage.

Find detached volumes and remove or archive them after ownership and retention checks solves the related scenario A test stack leaves behind dozens of unattached EBS volumes after CloudFormation removal; unattached EBS volumes incur storage charges while no workload is using them.

Although Set lifecycle rules to expire old noncurrent versions subject to retention policy can be valid when A bucket retains noncurrent versions of frequently updated transient logs indefinitely, it targets a different technical condition. Versioned-object history consumes storage until lifecycle cleanup or manual deletion.

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.