Amazon AWS SAA-C03 Cost-Optimized Storage, Tiering, Lifecycle, Backup, Archive, and Transfer Practice Test 3

 

Topic 17 Practice Test 3 covers Cost-Optimized Storage, Tiering, Lifecycle, Backup, Archive, and Transfer for AWS SAA-C03. For broader exam preparation, review the AWS SAA-C03 Exam Dumps. Every option includes focused technical reasoning explaining both the AWS architecture concept and its fit to the scenario.

Question 1

A serverless application writes 2 MB temporary results that are frequently read for ten days and then deleted. A proposal would put every object directly into Standard-IA. Which storage choice better matches the short lifetime? Choose ONE.

1. S3 Intelligent-Tiering
2. S3 Standard-IA
3. S3 Glacier Instant Retrieval
4. S3 Standard

Correct Answer(s)

 

D

Rationale

1. S3 Intelligent-Tiering automatically moves eligible objects among access tiers as their observed access pattern changes, with optional asynchronous archive tiers. This case requires avoid colder-tier minimum-duration and retrieval costs for frequently read objects deleted within days. It is less attractive for many sub-128 KB objects because those objects are not automatically tiered by the class.
2. S3 Standard-IA stores long-lived cold objects with multi-AZ resilience and immediate access, using lower capacity pricing plus access fees. This case requires avoid colder-tier minimum-duration and retrieval costs for frequently read objects deleted within days. Data that is deleted early or read often can lose the expected savings because minimum-duration and access charges still apply.
3. S3 Glacier Instant Retrieval combines archive-oriented capacity pricing with real-time access for long-lived data that is seldom opened. This case requires avoid colder-tier minimum-duration and retrieval costs for frequently read objects deleted within days. Objects expected to disappear quickly or be read often do not fit its archive-duration and access-cost model.
4. S3 Standard provides general-purpose multi-AZ object storage for frequently accessed data without minimum storage-duration charges. The requirement is to avoid colder-tier minimum-duration and retrieval costs for frequently read objects deleted within days. S3 Standard matches the hot ten-day lifetime; moving directly to Standard-IA would pay for an infrequent-access economic model the objects never reach.

 

Question 2

A reporting export is written once, read once around day 35, and deleted at day 45. Objects are large and must remain immediately readable across multiple Availability Zones. Which class is generally more appropriate than a 90-day archive class? Choose ONE.

1. S3 Glacier Deep Archive
2. S3 Standard-IA
3. S3 One Zone-IA
4. S3 Glacier Instant Retrieval

Correct Answer(s)

 

B

Rationale

1. S3 Glacier Deep Archive provides Amazon S3’s lowest-cost long-term archive tier for data that can tolerate hours-long restoration. This case requires use a multi-AZ infrequent-access class whose minimum duration better matches a 45-day object lifetime. The 180-day minimum duration and long restore window make it unsuitable for shorter retention or rapid operational recovery.
2. S3 Standard-IA keeps infrequently accessed objects across several Availability Zones while retaining millisecond reads and charging for retrievals. The requirement is to use a multi-AZ infrequent-access class whose minimum duration better matches a 45-day object lifetime. Standard-IA’s 30-day minimum is compatible with the stated lifespan and retains immediate multi-AZ reads, unlike 90- or 180-day archive economics.
3. S3 One Zone-IA stores cold recreatable objects inside one chosen Availability Zone and prices capacity below multi-AZ infrequent-access storage. This case requires use a multi-AZ infrequent-access class whose minimum duration better matches a 45-day object lifetime. Loss of that selected Availability Zone can make the data unavailable, so irreplaceable data needing regional resilience belongs elsewhere.
4. S3 Glacier Instant Retrieval places archive data in a lower-cost class while still providing millisecond retrieval for each object. This case requires use a multi-AZ infrequent-access class whose minimum duration better matches a 45-day object lifetime. Its 90-day minimum and retrieval pricing are a poor match for short retention or frequent reads.

 

Question 3

Audit packages are retained for 120 days and restored only if an investigation opens. Restore latency of several hours is acceptable. Which archive class avoids the 180-day minimum-duration mismatch of Deep Archive? Choose ONE.

1. S3 Glacier Instant Retrieval
2. S3 Glacier Deep Archive
3. S3 Glacier Flexible Retrieval
4. S3 Standard

Correct Answer(s)

 

C

Rationale

