Amazon AWS Certified Solutions Architect - Associate SAA-C03 Practice Test 67

Question 660

Operations must attach revised compliance tags to millions of existing S3 objects and retain an auditable completion report. Which managed bulk action?

Run an S3 Batch Operations job with an empty manifest and assume it discovers every noncompliant object automatically.
Use S3 Storage Lens to identify objects but assume it writes a new compliance tag onto every old object automatically.
Run a single AWS CLI PutObjectTagging command with a bucket ARN as the object key and assume it tags every existing object under that bucket.
Use S3 Batch Operations with an appropriate object manifest, IAM permissions and completion report.

Explanation

Correct Answer

Batch Operations can apply supported actions at scale to enumerated object keys without per-object manual loops.

Incorrect Answers

Batch Operations acts on explicitly selected keys and versions from its manifest or supported inventory selection.

Storage Lens provides reporting; a supported Batch Operations job with explicit manifest and permissions is needed for changes.

PutObjectTagging targets particular objects; applying tags to millions of keys requires enumerating/manifesting those objects or an orchestrated supported bulk action.

Question 661

A finance account spends hundreds monthly on EBS volumes whose EC2 instances were terminated; several volumes are unattached and unused. What is the right inventory action?

Find unattached EBS volumes and verify data/retention ownership before snapshotting or deleting unnecessary volumes.
Delete every unattached EBS volume without checking whether it contains retained recovery data or is owned by a legal-hold workflow.
Assume termination of the former EC2 host always deletes all separately attached EBS volumes and removes their storage charges.
Keep a detached EBS volume in the inventory but disable the attached instance termination protection, expecting the unused volume to stop billing while it remains allocated.

Explanation

Correct Answer

Unattached EBS volume capacity remains chargeable until deleted, regardless of a running instance.

Incorrect Answers

Unattached volumes incur charges, but business retention and recovery ownership must be checked before snapshot or deletion.

Only volumes configured for deletion on instance termination are automatically removed; detached retained EBS volumes may remain billable.

Instance termination protection and EBS chargeability are distinct. A retained unattached volume remains provisioned and billed until it is deleted; assess retention obligations and snapshot needs first.

Question 662

A download site serves immutable product images to international customers from S3. The origin receives millions of repeated GET requests with high egress spend. Which delivery change?

Disable CloudFront caching and send every international request to S3 while assuming the absence of cache lookup fees always minimizes total cost.
Enable S3 Transfer Acceleration for all image GET requests and assume it creates persistent globally shared caches for repeated downloads.
Enable CloudFront caching with appropriate TTL/cache keys and confirm origin-to-edge hit-rate improvement.
Disable HTTP cache headers on the immutable images so that every CloudFront edge must re-fetch them from S3.

Explanation

Correct Answer

Edge cache hits can eliminate repeated S3 GET origin requests and reduce origin data-transfer charges subject to CDN pricing.

Incorrect Answers

A useful edge hit ratio can reduce origin requests and data transfer; full cost requires comparing CloudFront distribution and origin charges.

Transfer Acceleration optimizes supported data transfer paths, mainly uploads; it is not an edge object cache for repeated global HTTP reads.

Disabling caching defeats the expected cache-hit improvement and continues costly origin requests. Use suitable cache keys and TTLs for immutable assets.

Question 663

After migrating frequently downloaded files to S3 Standard-IA, the total monthly bill rises although stored bytes are unchanged. Why?

Frequent GET retrieval charges and storage-class minimum charges can exceed the Standard-IA storage-rate discount.
Every S3 Standard-IA GET request is free and minimum storage duration charges apply only to Glacier Deep Archive.
Use an S3 Lifecycle rule that repeatedly transitions heavily downloaded files from Standard-IA to the same Standard-IA class, assuming the rule eliminates retrieval fees.
Assume moving all frequently accessed objects to Standard-IA always lowers total S3 charges, independent of object size and access frequency.

Explanation

Correct Answer

Calculate retrieval frequency and object size, not simply price per GiB stored.

Incorrect Answers

S3 Standard-IA has retrieval/request costs and a 30-day minimum; frequent access may make Standard cheaper overall.

Lifecycle rules do not waive Standard-IA retrieval or minimum-duration charges. Repeated GET volume still determines whether its lower at-rest rate saves money compared with Standard.

Storage-class selection needs total storage, retrieval, request and minimum-size/duration economics; frequent access may make Standard preferable.

Question 664

