Amazon AWS Certified Solutions Architect - Associate SAA-C03 Practice Test 40
Question 390
A large DynamoDB table must survive a destructive application bug that propagates deletions globally. Which additional recovery protection is needed?
- Enable DynamoDB point-in-time recovery on the table.
- Global replication can have lag, so cross-Region reads require an explicit consistency and conflict strategy.
- Keep independently restorable backups or PITR in addition to global replication.
- Use a global table replica in another Region and route application traffic to that Region.
Explanation
Correct Answer
C:Global replication copies valid deletes too; it is not a substitute for point-in-time recovery. Simulate an accidental delete in staging and restore from a prior point.
Incorrect Answers
A:PITR permits restoring a new table to a supported timestamp without manually replaying each request. Keep independently restorable backups or PITR in addition to global replication. Simulate an accidental delete in staging and restore from a prior point.
B:Cross-Region table replication is asynchronous in supported global table modes and not a universal strongly consistent read guarantee. Keep independently restorable backups or PITR in addition to global replication. Simulate an accidental delete in staging and restore from a prior point.
D:Multi-Region tables keep additional regional copies available for service recovery. Keep independently restorable backups or PITR in addition to global replication. Simulate an accidental delete in staging and restore from a prior point.
Question 391
A DynamoDB application can survive regional failure but depends on a single-Region KMS key for sensitive auxiliary data. What is missing?
- Design key availability and encrypted-data access in the recovery Region as part of failover.
- Design for the global table's conflict-resolution semantics and avoid competing writes when possible.
- Use a global table replica in another Region and route application traffic to that Region.
- Keep independently restorable backups or PITR in addition to global replication.
Explanation
Correct Answer
A:Regional data replication does not automatically solve every application's cryptographic and dependent-service boundary. Disable the primary Region and test access to all encrypted dependencies in the secondary.
Incorrect Answers
B:Cross-Region replication is not a globally serialized multi-item transaction; conflicts can produce unexpected last-writer outcomes. Design key availability and encrypted-data access in the recovery Region as part of failover. Disable the primary Region and test access to all encrypted dependencies in the secondary.
C:Multi-Region tables keep additional regional copies available for service recovery. Design key availability and encrypted-data access in the recovery Region as part of failover. Disable the primary Region and test access to all encrypted dependencies in the secondary.
D:Global replication copies valid deletes too; it is not a substitute for point-in-time recovery. Design key availability and encrypted-data access in the recovery Region as part of failover. Disable the primary Region and test access to all encrypted dependencies in the secondary.
Question 392
A global table's application writes conflict when users travel between Regions. What workload change reduces the collision probability?
- Configure DynamoDB global tables across the target Regions.
- Use a global table replica in another Region and route application traffic to that Region.
- Route a given item's mutable writes to a preferred Region or use conflict-safe merge logic.
- Design for the global table's conflict-resolution semantics and avoid competing writes when possible.
Explanation
Correct Answer
C:Keeping one logical item's updates coordinated avoids unsupported assumptions about global write ordering. Simultaneously update a test item from two Regions and inspect conflict behavior after the change.
Incorrect Answers
A:Global tables replicate item changes among regional replicas and support multi-Region active-active applications under supported consistency behavior. Route a given item's mutable writes to a preferred Region or use conflict-safe merge logic. Simultaneously update a test item from two Regions and inspect conflict behavior after the change.
B:Multi-Region tables keep additional regional copies available for service recovery. Route a given item's mutable writes to a preferred Region or use conflict-safe merge logic. Simultaneously update a test item from two Regions and inspect conflict behavior after the change.
D:Cross-Region replication is not a globally serialized multi-item transaction; conflicts can produce unexpected last-writer outcomes. Route a given item's mutable writes to a preferred Region or use conflict-safe merge logic. Simultaneously update a test item from two Regions and inspect conflict behavior after the change.
Question 393
A critical object is accidentally overwritten and users need to retrieve the earlier contents. Which S3 control should be enabled beforehand?
- Use S3 Object Lock with a supported retention mode and versioning.
- Review S3 replication delete-marker behavior and destination retention separately.
- Enable S3 Versioning and retain prior object versions according to policy.
- Add lifecycle rules for noncurrent versions consistent with compliance retention.
Explanation
Correct Answer
C:Versioning preserves overwritten versions so a prior object version can be recovered. Overwrite a test key and retrieve its earlier version ID.
Incorrect Answers
A:Object Lock retains protected object versions against deletion or alteration according to configured retention. Enable S3 Versioning and retain prior object versions according to policy. Overwrite a test key and retrieve its earlier version ID.
B:Replication settings can propagate certain delete markers; independent retention and Object Lock control recovery policy. Enable S3 Versioning and retain prior object versions according to policy. Overwrite a test key and retrieve its earlier version ID.
D:Lifecycle expiration can manage historic versions, but policy must preserve obligated recoverability. Enable S3 Versioning and retain prior object versions according to policy. Overwrite a test key and retrieve its earlier version ID.
Question 394
A data lake must keep a copy of selected objects in a second Region for a disaster-recovery objective. Which mechanism suits ongoing replication?
- Enable S3 Versioning and retain prior object versions according to policy.
- Use S3 Batch Replication for eligible existing object versions.
- Grant the replication role the required source and destination KMS key and bucket permissions.
- Configure S3 Cross-Region Replication with versioning and necessary IAM/KMS permissions.
Explanation
Correct Answer
D:CRR asynchronously replicates eligible versions to a destination bucket in another Region. Upload a scoped object and verify it arrives in the destination.
Incorrect Answers
A:Versioning preserves overwritten versions so a prior object version can be recovered. Configure S3 Cross-Region Replication with versioning and necessary IAM/KMS permissions. Upload a scoped object and verify it arrives in the destination.
B:Ordinary live replication does not automatically replay all pre-existing bucket objects. Configure S3 Cross-Region Replication with versioning and necessary IAM/KMS permissions. Upload a scoped object and verify it arrives in the destination.
C:Cross-account encrypted replication needs compatible IAM, bucket policy, and KMS key authorizations. Configure S3 Cross-Region Replication with versioning and necessary IAM/KMS permissions. Upload a scoped object and verify it arrives in the destination.
Question 395
An auditor assumes replication prevents deletion of a source object from affecting the destination. What should be considered?
- Use S3 Object Lock with a supported retention mode and versioning.
- Apply least-privilege access and immutable retention such as S3 Object Lock where required.
- Review S3 replication delete-marker behavior and destination retention separately.
- Enable S3 Versioning and retain prior object versions according to policy.
Explanation
Correct Answer
C:Replication settings can propagate certain delete markers; independent retention and Object Lock control recovery policy. Delete an object and inspect destination version and delete marker results.
Incorrect Answers
A:Object Lock retains protected object versions against deletion or alteration according to configured retention. Review S3 replication delete-marker behavior and destination retention separately. Delete an object and inspect destination version and delete marker results.
B:Versioning aids recovery but authorized principals may delete or expire versions absent stronger controls. Review S3 replication delete-marker behavior and destination retention separately. Delete an object and inspect destination version and delete marker results.
D:Versioning preserves overwritten versions so a prior object version can be recovered. Review S3 replication delete-marker behavior and destination retention separately. Delete an object and inspect destination version and delete marker results.
Question 396
A bucket's old objects must become write-once retained for a regulatory period. Which control is appropriate?
- Review S3 replication delete-marker behavior and destination retention separately.
- Apply least-privilege access and immutable retention such as S3 Object Lock where required.
- Configure S3 Cross-Region Replication with versioning and necessary IAM/KMS permissions.
- Use S3 Object Lock with a supported retention mode and versioning.
Explanation
Correct Answer
D:Object Lock retains protected object versions against deletion or alteration according to configured retention. Attempt deletion of a retained test version under an ordinary role.
Incorrect Answers
A:Replication settings can propagate certain delete markers; independent retention and Object Lock control recovery policy. Use S3 Object Lock with a supported retention mode and versioning. Attempt deletion of a retained test version under an ordinary role.
B:Versioning aids recovery but authorized principals may delete or expire versions absent stronger controls. Use S3 Object Lock with a supported retention mode and versioning. Attempt deletion of a retained test version under an ordinary role.
C:CRR asynchronously replicates eligible versions to a destination bucket in another Region. Object Lock retains protected object versions against deletion or alteration according to configured retention.
Question 397
An S3 bucket has versioning but no recovery policy, and storage grows due to old versions. Which operation should manage lifecycle without sacrificing required retention?
- Enable S3 Versioning and retain prior object versions according to policy.
- Review S3 replication delete-marker behavior and destination retention separately.
- Add lifecycle rules for noncurrent versions consistent with compliance retention.
- Configure S3 Cross-Region Replication with versioning and necessary IAM/KMS permissions.
Explanation
Correct Answer
C:Lifecycle expiration can manage historic versions, but policy must preserve obligated recoverability. Inspect retained versions and verify noncurrent expiration occurs after the required window.
Incorrect Answers
A:Versioning preserves overwritten versions so a prior object version can be recovered. Add lifecycle rules for noncurrent versions consistent with compliance retention. Inspect retained versions and verify noncurrent expiration occurs after the required window.
B:Replication settings can propagate certain delete markers; independent retention and Object Lock control recovery policy. Add lifecycle rules for noncurrent versions consistent with compliance retention. Inspect retained versions and verify noncurrent expiration occurs after the required window.
D:CRR asynchronously replicates eligible versions to a destination bucket in another Region. Lifecycle expiration can manage historic versions, but policy must preserve obligated recoverability.
Question 398
A pipeline needs S3 object replication to a bucket in a different account with SSE-KMS. What else must the deployment configure?
- Review S3 replication delete-marker behavior and destination retention separately.
- Grant the replication role the required source and destination KMS key and bucket permissions.
- Configure S3 Cross-Region Replication with versioning and necessary IAM/KMS permissions.
- Use S3 Batch Replication for eligible existing object versions.
Explanation
Correct Answer
B:Cross-account encrypted replication needs compatible IAM, bucket policy, and KMS key authorizations. Replicate an encrypted test object and inspect failed replication metrics.
Incorrect Answers
A:Replication settings can propagate certain delete markers; independent retention and Object Lock control recovery policy. Grant the replication role the required source and destination KMS key and bucket permissions. Replicate an encrypted test object and inspect failed replication metrics.
C:CRR asynchronously replicates eligible versions to a destination bucket in another Region. Grant the replication role the required source and destination KMS key and bucket permissions. Replicate an encrypted test object and inspect failed replication metrics.
D:Ordinary live replication does not automatically replay all pre-existing bucket objects. Grant the replication role the required source and destination KMS key and bucket permissions. Replicate an encrypted test object and inspect failed replication metrics.
Question 399
A team needs to backfill older objects after first enabling replication for newly created objects. Which feature should be evaluated?
- Use S3 Batch Replication for eligible existing object versions.
- Configure S3 Cross-Region Replication with versioning and necessary IAM/KMS permissions.
- Enable S3 Versioning and retain prior object versions according to policy.
- Use S3 Object Lock with a supported retention mode and versioning.
Explanation
Correct Answer
A:Ordinary live replication does not automatically replay all pre-existing bucket objects. Run a bounded backfill job and verify destination versions.
Incorrect Answers
B:CRR asynchronously replicates eligible versions to a destination bucket in another Region. Use S3 Batch Replication for eligible existing object versions. Run a bounded backfill job and verify destination versions.
C:Versioning preserves overwritten versions so a prior object version can be recovered. Use S3 Batch Replication for eligible existing object versions. Run a bounded backfill job and verify destination versions.
D:Object Lock retains protected object versions against deletion or alteration according to configured retention. Use S3 Batch Replication for eligible existing object versions. Run a bounded backfill job and verify destination versions.
Question 400
A developer believes S3 versioning alone stops malware from modifying every version. What gap remains?
- Leave Object Lock disabled and rely only on S3 Versioning to prevent privileged deletion of every retained version.
- Enable S3 Versioning and retain prior object versions according to policy.
- Apply least-privilege access and immutable retention such as S3 Object Lock where required.
- Review S3 replication delete-marker behavior and destination retention separately.
Explanation
Correct Answer
C:Versioning aids recovery but authorized principals may delete or expire versions absent stronger controls. Try deleting a prior version under ordinary credentials and observe the policy result.
Incorrect Answers
A:Versioning retains older revisions after ordinary overwrites but does not itself establish immutability. An approved Object Lock retention mode or legal hold must protect required versions from prohibited deletion.
B:Versioning preserves overwritten versions so a prior object version can be recovered. Apply least-privilege access and immutable retention such as S3 Object Lock where required. Try deleting a prior version under ordinary credentials and observe the policy result.
D:Replication settings can propagate certain delete markers; independent retention and Object Lock control recovery policy. Apply least-privilege access and immutable retention such as S3 Object Lock where required. Try deleting a prior version under ordinary credentials and observe the policy result.