1. S3 Glacier Instant Retrieval combines archive-oriented capacity pricing with real-time access for long-lived data that is seldom opened. This case requires use an archive tier compatible with a 120-day retention period and asynchronous restoration. Objects expected to disappear quickly or be read often do not fit its archive-duration and access-cost model.
2. S3 Glacier Deep Archive provides Amazon S3’s lowest-cost long-term archive tier for data that can tolerate hours-long restoration. This case requires use an archive tier compatible with a 120-day retention period and asynchronous restoration. The 180-day minimum duration and long restore window make it unsuitable for shorter retention or rapid operational recovery.
3. S3 Glacier Flexible Retrieval provides low-cost archive storage for data that can tolerate restore workflows measured in minutes to hours. Glacier Flexible Retrieval has archive economics and a 90-day minimum duration, fitting the retention window without paying Deep Archive’s longer minimum. That outcome matches 120-day asynchronous archive for this workload.
4. S3 Standard provides general-purpose multi-AZ object storage for frequently accessed data without minimum storage-duration charges. This case requires use an archive tier compatible with a 120-day retention period and asynchronous restoration. Its storage price is higher than colder classes, so predictable long-lived archives can usually be stored more cheaply elsewhere.

 

Question 4

A telemetry platform wants lifecycle tiering for 50 KB objects. A newly created lifecycle rule leaves them in Standard because current S3 lifecycle behavior does not transition sub-128 KB objects by default. Economic analysis still shows a net benefit for this unusually long-lived dataset. What should be added? Choose ONE.

1. Use an S3 Lifecycle object-size filter for small-object transitions
2. S3 Intelligent-Tiering
3. Aggregate small records into larger S3 objects
4. S3 Standard-IA

Correct Answer(s)

 

A

Rationale

1. Use an S3 Lifecycle object-size filter for small-object transitions overrides the default 128 KB minimum transition behavior when a deliberate economic analysis justifies transitioning smaller objects. An explicit object-size filter can allow the lifecycle rule to include smaller objects when the team has deliberately validated that savings exceed per-object costs. That outcome matches small-object lifecycle override for this workload.
2. S3 Intelligent-Tiering automatically moves eligible objects among access tiers as their observed access pattern changes, with optional asynchronous archive tiers. This case requires override the default minimum transition size only after confirming small-object economics. It is less attractive for many sub-128 KB objects because those objects are not automatically tiered by the class.
3. Aggregate small records into larger S3 objects reduces per-object request, transition, and archive metadata overhead by packaging many tiny records into fewer larger objects. This case requires override the default minimum transition size only after confirming small-object economics. Aggregation adds packaging and extraction logic, so it is a poor fit when every record must be independently updated or fetched at random.
4. S3 Standard-IA keeps infrequently accessed objects across several Availability Zones while retaining millisecond reads and charging for retrievals. Its 30-day minimum and retrieval charges weaken the economics for short-lived or frequently read objects. Because the scenario must override the default minimum transition size only after confirming small-object economics, this option misses small-object lifecycle override.

 

Question 5

An image pipeline replaces most objects several times during their first 20 days, but objects that survive past day 45 remain unchanged for years. A rule currently transitions everything to Standard-IA on day 1. What change better aligns lifecycle timing with actual churn? Choose ONE.

1. S3 Storage Class Analysis
2. S3 Lifecycle expiration
3. Delay the S3 Lifecycle transition until objects are unlikely to change or be deleted
4. S3 Standard-IA

Correct Answer(s)

 

C

Rationale

1. S3 Storage Class Analysis analyzes access patterns to help determine when objects are good candidates to transition from Standard to Standard-IA. This case requires keep volatile young objects out of minimum-duration classes until the replacement window is over. It does not automatically move objects and is not a substitute for Intelligent-Tiering when access patterns remain unpredictable.
2. S3 Lifecycle expiration enforces time-based deletion of current S3 objects without a separate cleanup application. Current-object expiration leaves other storage categories, such as noncurrent versions and abandoned upload parts, untouched. Because the scenario must keep volatile young objects out of minimum-duration classes until the replacement window is over, this option misses lifecycle timing after churn.
3. Delay the S3 Lifecycle transition until objects are unlikely to change or be deleted keeps young objects in Standard until they have survived the churn window, avoiding premature minimum-duration and transition costs. Delaying the transition prevents repeated early-deletion and transition costs during the high-churn period while still tiering stable survivors later. That outcome matches lifecycle timing after churn for this workload.
4. S3 Standard-IA stores long-lived cold objects with multi-AZ resilience and immediate access, using lower capacity pricing plus access fees. This case requires keep volatile young objects out of minimum-duration classes until the replacement window is over. Data that is deleted early or read often can lose the expected savings because minimum-duration and access charges still apply.

 

