Amazon AWS Certified Solutions Architect - Professional SAP-C02 Bundle

Evaluate a Compute Savings Plan sized to the stable baseline solves the related scenario A steady fleet of EC2 web servers runs all day with unpredictable instance-family changes; compute Savings Plans cover eligible compute usage flexibly across supported families and Regions.

Although Evaluate EC2 Instance Savings Plans or appropriate Reserved Instance commitments can be valid when A fixed EC2 instance family is used continuously in one Region and cost minimization is paramount, it targets a different technical condition. Narrower commitments can reduce cost when predictable usage justifies less flexibility.

This alternative, Use EC2 Spot Instances with checkpointing and interruption-aware retries, is appropriate when A fault-tolerant batch queue can stop and resume tasks whenever spare capacity disappears. Spot provides discount capacity with reclaim risk suited to flexible workloads.

Move eligible objects to an S3 Glacier archival storage class with an appropriate retrieval tier would address a different requirement: An archived dataset is rarely accessed and can tolerate a multi-hour restore. Glacier archival tiers lower storage charges in exchange for retrieval constraints.

For the separate situation A company needs visibility into which buckets contain cold or small objects before changing policies, Review Amazon S3 Storage Lens metrics and storage class distributions could be useful. Storage Lens surfaces capacity and activity trends across buckets and accounts.

Evaluate per-object metadata, minimum billing, and retrieval fees before lifecycle transitions solves the related scenario Millions of tiny frequently accessed objects are being moved to low-cost archive blindly; object overhead and minimum storage durations can outweigh nominal per-GB class savings.

For the separate situation An archived dataset is rarely accessed and can tolerate a multi-hour restore, Move eligible objects to an S3 Glacier archival storage class with an appropriate retrieval tier could be useful. Glacier archival tiers lower storage charges in exchange for retrieval constraints.

Review Amazon S3 Storage Lens metrics and storage class distributions solves the related scenario A company needs visibility into which buckets contain cold or small objects before changing policies; storage Lens surfaces capacity and activity trends across buckets and accounts.

Although Apply a lifecycle policy to move eligible objects to a suitable S3 infrequent-access class can be valid when An S3 bucket holds infrequently accessed immutable audit logs that must be retrievable rapidly on demand, it targets a different technical condition. Lifecycle transitions align per-GB storage price with infrequent access and retrieval requirements.

For the separate situation Millions of tiny frequently accessed objects are being moved to low-cost archive blindly, Evaluate per-object metadata, minimum billing, and retrieval fees before lifecycle transitions could be useful. Object overhead and minimum storage durations can outweigh nominal per-GB class savings.

Although Apply a lifecycle policy to move eligible objects to a suitable S3 infrequent-access class can be valid when An S3 bucket holds infrequently accessed immutable audit logs that must be retrievable rapidly on demand, it targets a different technical condition. Lifecycle transitions align per-GB storage price with infrequent access and retrieval requirements.

Choose S3 Intelligent-Tiering where object size and monitoring economics fit would address a different requirement: A dataset has unpredictable object access patterns and operations cannot manage tiers manually. Intelligent-Tiering automatically moves qualifying objects based on access activity.

Although Apply a lifecycle policy to move eligible objects to a suitable S3 infrequent-access class can be valid when An S3 bucket holds infrequently accessed immutable audit logs that must be retrievable rapidly on demand, it targets a different technical condition. Lifecycle transitions align per-GB storage price with infrequent access and retrieval requirements.

Move eligible objects to an S3 Glacier archival storage class with an appropriate retrieval tier would address a different requirement: An archived dataset is rarely accessed and can tolerate a multi-hour restore. Glacier archival tiers lower storage charges in exchange for retrieval constraints.

This alternative, Evaluate per-object metadata, minimum billing, and retrieval fees before lifecycle transitions, is appropriate when Millions of tiny frequently accessed objects are being moved to low-cost archive blindly. Object overhead and minimum storage durations can outweigh nominal per-GB class savings.

Move eligible objects to an S3 Glacier archival storage class with an appropriate retrieval tier would address a different requirement: An archived dataset is rarely accessed and can tolerate a multi-hour restore. Glacier archival tiers lower storage charges in exchange for retrieval constraints.

This alternative, Review Amazon S3 Storage Lens metrics and storage class distributions, is appropriate when A company needs visibility into which buckets contain cold or small objects before changing policies. Storage Lens surfaces capacity and activity trends across buckets and accounts.

For the separate situation A dataset has unpredictable object access patterns and operations cannot manage tiers manually, Choose S3 Intelligent-Tiering where object size and monitoring economics fit could be useful. Intelligent-Tiering automatically moves qualifying objects based on access activity.

This alternative, Inventory detached volumes and delete or archive them after confirming recoverability, is appropriate when Old unattached EBS volumes remain billed after test environments are torn down. Unattached EBS storage continues accruing capacity charges until removed.

Implement scheduled or metric-based Auto Scaling to reduce idle capacity solves the related scenario A mature service has predictable nightly idle periods but EC2 servers remain fully provisioned; elastic capacity aligns compute spend to demand while retaining availability limits.

Although Route supported S3 traffic through a gateway VPC endpoint can be valid when A private service calls S3 through a NAT gateway and incurs unexpected data-processing fees, it targets a different technical condition. S3 gateway endpoint routes avoid NAT processing charges for qualifying traffic.

For the separate situation A mature service has predictable nightly idle periods but EC2 servers remain fully provisioned, Implement scheduled or metric-based Auto Scaling to reduce idle capacity could be useful. Elastic capacity aligns compute spend to demand while retaining availability limits.

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.

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.

Model and reduce unnecessary cross-AZ transfers while retaining required fault isolation solves the related scenario Two compute tiers in the same Region exchange heavy traffic while spread across AZs; inter-AZ network charges can dominate high-volume chatty application traffic.

Route supported S3 traffic through a gateway VPC endpoint would address a different requirement: A private service calls S3 through a NAT gateway and incurs unexpected data-processing fees. S3 gateway endpoint routes avoid NAT processing charges for qualifying traffic.

This alternative, Inventory detached volumes and delete or archive them after confirming recoverability, is appropriate when Old unattached EBS volumes remain billed after test environments are torn down. Unattached EBS storage continues accruing capacity charges until removed.

Route supported S3 traffic through a gateway VPC endpoint would address a different requirement: A private service calls S3 through a NAT gateway and incurs unexpected data-processing fees. S3 gateway endpoint routes avoid NAT processing charges for qualifying traffic.

This alternative, Implement scheduled or metric-based Auto Scaling to reduce idle capacity, is appropriate when A mature service has predictable nightly idle periods but EC2 servers remain fully provisioned. Elastic capacity aligns compute spend to demand while retaining availability limits.

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.

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.