A team stores 60,000 objects of 32 KiB each in S3 Intelligent-Tiering and expects automatic lower-tier movement after 30 days. Costs remain high. Why?

Objects smaller than 128 KiB are not monitored or eligible for automatic tiering.
Intelligent-Tiering moves objects below 128 KiB to its archive tiers automatically and charges no monitoring cost per small object.
Increase the S3 Intelligent-Tiering idle threshold to 90 days and assume this causes 32-KiB objects to become monitored and eligible for automated tier changes.
Configure an S3 lifecycle transition of tiny objects and expect Intelligent-Tiering monitoring to treat the object as eligible without checking size eligibility.

Explanation

Correct Answer

Small-object economics differ; assess packing/retention or another suitable storage class.

Incorrect Answers

Objects below 128 KiB are not monitored for auto-tiering and remain in the Frequent Access tier under documented behavior.

Changing an inactivity threshold does not remove the 128-KiB automatic-tiering eligibility floor. Objects below it remain in the Frequent Access tier.

Putting small objects into Intelligent-Tiering does not override its automatic-tiering size rules; check the current tiering and minimum-size constraints.

Question 665

A customer restores a Glacier Flexible Retrieval object and immediately calls GetObject before the restoration has completed. Why is it unavailable?

Glacier Flexible Retrieval archive objects are always directly readable through GET without prior RestoreObject activity.
Archived Flexible Retrieval objects require a restore job before ordinary access, unless a supported retrieval process completes.
Submit an S3 Glacier Flexible Retrieval restore request and assume an ordinary GetObject returns archived bytes synchronously before the restore finishes.
Use a restored-object expiration date as proof that the Glacier Flexible Retrieval object is already readable before its restore job finishes.

Explanation

Correct Answer

Retrieval tier selection affects completion delay; restoring is not equivalent to an immediate Standard object read.

Incorrect Answers

Flexible Retrieval archived objects require restoration before normal object access; they are not instant-access archive objects.

Restore is an asynchronous job; archived Flexible Retrieval content becomes ordinarily accessible after the restored copy is ready, unless using a specifically supported direct-access path.

The period for which an object remains available after restoration is not its job completion signal. Wait for completed restoration, inspect object restoration status and then read normally.

Question 666

An annual legal audit requires retrieving 80,000 objects stored in S3 Glacier Deep Archive, but operators cannot efficiently initiate a separate restore call for each key. The audit allows asynchronous restoration and wants a controlled cost tier plus a completion manifest. Which AWS operation should the team choose?

Use CloudFront invalidations on all 80,000 keys and assume invalidation invokes S3 archive restoration for each object.
Choose S3 Batch Operations Restore with the EXPEDITED tier and treat completion of each job request as proof that the archived bytes are already readable.
Enable S3 Transfer Acceleration and assume it issues RestoreObject for every archived key without a restoration manifest or role.
Create an S3 Batch Operations Restore job with an appropriate manifest, eligible STANDARD or BULK tier, supported restore duration and monitoring of object-restore completion separately from job request initiation.

Explanation

Correct Answer

S3 Batch Operations uses a manifest to initiate many RestoreObject requests under IAM controls. It supports STANDARD/BULK tiers for eligible archived classes; the Batch job records initiation, so separate restore-complete events or HeadObject checks establish readiness.

Incorrect Answers

CloudFront cache invalidation cannot initiate restoration of a Glacier Deep Archive object stored in S3; archival restore is an S3 operation.

AWS S3 Batch Operations Restore supports STANDARD and BULK retrieval, not EXPEDITED, and successful job initiation does not mean objects have completed asynchronous retrieval.

S3 Transfer Acceleration affects upload/data paths but cannot issue the thousands of per-object archive restore requests required by this audit.

Question 667

A team chooses One Zone-IA as the only copy of legally mandatory evidence and loses availability after an AZ failure. What design mistake?

S3 One Zone-IA replicates objects across at least three Availability Zones automatically and therefore survives an entire AZ loss.
The selected class stores data in one AZ and does not provide the multi-AZ resilience the evidence requirement needs.
Rely on bucket replication to a second Region without ever enabling replication rules or verifying a destination copy, and assume the sole One Zone-IA object survives AZ failure.
Keep the sole legal-evidence copy in One Zone-IA and rely only on bucket versioning to survive loss of its Availability Zone.

Explanation

Correct Answer

Do not base irreplaceable compliance retention on single-AZ object durability assumptions.