Question 6

A data team believes reports should move to Standard-IA after 14 days, but it has no evidence that objects are actually cold by then. Which S3 feature can analyze access patterns and help choose an evidence-based Standard-to-IA transition age? Choose ONE.

1. S3 Storage Class Analysis
2. S3 Intelligent-Tiering
3. S3 Inventory
4. S3 Storage Lens cost-optimization metrics

Correct Answer(s)

 

A

Rationale

1. S3 Storage Class Analysis analyzes access patterns to help determine when objects are good candidates to transition from Standard to Standard-IA. Storage Class Analysis is intended to analyze object access patterns and inform transition timing instead of relying on a guessed age threshold. That outcome matches evidence-based transition timing for this workload.
2. S3 Intelligent-Tiering automatically moves eligible objects among access tiers as their observed access pattern changes, with optional asynchronous archive tiers. This case requires measure established access behavior to decide when Standard-to-IA transitions make economic sense. It is less attractive for many sub-128 KB objects because those objects are not automatically tiered by the class.
3. S3 Inventory produces scheduled object-level listings with metadata such as size, storage class, encryption, and version information. It is a reporting dataset rather than an automatic tiering engine or real-time performance mechanism. Because the scenario must measure established access behavior to decide when Standard-to-IA transitions make economic sense, this option misses evidence-based transition timing.
4. S3 Storage Lens cost-optimization metrics provides organization-scale visibility into storage usage and cost opportunities such as old multipart parts and noncurrent versions. This case requires measure established access behavior to decide when Standard-to-IA transitions make economic sense. It identifies optimization opportunities but does not itself transition or delete data.

 

Question 7

An S3 Intelligent-Tiering bucket must keep every object synchronously readable today, but records untouched for a year may be restored asynchronously when needed. Which configuration adds lower-cost capacity only for the sufficiently cold subset? Choose ONE.

1. S3 Glacier Instant Retrieval
2. Enable S3 Intelligent-Tiering Archive Access tiers
3. S3 Lifecycle expiration
4. S3 Glacier Deep Archive

Correct Answer(s)

 

B

Rationale

1. S3 Glacier Instant Retrieval combines archive-oriented capacity pricing with real-time access for long-lived data that is seldom opened. This case requires retain adaptive normal tiers while allowing very old objects to enter asynchronous archive access. Objects expected to disappear quickly or be read often do not fit its archive-duration and access-cost model.
2. Enable S3 Intelligent-Tiering Archive Access tiers lets Intelligent-Tiering move sufficiently cold eligible objects into asynchronous Archive Access or Deep Archive Access tiers. The optional archive tiers extend Intelligent-Tiering for cold objects without replacing the class or forcing all objects into a fixed archive rule. That outcome matches selective automatic archive access for this workload.
3. S3 Lifecycle expiration enforces time-based deletion of current S3 objects without a separate cleanup application. Current-object expiration leaves other storage categories, such as noncurrent versions and abandoned upload parts, untouched. Because the scenario must retain adaptive normal tiers while allowing very old objects to enter asynchronous archive access, this option misses selective automatic archive access.
4. S3 Glacier Deep Archive provides Amazon S3’s lowest-cost long-term archive tier for data that can tolerate hours-long restoration. This case requires retain adaptive normal tiers while allowing very old objects to enter asynchronous archive access. The 180-day minimum duration and long restore window make it unsuitable for shorter retention or rapid operational recovery.

 

Question 8

An organization wants one view to rank buckets by incomplete multipart bytes and noncurrent-version growth, then apply cleanup only where those metrics show waste. Which approach is strongest? Choose ONE.

1. S3 Inventory
2. S3 Storage Lens cost-optimization metrics
3. S3 Lifecycle expiration
4. Use S3 Storage Lens to locate old multipart uploads and excessive noncurrent versions, then add targeted Lifecycle rules

Correct Answer(s)

 

D

Rationale

