Amazon AWS Certified Solutions Architect - Associate SAA-C03 Practice Test 66
Question 650
A bucket receives incomplete multipart uploads from interrupted clients and pays for orphaned uploaded parts. Which lifecycle rule helps?
- Abort incomplete multipart uploads after a safe configured age.
- Retain locked object versions until their retention expires and model the unavoidable storage.
- Use lifecycle transitions to suitable progressively colder S3 classes while preserving retention.
- Align dump expiration and version lifecycle to the approved seven-day recovery obligation.
Explanation
Correct Answer
A:S3 retains uploaded parts until completion or abort, so stale parts incur storage charges. List incomplete uploads and verify the lifecycle rule clears aged parts.
Incorrect Answers
B:Lifecycle rules cannot override applicable Object Lock retention merely for savings. Abort incomplete multipart uploads after a safe configured age. List incomplete uploads and verify the lifecycle rule clears aged parts.
C:Age-based transitions align per-class costs with expected access frequency and recovery needs. Abort incomplete multipart uploads after a safe configured age. List incomplete uploads and verify the lifecycle rule clears aged parts.
D:Storage lifecycle should retain only justified copies while ensuring recovery and compliance evidence. Abort incomplete multipart uploads after a safe configured age. List incomplete uploads and verify the lifecycle rule clears aged parts.
Question 651
A dataset is hot during its first month and never accessed after one year, but its retention policy lasts seven years. What cost management fits?
- Retain locked object versions until their retention expires and model the unavoidable storage.
- Use lifecycle transitions to suitable progressively colder S3 classes while preserving retention.
- Align dump expiration and version lifecycle to the approved seven-day recovery obligation.
- Consider per-object transition charges and class minimum object-size and duration rules.
Explanation
Correct Answer
B:Age-based transitions align per-class costs with expected access frequency and recovery needs. Inspect transitioned object versions and calculate restore costs.
Incorrect Answers
A:Lifecycle rules cannot override applicable Object Lock retention merely for savings. Use lifecycle transitions to suitable progressively colder S3 classes while preserving retention. Inspect transitioned object versions and calculate restore costs.
C:Storage lifecycle should retain only justified copies while ensuring recovery and compliance evidence. Use lifecycle transitions to suitable progressively colder S3 classes while preserving retention. Inspect transitioned object versions and calculate restore costs.
D:Frequent transitions of short-lived tiny objects can cost more than keeping them in Standard. Use lifecycle transitions to suitable progressively colder S3 classes while preserving retention. Inspect transitioned object versions and calculate restore costs.
Question 652
A bucket's storage costs rise after objects are logically deleted because many prior versions remain. What setting should be audited?
- Retain locked object versions until their retention expires and model the unavoidable storage.
- Apply S3 lifecycle rules for noncurrent versions after the approved retention period.
- Abort incomplete multipart uploads after a safe configured age.
- Review lifecycle expiration for noncurrent versions and expired object delete markers.
Explanation
Correct Answer
D:Deleting the current view is not equivalent to removing every stored version; retention settings determine safe cleanup. Use ListObjectVersions to measure residual storage before and after policy.
Incorrect Answers
A:Lifecycle rules cannot override applicable Object Lock retention merely for savings. Review lifecycle expiration for noncurrent versions and expired object delete markers. Use ListObjectVersions to measure residual storage before and after policy.
B:Versioning can accumulate old versions; lifecycle expiration manages eligible historic versions without removing required copies early. Review lifecycle expiration for noncurrent versions and expired object delete markers. Use ListObjectVersions to measure residual storage before and after policy.
C:S3 retains uploaded parts until completion or abort, so stale parts incur storage charges. Deleting the current view is not equivalent to removing every stored version; retention settings determine safe cleanup.
Question 653
An S3 lifecycle transition immediately moves tiny short-lived objects into Standard-IA and increases the invoice. What caused the unexpected charge?
- Scope replication rules to only required prefixes and tags with an explicit recovery policy.
- Retain locked object versions until their retention expires and model the unavoidable storage.
- Consider per-object transition charges and class minimum object-size and duration rules.
- Use lifecycle transitions to suitable progressively colder S3 classes while preserving retention.
Explanation
Correct Answer
C:Frequent transitions of short-lived tiny objects can cost more than keeping them in Standard. Calculate transition-plus-duration fees from a realistic object distribution.
Incorrect Answers
A:Selective replication avoids paying for copied objects that have no DR or governance purpose. Consider per-object transition charges and class minimum object-size and duration rules. Calculate transition-plus-duration fees from a realistic object distribution.
B:Lifecycle rules cannot override applicable Object Lock retention merely for savings. Consider per-object transition charges and class minimum object-size and duration rules. Calculate transition-plus-duration fees from a realistic object distribution.
D:Age-based transitions align per-class costs with expected access frequency and recovery needs. Consider per-object transition charges and class minimum object-size and duration rules. Calculate transition-plus-duration fees from a realistic object distribution.
Question 654
An object is under S3 Object Lock compliance retention; a lifecycle rule attempts to expire it early. What must the cost plan respect?
- Review lifecycle expiration for noncurrent versions and expired object delete markers.
- Retain locked object versions until their retention expires and model the unavoidable storage.
- Align dump expiration and version lifecycle to the approved seven-day recovery obligation.
- Abort incomplete multipart uploads after a safe configured age.
Explanation
Correct Answer
B:Lifecycle rules cannot override applicable Object Lock retention merely for savings. Inspect locked version retention dates and expiration results.
Incorrect Answers
A:Deleting the current view is not equivalent to removing every stored version; retention settings determine safe cleanup. Retain locked object versions until their retention expires and model the unavoidable storage. Inspect locked version retention dates and expiration results.
C:Storage lifecycle should retain only justified copies while ensuring recovery and compliance evidence. Retain locked object versions until their retention expires and model the unavoidable storage. Inspect locked version retention dates and expiration results.
D:S3 retains uploaded parts until completion or abort, so stale parts incur storage charges. Lifecycle rules cannot override applicable Object Lock retention merely for savings.
Question 655
A daily dump retains twenty identical full copies in one prefix although only seven days of backups are required. Which safe cost approach fits?
- Align dump expiration and version lifecycle to the approved seven-day recovery obligation.
- Retain locked object versions until their retention expires and model the unavoidable storage.
- Use lifecycle transitions to suitable progressively colder S3 classes while preserving retention.
- Apply S3 lifecycle rules for noncurrent versions after the approved retention period.
Explanation
Correct Answer
A:Storage lifecycle should retain only justified copies while ensuring recovery and compliance evidence. Restore from the oldest required dump and inspect expiration dates.
Incorrect Answers
B:Lifecycle rules cannot override applicable Object Lock retention merely for savings. Align dump expiration and version lifecycle to the approved seven-day recovery obligation. Restore from the oldest required dump and inspect expiration dates.
C:Age-based transitions align per-class costs with expected access frequency and recovery needs. Align dump expiration and version lifecycle to the approved seven-day recovery obligation. Restore from the oldest required dump and inspect expiration dates.
D:Versioning can accumulate old versions; lifecycle expiration manages eligible historic versions without removing required copies early. Align dump expiration and version lifecycle to the approved seven-day recovery obligation. Restore from the oldest required dump and inspect expiration dates.
Question 656
A bucket replicates every temporary build artifact to another Region, doubling unneeded storage. What should change?
- Use lifecycle transitions to suitable progressively colder S3 classes while preserving retention.
- Consider per-object transition charges and class minimum object-size and duration rules.
- Apply S3 lifecycle rules for noncurrent versions after the approved retention period.
- Scope replication rules to only required prefixes and tags with an explicit recovery policy.
Explanation
Correct Answer
D:Selective replication avoids paying for copied objects that have no DR or governance purpose. Upload temporary and critical objects and compare destination replication.
Incorrect Answers
A:Age-based transitions align per-class costs with expected access frequency and recovery needs. Scope replication rules to only required prefixes and tags with an explicit recovery policy. Upload temporary and critical objects and compare destination replication.
B:Frequent transitions of short-lived tiny objects can cost more than keeping them in Standard. Scope replication rules to only required prefixes and tags with an explicit recovery policy. Upload temporary and critical objects and compare destination replication.
C:Versioning can accumulate old versions; lifecycle expiration manages eligible historic versions without removing required copies early. Scope replication rules to only required prefixes and tags with an explicit recovery policy. Upload temporary and critical objects and compare destination replication.
Question 657
A database uses gp2 volumes sized artificially large solely to gain IOPS; actual data occupies little space. Which storage redesign reduces cost while retaining measured performance?
- Benchmark gp3 against required throughput, latency and durability before replacing overprovisioned io2.
- Migrate eligible volumes to gp3 with independently provisioned capacity, IOPS and throughput.
- Reduce provisioned IOPS after workload benchmarking and documented performance headroom.
- Right-size the EBS volume using a supported filesystem migration or volume-recreation plan.
Explanation
Correct Answer
B:Gp3 separates performance from volume size and can avoid paying for unnecessary stored capacity. Compare provisioned settings and actual latency before and after migration.
Incorrect Answers
A:Provisioned IOPS families are justified by measured extreme I/O requirements, not a general performance label. Migrate eligible volumes to gp3 with independently provisioned capacity, IOPS and throughput. Compare provisioned settings and actual latency before and after migration.
C:Paying for idle provisioned performance is unnecessary when lower settings still meet the workload. Migrate eligible volumes to gp3 with independently provisioned capacity, IOPS and throughput. Compare provisioned settings and actual latency before and after migration.
D:EBS bills for provisioned capacity even when application files use much less space. Migrate eligible volumes to gp3 with independently provisioned capacity, IOPS and throughput. Compare provisioned settings and actual latency before and after migration.
Question 658
An EC2 instance hosts a rarely used development volume of 2 TB with only 50 GB occupied. What should be considered?
- Migrate eligible volumes to gp3 with independently provisioned capacity, IOPS and throughput.
- 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.
- Reduce provisioned IOPS after workload benchmarking and documented performance headroom.
Explanation
Correct Answer
C:EBS bills for provisioned capacity even when application files use much less space. Measure utilization and safely test a smaller replacement volume.
Incorrect Answers
A:Gp3 separates performance from volume size and can avoid paying for unnecessary stored capacity. Right-size the EBS volume using a supported filesystem migration or volume-recreation plan. Measure utilization and safely test a smaller replacement volume.
B:Detached EBS volumes continue incurring capacity charges even when no EC2 instance uses them. Right-size the EBS volume using a supported filesystem migration or volume-recreation plan. Measure utilization and safely test a smaller replacement volume.
D:Paying for idle provisioned performance is unnecessary when lower settings still meet the workload. Right-size the EBS volume using a supported filesystem migration or volume-recreation plan. Measure utilization and safely test a smaller replacement volume.
Question 659
An EBS volume has provisioned 20,000 IOPS but CloudWatch shows minimal I/O during peak traffic. How should spending be optimized?
- Right-size the EBS volume using a supported filesystem migration or volume-recreation plan.
- Reduce provisioned IOPS after workload benchmarking and documented performance headroom.
- Benchmark gp3 against required throughput, latency and durability before replacing overprovisioned io2.
- EBS snapshots are incremental and charges depend on stored changed data and retention.
Explanation
Correct Answer
B:Paying for idle provisioned performance is unnecessary when lower settings still meet the workload. Run a production-like I/O test at the proposed limit.
Incorrect Answers
A:EBS bills for provisioned capacity even when application files use much less space. Reduce provisioned IOPS after workload benchmarking and documented performance headroom. Run a production-like I/O test at the proposed limit.
C:Provisioned IOPS families are justified by measured extreme I/O requirements, not a general performance label. Reduce provisioned IOPS after workload benchmarking and documented performance headroom. Run a production-like I/O test at the proposed limit.
D:Snapshot storage tracks unique retained data blocks rather than charging each snapshot as an entire full volume. Paying for idle provisioned performance is unnecessary when lower settings still meet the workload.
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.