Incorrect Answers

One Zone-IA is intentionally AZ-scoped; selecting it for essential evidence violates a stated multi-AZ durability requirement.

A design may achieve separate durability by deliberately maintaining and testing an independent second copy, but an unconfigured plan does not protect data. The sole One Zone-IA object remains AZ-dependent.

Versioning protects object history within the chosen class but cannot substitute for cross-AZ resilience when the underlying class uses one AZ.

Question 668

Objects are removed from Standard-IA after 10 days but the bill includes additional storage-duration charges. Why?

An S3 Standard-IA object deleted after 12 days incurs no remaining storage-related charges because the bucket immediately becomes empty.
Assume S3 Standard-IA has no minimum storage-duration charge because the object was successfully deleted after ten days.
Assume minimum storage-duration billing applies only to Deep Archive and never to S3 Standard-IA.
Standard-IA has a 30-day minimum storage-duration billing period, so early deletions can incur prorated minimum charges.

Explanation

Correct Answer

Lifecycle expiry does not cancel minimum-duration billing already incurred for the storage class.

Incorrect Answers

Early deletion does not waive the storage class’s minimum billed duration even though the object is no longer accessible.

Standard-IA has a 30-day minimum storage-duration period; deleting earlier can still incur prorated charges for the remaining duration.

Different S3 classes have minimum-duration terms, including Standard-IA. The expected saving must include early-deletion effects.

Question 669

An S3 prefix contains no completed new objects, yet its bucket metrics show growing multipart-upload storage. Why?

An initiated multipart upload that was never completed is already a normal completed object included in all ListObjectsV2 results.
Enable a Lifecycle Expiration action on completed objects and expect it to remove incompletely uploaded multipart parts that have no completed object key.
Clients left uncompleted upload parts; they do not become visible completed objects until CompleteMultipartUpload.
Increase S3 object lifecycle expiration on completed objects and assume incomplete multipart uploads are always removed by that same rule.

Explanation

Correct Answer

Inspect ListMultipartUploads and lifecycle abort handling instead of assuming storage metrics only count completed keys.

Incorrect Answers

Uncompleted parts are separate billable multipart-upload state and are not exposed as a completed object until the complete operation.

Completed-object expiration applies to stored objects. Incomplete multipart parts need AbortIncompleteMultipartUpload or an explicit abort; the ordinary expiration rule does not clean them up.

An incomplete multipart upload needs appropriate abort-incomplete-multipart cleanup rather than relying only on expiration of completed objects.

Question 670

A finance manager assumes S3 Storage Lens can immediately delete all costly objects after it identifies a stale prefix. Why is this incorrect?

S3 Storage Lens automatically changes every bucket Object Lock retention to recover storage whenever a growth anomaly appears.
Storage Lens provides observability and recommendations, not automatic deletion of arbitrary objects by itself.
Treat S3 Storage Lens recommendation dashboards as an automatic, authorized DeleteObjects executor for every reported cold prefix.
Enable Storage Lens metrics and assume retention policies and legal holds are automatically checked before it purges costly objects.

Explanation

Correct Answer

Apply verified lifecycle/Batch Operations or owner-approved removal actions separately after analysis.

Incorrect Answers

Storage Lens reports usage trends and metrics, not a privileged retention-override and deletion mechanism.

Storage Lens reports usage and optimization insights but does not independently delete arbitrary customer data; lifecycle or explicitly authorized operations are separate.

Storage Lens is observational. Data deletion requires explicit policy, retention validation and appropriate lifecycle or object operations.

Pass Your Amazon AWS Certified Solutions Architect - Associate SAA-C03 Exam Easy!

Question 660

Explanation

Correct Answer

Incorrect Answers

Question 661

Explanation

Correct Answer

Incorrect Answers

Question 662

Explanation

Correct Answer

Incorrect Answers

Question 663

Explanation

Correct Answer

Incorrect Answers

Question 664

Explanation

Correct Answer

Incorrect Answers

Question 665

Explanation

Correct Answer

Incorrect Answers

Question 666

Explanation

Correct Answer

Incorrect Answers

Question 667

Explanation

Correct Answer

Incorrect Answers

Question 668

Explanation

Correct Answer

Incorrect Answers

Question 669

Explanation

Correct Answer

Incorrect Answers

Question 670

Explanation

Correct Answer

Incorrect Answers

AWS Certified Solutions Architect - Associate SAA-C03 Practice Tests