1. S3 Inventory produces scheduled object-level listings with metadata such as size, storage class, encryption, and version information. It is a reporting dataset rather than an automatic tiering engine or real-time performance mechanism. Because the scenario must combine cross-bucket diagnosis with targeted automated remediation rather than using either alone, this option misses diagnose then remediate S3 waste.
2. S3 Storage Lens cost-optimization metrics provides organization-scale visibility into storage usage and cost opportunities such as old multipart parts and noncurrent versions. This case requires combine cross-bucket diagnosis with targeted automated remediation rather than using either alone. It identifies optimization opportunities but does not itself transition or delete data.
3. S3 Lifecycle expiration removes current objects automatically after the age defined by a lifecycle rule. The scenario instead requires combine cross-bucket diagnosis with targeted automated remediation rather than using either alone. It does not automatically purge previous versions or unfinished multipart parts. That limitation conflicts with diagnose then remediate S3 waste.
4. Use S3 Storage Lens to locate old multipart uploads and excessive noncurrent versions, then add targeted Lifecycle rules combines account-scale cost visibility with automated cleanup at the specific buckets creating waste. Storage Lens identifies the waste concentration, and targeted Lifecycle actions remove the specific multipart or versioned data that creates recurring cost. That outcome matches diagnose then remediate S3 waste for this workload.

 

Question 9

A database server uses a 4 TiB gp2 volume only because the old design needed 12,000 IOPS. Current used capacity is 700 GiB and the same IOPS target can be provisioned separately. Which migration is the clearest cost optimization? Choose ONE.

1. EBS gp3
2. EBS st1 Throughput Optimized HDD
3. EBS sc1 Cold HDD
4. Amazon Data Lifecycle Manager for EBS snapshots

Correct Answer(s)

 

A

Rationale

1. EBS gp3 provides general-purpose SSD storage with capacity, IOPS, and throughput provisioned independently. The requirement is to right-size SSD capacity independently from required IOPS instead of paying for unused GiB. gp3 lets the architect provision the needed performance separately from volume size, so the storage allocation can follow real capacity demand.
2. EBS st1 Throughput Optimized HDD delivers low-cost magnetic storage optimized for frequently accessed, large sequential I/O and high throughput. This case requires right-size SSD capacity independently from required IOPS instead of paying for unused GiB. It performs poorly for small random I/O and cannot be used as a boot volume.
3. EBS sc1 Cold HDD provides the lowest-cost EBS block storage for infrequently accessed workloads dominated by large sequential I/O. This case requires right-size SSD capacity independently from required IOPS instead of paying for unused GiB. Its low IOPS and throughput profile is unsuitable for transactional or latency-sensitive random I/O.
4. Amazon Data Lifecycle Manager for EBS snapshots automates creation, retention, and expiration schedules for EBS snapshots and AMI-backed policies. This case requires right-size SSD capacity independently from required IOPS instead of paying for unused GiB. It is focused on EC2/EBS lifecycle automation rather than general S3 object-class transitions or cross-service backup policy.

 

Question 10

A general-purpose application was placed on expensive high-IOPS block storage years ago, but monitoring now shows moderate random I/O well within gp3 capabilities. Which change should be evaluated first for lower cost? Choose ONE.

1. EBS st1 Throughput Optimized HDD
2. EBS sc1 Cold HDD
3. EBS Snapshots Archive
4. EBS gp3

Correct Answer(s)

 

D

Rationale

1. EBS st1 Throughput Optimized HDD delivers low-cost magnetic storage optimized for frequently accessed, large sequential I/O and high throughput. This case requires move a moderate random-I/O workload to general-purpose SSD rather than paying for unnecessary premium IOPS capability. It performs poorly for small random I/O and cannot be used as a boot volume.
2. EBS sc1 Cold HDD provides the lowest-cost EBS block storage for infrequently accessed workloads dominated by large sequential I/O. This case requires move a moderate random-I/O workload to general-purpose SSD rather than paying for unnecessary premium IOPS capability. Its low IOPS and throughput profile is unsuitable for transactional or latency-sensitive random I/O.
3. EBS Snapshots Archive moves rarely accessed EBS snapshots to a lower-cost archive tier after converting the archived snapshot to a full snapshot. This case requires move a moderate random-I/O workload to general-purpose SSD rather than paying for unnecessary premium IOPS capability. Early permanent restore or deletion can trigger minimum-duration charges, and archive is poor for frequently restored snapshots.
4. EBS gp3 provides general-purpose SSD storage with capacity, IOPS, and throughput provisioned independently. The requirement is to move a moderate random-I/O workload to general-purpose SSD rather than paying for unnecessary premium IOPS capability. gp3 is designed for broad SSD workloads and can meet moderate measured requirements without the price of a specialized extreme-I/O design.

 

Question 11

