Amazon AWS Certified Solutions Architect - Associate SAA-C03 Practice Test 67
Question 660
A team creates daily full-size EBS snapshots and assumes every snapshot stores the entire volume anew. What pricing assumption is wrong?
- EBS snapshots are incremental and charges depend on stored changed data and retention.
- Stopping EC2 compute does not stop charges for provisioned EBS volumes and snapshots.
- Use EBS Snapshots Archive for eligible long-term retention with expected restore latency.
- Identify unattached volumes, verify ownership and retention, then snapshot and delete unneeded volumes.
Explanation
Correct Answer
A:Snapshot storage tracks unique retained data blocks rather than charging each snapshot as an entire full volume. Inspect snapshot storage trends after a controlled block change.
Incorrect Answers
B:Compute and persistent storage are billed separately and need distinct cost actions. EBS snapshots are incremental and charges depend on stored changed data and retention. Inspect snapshot storage trends after a controlled block change.
C:Archive can lower storage cost but restores take longer and have restoration pricing and duration rules. EBS snapshots are incremental and charges depend on stored changed data and retention. Inspect snapshot storage trends after a controlled block change.
D:Detached EBS volumes continue incurring capacity charges even when no EC2 instance uses them. EBS snapshots are incremental and charges depend on stored changed data and retention. Inspect snapshot storage trends after a controlled block change.
Question 661
A long-retained backup snapshot is rarely restored and operators want a cheaper archival tier. What storage option should be evaluated?
- Stopping EC2 compute does not stop charges for provisioned EBS volumes and snapshots.
- Use EBS Snapshots Archive for eligible long-term retention with expected restore latency.
- Migrate eligible volumes to gp3 with independently provisioned capacity, IOPS and throughput.
- EBS snapshots are incremental and charges depend on stored changed data and retention.
Explanation
Correct Answer
B:Archive can lower storage cost but restores take longer and have restoration pricing and duration rules. Restore a staging archived snapshot and calculate total lifecycle charges.
Incorrect Answers
A:Compute and persistent storage are billed separately and need distinct cost actions. Use EBS Snapshots Archive for eligible long-term retention with expected restore latency. Restore a staging archived snapshot and calculate total lifecycle charges.
C:Gp3 separates performance from volume size and can avoid paying for unnecessary stored capacity. Use EBS Snapshots Archive for eligible long-term retention with expected restore latency. Restore a staging archived snapshot and calculate total lifecycle charges.
D:Snapshot storage tracks unique retained data blocks rather than charging each snapshot as an entire full volume. Use EBS Snapshots Archive for eligible long-term retention with expected restore latency. Restore a staging archived snapshot and calculate total lifecycle charges.
Question 662
A fleet terminates EC2 instances but leaves unused unattached EBS volumes costing money. What action should a cleanup policy take?
- Identify unattached volumes, verify ownership and retention, then snapshot and delete unneeded volumes.
- Right-size the EBS volume using a supported filesystem migration or volume-recreation plan.
- EBS snapshots are incremental and charges depend on stored changed data and retention.
- Stopping EC2 compute does not stop charges for provisioned EBS volumes and snapshots.
Explanation
Correct Answer
A:Detached EBS volumes continue incurring capacity charges even when no EC2 instance uses them. Audit unattached volume age and validate recoverability before cleanup.
Incorrect Answers
B:EBS bills for provisioned capacity even when application files use much less space. Identify unattached volumes, verify ownership and retention, then snapshot and delete unneeded volumes. Audit unattached volume age and validate recoverability before cleanup.
C:Snapshot storage tracks unique retained data blocks rather than charging each snapshot as an entire full volume. Identify unattached volumes, verify ownership and retention, then snapshot and delete unneeded volumes. Audit unattached volume age and validate recoverability before cleanup.
D:Compute and persistent storage are billed separately and need distinct cost actions. Identify unattached volumes, verify ownership and retention, then snapshot and delete unneeded volumes. Audit unattached volume age and validate recoverability before cleanup.
Question 663
A service has stopped EC2 instances while their EBS volumes still incur charges. What is the correct billing explanation?
- Use EBS Snapshots Archive for eligible long-term retention with expected restore latency.
- Migrate eligible volumes to gp3 with independently provisioned capacity, IOPS and throughput.
- Stopping EC2 compute does not stop charges for provisioned EBS volumes and snapshots.
- Identify unattached volumes, verify ownership and retention, then snapshot and delete unneeded volumes.
Explanation
Correct Answer
C:Compute and persistent storage are billed separately and need distinct cost actions. Compare daily EBS usage with stopped-instance compute usage.
Incorrect Answers
A:Archive can lower storage cost but restores take longer and have restoration pricing and duration rules. Stopping EC2 compute does not stop charges for provisioned EBS volumes and snapshots. Compare daily EBS usage with stopped-instance compute usage.
B:Gp3 separates performance from volume size and can avoid paying for unnecessary stored capacity. Compute and persistent storage are billed separately and need distinct cost actions.
D:Detached EBS volumes continue incurring capacity charges even when no EC2 instance uses them. Stopping EC2 compute does not stop charges for provisioned EBS volumes and snapshots. Compare daily EBS usage with stopped-instance compute usage.
Question 664
A database provisioned costly io2 Block Express performance for a workload using only low IOPS. What should govern a lower-cost volume choice?
- Migrate eligible volumes to gp3 with independently provisioned capacity, IOPS and throughput.
- Stopping EC2 compute does not stop charges for provisioned EBS volumes and snapshots.
- Benchmark gp3 against required throughput, latency and durability before replacing overprovisioned io2.
- Reduce provisioned IOPS after workload benchmarking and documented performance headroom.
Explanation
Correct Answer
C:Provisioned IOPS families are justified by measured extreme I/O requirements, not a general performance label. Replay representative I/O on a candidate gp3 staging volume.
Incorrect Answers
A:Gp3 separates performance from volume size and can avoid paying for unnecessary stored capacity. Benchmark gp3 against required throughput, latency and durability before replacing overprovisioned io2. Replay representative I/O on a candidate gp3 staging volume.
B:Compute and persistent storage are billed separately and need distinct cost actions. Benchmark gp3 against required throughput, latency and durability before replacing overprovisioned io2. Replay representative I/O on a candidate gp3 staging volume.
D:Paying for idle provisioned performance is unnecessary when lower settings still meet the workload. Benchmark gp3 against required throughput, latency and durability before replacing overprovisioned io2. Replay representative I/O on a candidate gp3 staging volume.
Question 665
An EFS filesystem holds files unused for months but bills entirely at its active storage class. What reduces storage cost?
- Evaluate FSx for ONTAP storage tiering to eligible capacity-pool storage.
- Configure EFS lifecycle transitions to an eligible Infrequent Access or Archive class.
- Use suitable instance-attached EBS or ephemeral storage instead of a shared EFS filesystem.
- Compare Elastic throughput and alternative modes against measured I/O demand.
Explanation
Correct Answer
B:Managed lifecycle moves cold files to lower storage rates while retrieval frequency and throughput charges remain relevant. Observe class usage after the transition policy operates.
Incorrect Answers
A:Tiering can reduce SSD-tier demand for cold file data while preserving access through ONTAP protocols. Configure EFS lifecycle transitions to an eligible Infrequent Access or Archive class. Observe class usage after the transition policy operates.
C:Shared managed-file features incur charges that may be unnecessary for single-host temporary data. Configure EFS lifecycle transitions to an eligible Infrequent Access or Archive class. Observe class usage after the transition policy operates.
D:EFS throughput mode affects charges; overprovisioned throughput may be inefficient for variable activity. Configure EFS lifecycle transitions to an eligible Infrequent Access or Archive class. Observe class usage after the transition policy operates.
Question 666
An EFS workload uses provisioned throughput far above its tiny sustained usage. What pricing decision should be reevaluated?
- Use suitable instance-attached EBS or ephemeral storage instead of a shared EFS filesystem.
- Compare FSx for Windows File Server capacity and throughput charges with EC2 license and administration costs.
- Right-size a managed EFS solution against required protocol and throughput before selecting specialized FSx.
- Compare Elastic throughput and alternative modes against measured I/O demand.
Explanation
Correct Answer
D:EFS throughput mode affects charges; overprovisioned throughput may be inefficient for variable activity. Model monthly billed throughput across candidate modes.
Incorrect Answers
A:Shared managed-file features incur charges that may be unnecessary for single-host temporary data. Compare Elastic throughput and alternative modes against measured I/O demand. Model monthly billed throughput across candidate modes.
B:Managed file services can reduce operations but have their own capacity and performance billing components. Compare Elastic throughput and alternative modes against measured I/O demand. Model monthly billed throughput across candidate modes.
C:General shared NFS may be cheaper and simpler than specialized high-throughput filesystem capacity. Compare Elastic throughput and alternative modes against measured I/O demand. Model monthly billed throughput across candidate modes.
Question 667
A team stores temporary build outputs on expensive EFS even though only one CI runner accesses them. What cheaper approach may fit?
- Right-size a managed EFS solution against required protocol and throughput before selecting specialized FSx.
- Configure EFS lifecycle transitions to an eligible Infrequent Access or Archive class.
- Compare Elastic throughput and alternative modes against measured I/O demand.
- Use suitable instance-attached EBS or ephemeral storage instead of a shared EFS filesystem.
Explanation
Correct Answer
D:Shared managed-file features incur charges that may be unnecessary for single-host temporary data. Measure total lifecycle cost and confirm artifacts are disposable.
Incorrect Answers
A:General shared NFS may be cheaper and simpler than specialized high-throughput filesystem capacity. Use suitable instance-attached EBS or ephemeral storage instead of a shared EFS filesystem. Measure total lifecycle cost and confirm artifacts are disposable.
B:Managed lifecycle moves cold files to lower storage rates while retrieval frequency and throughput charges remain relevant. Use suitable instance-attached EBS or ephemeral storage instead of a shared EFS filesystem. Measure total lifecycle cost and confirm artifacts are disposable.
C:EFS throughput mode affects charges; overprovisioned throughput may be inefficient for variable activity. Use suitable instance-attached EBS or ephemeral storage instead of a shared EFS filesystem. Measure total lifecycle cost and confirm artifacts are disposable.
Question 668
A shared NFS deployment needs multi-AZ durability but engineers choose One Zone EFS solely because it is cheaper. What must be compared?
- Compare Elastic throughput and alternative modes against measured I/O demand.
- Right-size a managed EFS solution against required protocol and throughput before selecting specialized FSx.
- Use suitable instance-attached EBS or ephemeral storage instead of a shared EFS filesystem.
- Include business cost of AZ-level loss and recovery in the One Zone-versus-regional EFS decision.
Explanation
Correct Answer
D:One Zone pricing savings come with a different failure boundary than regional EFS. Test recovery from AZ unavailability against the workload's RTO.
Incorrect Answers
A:EFS throughput mode affects charges; overprovisioned throughput may be inefficient for variable activity. Include business cost of AZ-level loss and recovery in the One Zone-versus-regional EFS decision. Test recovery from AZ unavailability against the workload's RTO.
B:General shared NFS may be cheaper and simpler than specialized high-throughput filesystem capacity. Include business cost of AZ-level loss and recovery in the One Zone-versus-regional EFS decision. Test recovery from AZ unavailability against the workload's RTO.
C:Shared managed-file features incur charges that may be unnecessary for single-host temporary data. Include business cost of AZ-level loss and recovery in the One Zone-versus-regional EFS decision. Test recovery from AZ unavailability against the workload's RTO.
Question 669
A shared SMB workload runs a self-managed Windows file server around the clock but could use managed FSx. What cost assessment matters?
- Compare FSx for Windows File Server capacity and throughput charges with EC2 license and administration costs.
- Evaluate FSx for ONTAP storage tiering to eligible capacity-pool storage.
- Right-size a managed EFS solution against required protocol and throughput before selecting specialized FSx.
- Compare Elastic throughput and alternative modes against measured I/O demand.
Explanation
Correct Answer
A:Managed file services can reduce operations but have their own capacity and performance billing components. Model annual total ownership cost rather than hourly EC2 price only.
Incorrect Answers
B:Tiering can reduce SSD-tier demand for cold file data while preserving access through ONTAP protocols. Compare FSx for Windows File Server capacity and throughput charges with EC2 license and administration costs. Model annual total ownership cost rather than hourly EC2 price only.
C:General shared NFS may be cheaper and simpler than specialized high-throughput filesystem capacity. Compare FSx for Windows File Server capacity and throughput charges with EC2 license and administration costs. Model annual total ownership cost rather than hourly EC2 price only.
D:EFS throughput mode affects charges; overprovisioned throughput may be inefficient for variable activity. Compare FSx for Windows File Server capacity and throughput charges with EC2 license and administration costs. Model annual total ownership cost rather than hourly EC2 price only.
Question 670
A migrated ONTAP workload has a large cold data pool but requires its familiar file protocol. What FSx ONTAP mechanism may save capacity cost?
- Configure EFS lifecycle transitions to an eligible Infrequent Access or Archive class.
- Use suitable instance-attached EBS or ephemeral storage instead of a shared EFS filesystem.
- Compare FSx for Windows File Server capacity and throughput charges with EC2 license and administration costs.
- Evaluate FSx for ONTAP storage tiering to eligible capacity-pool storage.
Explanation
Correct Answer
D:Tiering can reduce SSD-tier demand for cold file data while preserving access through ONTAP protocols. Inspect SSD and capacity-pool usage plus access penalties.
Incorrect Answers
A:Managed lifecycle moves cold files to lower storage rates while retrieval frequency and throughput charges remain relevant. Evaluate FSx for ONTAP storage tiering to eligible capacity-pool storage. Inspect SSD and capacity-pool usage plus access penalties.
B:Shared managed-file features incur charges that may be unnecessary for single-host temporary data. Evaluate FSx for ONTAP storage tiering to eligible capacity-pool storage. Inspect SSD and capacity-pool usage plus access penalties.
C:Managed file services can reduce operations but have their own capacity and performance billing components. Evaluate FSx for ONTAP storage tiering to eligible capacity-pool storage. Inspect SSD and capacity-pool usage plus access penalties.