A team deletes the oldest snapshot in a long EBS snapshot chain expecting an equal reduction in stored GiB, but newer snapshots still reference most of those blocks. Which statement should influence the cost plan? Choose ONE.

1. Disable Fast Snapshot Restore where immediate volume initialization is no longer required
2. Account for EBS snapshot incremental block references before deleting snapshots
3. EBS Snapshots Archive
4. Amazon Data Lifecycle Manager for EBS snapshots

Correct Answer(s)

 

B

Rationale

1. Disable Fast Snapshot Restore where immediate volume initialization is no longer required stops paying for Fast Snapshot Restore availability-zone acceleration while retaining the underlying snapshot. This case requires base savings estimates on referenced incremental blocks rather than treating each snapshot as an independent full copy. Disabling it sacrifices the specific immediate full-performance benefit that FSR provides to newly created volumes.
2. Account for EBS snapshot incremental block references before deleting snapshots recognizes that deleting one snapshot removes only blocks that no later snapshot still references. EBS preserves blocks referenced by later snapshots, so deleting an early snapshot may move accounting rather than eliminate the underlying stored data. That outcome matches snapshot reference economics for this workload.
3. EBS Snapshots Archive moves rarely accessed EBS snapshots to a lower-cost archive tier after converting the archived snapshot to a full snapshot. This case requires base savings estimates on referenced incremental blocks rather than treating each snapshot as an independent full copy. Early permanent restore or deletion can trigger minimum-duration charges, and archive is poor for frequently restored snapshots.
4. Amazon Data Lifecycle Manager for EBS snapshots automates creation, retention, and expiration schedules for EBS snapshots and AMI-backed policies. This case requires base savings estimates on referenced incremental blocks rather than treating each snapshot as an independent full copy. It is focused on EC2/EBS lifecycle automation rather than general S3 object-class transitions or cross-service backup policy.

 

Question 12

An AWS Backup rule moves eligible recovery points to cold storage after 30 days and is configured to delete them after 60 days. The configuration is rejected. What change aligns the lifecycle with cold-storage retention rules? Choose ONE.

1. S3 Glacier Deep Archive
2. AWS Backup lifecycle expiration
3. AWS Backup lifecycle transition to cold storage for supported resources
4. EBS Snapshots Archive

Correct Answer(s)

 

C

Rationale

1. S3 Glacier Deep Archive provides Amazon S3’s lowest-cost long-term archive tier for data that can tolerate hours-long restoration. This case requires set deletion at least 90 days after the cold-storage transition for a supported backup type. The 180-day minimum duration and long restore window make it unsuitable for shorter retention or rapid operational recovery.
2. AWS Backup lifecycle expiration automatically deletes recovery points after the approved retention period instead of keeping them indefinitely. This case requires set deletion at least 90 days after the cold-storage transition for a supported backup type. Shortening retention without governance approval can remove required restore points even though it reduces storage cost.
3. AWS Backup lifecycle transition to cold storage for supported resources moves eligible recovery points from warm to lower-cost cold storage while enforcing the cold-tier minimum-retention rules. AWS Backup requires cold recovery points to remain cold for at least 90 days, so a day-30 transition requires retention extending to at least day 120. That outcome matches valid backup cold retention for this workload.
4. EBS Snapshots Archive moves rarely accessed EBS snapshots to a lower-cost archive tier after converting the archived snapshot to a full snapshot. This case requires set deletion at least 90 days after the cold-storage transition for a supported backup type. Early permanent restore or deletion can trigger minimum-duration charges, and archive is poor for frequently restored snapshots.

 

Question 13

For a resource type with incremental AWS Backup behavior, a plan transitions the first warm full backup to cold after one day. The service then creates another warm full backup, increasing cost. Which adjustment follows AWS guidance? Choose ONE.

1. Amazon Data Lifecycle Manager for EBS snapshots
2. AWS Backup lifecycle transition to cold storage for supported resources
3. AWS Backup lifecycle expiration
4. S3 Lifecycle expiration

Correct Answer(s)

 

B

Rationale

1. Amazon Data Lifecycle Manager for EBS snapshots automates creation, retention, and expiration schedules for EBS snapshots and AMI-backed policies. This case requires delay cold transition long enough to avoid prematurely removing the warm full backup used by incrementals. It is focused on EC2/EBS lifecycle automation rather than general S3 object-class transitions or cross-service backup policy.
2. AWS Backup lifecycle transition to cold storage for supported resources moves eligible recovery points from warm to lower-cost cold storage while enforcing the cold-tier minimum-retention rules. AWS recommends not moving the supporting warm full backup to cold too quickly; keeping it warm for at least the advised initial period avoids forcing another full. That outcome matches incremental backup warm baseline for this workload.
3. AWS Backup lifecycle expiration automatically deletes recovery points after the approved retention period instead of keeping them indefinitely. This case requires delay cold transition long enough to avoid prematurely removing the warm full backup used by incrementals. Shortening retention without governance approval can remove required restore points even though it reduces storage cost.
4. S3 Lifecycle expiration enforces time-based deletion of current S3 objects without a separate cleanup application. This case requires delay cold transition long enough to avoid prematurely removing the warm full backup used by incrementals. Current-object expiration leaves other storage categories, such as noncurrent versions and abandoned upload parts, untouched.

 

Question 14

A team plans to use the EFS Archive class for very cold shared files, but the current file system uses a mode that is not compatible with Archive. Which design prerequisite should be addressed? Choose ONE.

1. EFS lifecycle management to IA and then Archive
2. EFS One Zone storage
3. Use EFS General Purpose performance mode with Elastic throughput before relying on EFS Archive
4. EFS lifecycle transition back to Standard on first access

Correct Answer(s)

 

C

Rationale

1. EFS lifecycle management to IA and then Archive tiers cold file contents first to IA and later to the lower-cost EFS Archive class after longer inactivity. This case requires use EFS modes that actually support Archive before configuring the lifecycle transition. Archive requires compatible EFS performance and throughput modes and is unsuitable for hot latency-sensitive file content.
2. EFS One Zone storage keeps EFS file-system data in one Availability Zone at a lower storage price than regional EFS. This case requires use EFS modes that actually support Archive before configuring the lifecycle transition. It does not provide the multi-AZ durability of Regional EFS, so irreplaceable shared data needs a regional design.
3. Use EFS General Purpose performance mode with Elastic throughput before relying on EFS Archive uses the EFS modes that support the Archive storage class and can therefore participate in lifecycle tiering into Archive. EFS Archive is available with General Purpose performance and Elastic throughput, so lifecycle savings depend on meeting those compatibility prerequisites. That outcome matches EFS Archive compatibility for this workload.
4. EFS lifecycle transition back to Standard on first access moves a file from IA or Archive back to Standard when it is read so subsequent hot accesses avoid repeated lower-tier access charges. This case requires use EFS modes that actually support Archive before configuring the lifecycle transition. Moving files back adds Standard storage cost and is unnecessary when accesses remain isolated and rare.

 

Question 15

Users list directories on an EFS file system many times a day, but rarely open the file contents stored in IA. The team fears directory listings will constantly rewarm files into Standard. Which interpretation is correct for cost planning? Choose ONE.

1. EFS lifecycle management to IA and then Archive
2. EFS One Zone storage
3. EFS lifecycle transition back to Standard on first access
4. EFS lifecycle management to Infrequent Access

Correct Answer(s)

 

D

Rationale

1. EFS lifecycle management to IA and then Archive tiers cold file contents first to IA and later to the lower-cost EFS Archive class after longer inactivity. This case requires keep cold file contents tiered because metadata listing alone does not count as file-content access for lifecycle. Archive requires compatible EFS performance and throughput modes and is unsuitable for hot latency-sensitive file content.
2. EFS One Zone storage keeps EFS file-system data in one Availability Zone at a lower storage price than regional EFS. This case requires keep cold file contents tiered because metadata listing alone does not count as file-content access for lifecycle. It does not provide the multi-AZ durability of Regional EFS, so irreplaceable shared data needs a regional design.
3. EFS lifecycle transition back to Standard on first access moves a file from IA or Archive back to Standard when it is read so subsequent hot accesses avoid repeated lower-tier access charges. This case requires keep cold file contents tiered because metadata listing alone does not count as file-content access for lifecycle. Moving files back adds Standard storage cost and is unnecessary when accesses remain isolated and rare.
4. EFS lifecycle management to Infrequent Access moves file contents that have not been accessed for the configured period from Standard into lower-cost EFS IA storage. EFS keeps metadata in Standard and directory metadata operations do not count as access to the IA file content, so listing alone does not defeat tiering. That outcome matches EFS metadata versus content access for this workload.

 

Question 16

S3 File Gateway writes directly to One Zone-IA for a workload whose applications frequently change timestamps and permissions during the first week. The gateway creates new object versions during these metadata updates, causing early-deletion fees. What architecture is safer? Choose ONE.

1. S3 File Gateway writing to S3 Standard with S3 Lifecycle tiering
2. S3 One Zone-IA
3. S3 Standard-IA
4. EFS One Zone storage

Correct Answer(s)

 

A

Rationale

1. S3 File Gateway writing to S3 Standard with S3 Lifecycle tiering presents an on-premises file interface with local caching while S3 stores durable objects that can later be lifecycle-tiered. Using Standard as the initial File Gateway class and lifecycle-tiering later avoids repeatedly resetting objects inside a minimum-duration infrequent-access class. That outcome matches gateway metadata churn for this workload.
2. S3 One Zone-IA stores cold recreatable objects inside one chosen Availability Zone and prices capacity below multi-AZ infrequent-access storage. This case requires let frequently modified gateway objects stabilize in Standard before lower-cost transition. Loss of that selected Availability Zone can make the data unavailable, so irreplaceable data needing regional resilience belongs elsewhere.
3. S3 Standard-IA keeps infrequently accessed objects across several Availability Zones while retaining millisecond reads and charging for retrievals. Its 30-day minimum and retrieval charges weaken the economics for short-lived or frequently read objects. Because the scenario must let frequently modified gateway objects stabilize in Standard before lower-cost transition, this option misses gateway metadata churn.
4. EFS One Zone storage keeps EFS file-system data in one Availability Zone at a lower storage price than regional EFS. This case requires let frequently modified gateway objects stabilize in Standard before lower-cost transition. It does not provide the multi-AZ durability of Regional EFS, so irreplaceable shared data needs a regional design.

 

Question 17

A lifecycle rule created this year should move objects to a colder class, but 90 KB objects never transition. The business does not actually need those tiny objects archived and wants to avoid per-object transition overhead. What is the most cost-conscious response? Choose ONE.

1. An S3 Lifecycle rule filtered by prefix and object tags
2. Use an S3 Lifecycle object-size filter for small-object transitions
3. S3 Glacier Instant Retrieval
4. Aggregate small records into larger S3 objects

Correct Answer(s)

 

D

Rationale

1. An S3 Lifecycle rule filtered by prefix and object tags applies transition or expiration actions only to objects that match the selected naming and metadata criteria. This case requires reduce object count before archive rather than forcing millions of tiny objects through chargeable transitions. A bucket-wide unfiltered rule would change objects outside the intended compliance or business subset.
2. Use an S3 Lifecycle object-size filter for small-object transitions overrides the default 128 KB minimum transition behavior when a deliberate economic analysis justifies transitioning smaller objects. This case requires reduce object count before archive rather than forcing millions of tiny objects through chargeable transitions. Forcing tiny objects into colder classes can cost more than leaving them in Standard because request and metadata charges are per object.
3. S3 Glacier Instant Retrieval combines archive-oriented capacity pricing with real-time access for long-lived data that is seldom opened. This case requires reduce object count before archive rather than forcing millions of tiny objects through chargeable transitions. Objects expected to disappear quickly or be read often do not fit its archive-duration and access-cost model.
4. Aggregate small records into larger S3 objects reduces per-object request, transition, and archive metadata overhead by packaging many tiny records into fewer larger objects. Because tiny records are numerous and do not require independent archival, aggregation attacks the economic problem directly instead of overriding the protective size default. That outcome matches small-object archive redesign for this workload.

 

Question 18

A versioned bucket has millions of incomplete multipart-upload bytes and old noncurrent versions. Leadership wants a repeatable process that first identifies the worst buckets across the organization and then prevents the same waste from returning. What should the architect implement? Choose ONE.

1. Use S3 Storage Lens to locate old multipart uploads and excessive noncurrent versions, then add targeted Lifecycle rules
2. S3 Storage Lens cost-optimization metrics
3. S3 Lifecycle noncurrent-version expiration
4. AbortIncompleteMultipartUpload lifecycle action

Correct Answer(s)

 

A

Rationale

1. Use S3 Storage Lens to locate old multipart uploads and excessive noncurrent versions, then add targeted Lifecycle rules combines account-scale cost visibility with automated cleanup at the specific buckets creating waste. Storage Lens provides the cross-account evidence, while targeted abort and noncurrent-version lifecycle rules remove and prevent the identified storage waste. That outcome matches S3 cost governance loop for this workload.
2. S3 Storage Lens cost-optimization metrics provides organization-scale visibility into storage usage and cost opportunities such as old multipart parts and noncurrent versions. This case requires locate the cost hotspots globally and then automate the appropriate bucket-specific cleanup. It identifies optimization opportunities but does not itself transition or delete data.
3. S3 Lifecycle noncurrent-version expiration permanently removes older object versions after they have remained noncurrent for the configured period. This case requires locate the cost hotspots globally and then automate the appropriate bucket-specific cleanup. It targets noncurrent versions rather than the live current version, so it does not implement ordinary current-object retention.
4. AbortIncompleteMultipartUpload lifecycle action stops multipart uploads that never complete and removes their stored parts after a chosen number of days. This case requires locate the cost hotspots globally and then automate the appropriate bucket-specific cleanup. It affects incomplete uploads only and does not expire completed objects or previous versions.

 

Question 19

A data lake stores objects with unpredictable access. Some datasets suddenly become hot again after months of inactivity, and the team wants to avoid maintaining transition and restore rules for each prefix. Which S3 class most directly handles that uncertainty? Choose ONE.

1. S3 Glacier Deep Archive
2. S3 Storage Class Analysis
3. S3 Intelligent-Tiering
4. S3 Standard-IA

Correct Answer(s)

 

C

Rationale

1. S3 Glacier Deep Archive provides Amazon S3’s lowest-cost long-term archive tier for data that can tolerate hours-long restoration. This case requires adapt automatically when cold data becomes active again without manual lifecycle retuning. The 180-day minimum duration and long restore window make it unsuitable for shorter retention or rapid operational recovery.
2. S3 Storage Class Analysis analyzes access patterns to help determine when objects are good candidates to transition from Standard to Standard-IA. This case requires adapt automatically when cold data becomes active again without manual lifecycle retuning. It does not automatically move objects and is not a substitute for Intelligent-Tiering when access patterns remain unpredictable.
3. S3 Intelligent-Tiering automatically moves eligible objects among access tiers as their observed access pattern changes, with optional asynchronous archive tiers. Intelligent-Tiering monitors eligible object access and changes tiers automatically, which is preferable when the future hot/cold boundary cannot be predicted reliably. That outcome matches changing data-lake access for this workload.
4. S3 Standard-IA stores long-lived cold objects with multi-AZ resilience and immediate access, using lower capacity pricing plus access fees. This case requires adapt automatically when cold data becomes active again without manual lifecycle retuning. Data that is deleted early or read often can lose the expected savings because minimum-duration and access charges still apply.

 

Question 20

A compliance archive contains very large objects retained for ten years. Retrieval is extremely rare and can wait many hours, while the primary goal is the lowest possible S3 storage price. Which class should be selected? Choose ONE.

1. S3 Glacier Instant Retrieval
2. S3 Glacier Deep Archive
3. S3 Glacier Flexible Retrieval
4. S3 Standard-IA

Correct Answer(s)

 

B

Rationale

1. S3 Glacier Instant Retrieval places archive data in a lower-cost class while still providing millisecond retrieval for each object. This case requires use the lowest-cost S3 class for extremely long-lived data with very infrequent asynchronous reads. Its 90-day minimum and retrieval pricing are a poor match for short retention or frequent reads.
2. S3 Glacier Deep Archive provides Amazon S3’s lowest-cost long-term archive tier for data that can tolerate hours-long restoration. Deep Archive aligns with multi-year retention and rare restores, allowing the design to trade retrieval speed for the lowest long-term storage rate. That outcome matches decade-long archive for this workload.
3. S3 Glacier Flexible Retrieval provides low-cost archive storage for data that can tolerate restore workflows measured in minutes to hours. This case requires use the lowest-cost S3 class for extremely long-lived data with very infrequent asynchronous reads. Objects require restore before normal access, so it cannot satisfy workloads that need synchronous millisecond reads.
4. S3 Standard-IA keeps infrequently accessed objects across several Availability Zones while retaining millisecond reads and charging for retrievals. This case requires use the lowest-cost S3 class for extremely long-lived data with very infrequent asynchronous reads. Its 30-day minimum and retrieval charges weaken the economics for short-lived or frequently read objects.

• < Amazon AWS SAA-C03 Cost-Optimized Storage, Tiering, Lifecycle, Backup, Archive, and Transfer Practice Test 2
• Amazon AWS SAA-C03 Cost-Optimized Compute, Purchasing Models, Rightsizing, and Elasticity Practice Test 1 >