Amazon AWS Certified Solutions Architect - Associate SAA-C03 Practice Test 42
Question 410
An attacker gains write access to a backup vault and tries to shorten retention. Which safeguard reduces that risk?
- Copy eligible recovery points into a separately controlled backup account and vault.
- Use AWS Backup plans and resource assignments for supported services.
- Configure AWS Backup Vault Lock in an appropriate supported governance or compliance mode.
- Adjust AWS Backup plan lifecycle and vault retention to the required policy period.
Explanation
Correct Answer
C:Vault Lock enforces retention controls that can restrict unauthorized modification and deletion. Try an early delete against a retained recovery point with a limited test identity.
Incorrect Answers
A:Cross-account copies separate backup administration from compromised production principals. Configure AWS Backup Vault Lock in an appropriate supported governance or compliance mode. Try an early delete against a retained recovery point with a limited test identity.
B:AWS Backup centralizes scheduling, retention, and recovery-point management for supported resources. Configure AWS Backup Vault Lock in an appropriate supported governance or compliance mode. Try an early delete against a retained recovery point with a limited test identity.
D:Recovery-point retention is governed by lifecycle and vault controls rather than an application's data TTL. Configure AWS Backup Vault Lock in an appropriate supported governance or compliance mode. Try an early delete against a retained recovery point with a limited test identity.
Question 411
A recovery plan must survive compromise of a production account. Which backup architecture provides independent boundaries?
- Run AWS Backup restore testing plans or equivalent controlled restore exercises.
- Use separate backup plans or policy selections with reliable resource tags.
- Adjust AWS Backup plan lifecycle and vault retention to the required policy period.
- Copy eligible recovery points into a separately controlled backup account and vault.
Explanation
Correct Answer
D:Cross-account copies separate backup administration from compromised production principals. Assume a production role and verify it cannot delete protected backup copies.
Incorrect Answers
A:Successful backup completion does not prove recovery without actual restoration tests. Copy eligible recovery points into a separately controlled backup account and vault. Assume a production role and verify it cannot delete protected backup copies.
B:Scoped assignments apply different recovery-point schedules and lifecycles to distinct resource classes. Copy eligible recovery points into a separately controlled backup account and vault. Assume a production role and verify it cannot delete protected backup copies.
C:Recovery-point retention is governed by lifecycle and vault controls rather than an application's data TTL. Copy eligible recovery points into a separately controlled backup account and vault. Assume a production role and verify it cannot delete protected backup copies.
Question 412
An RDS snapshot exists but a restoration test shows dependent application secrets are missing. What should the backup plan encompass?
- Ensure destination-region KMS keys and restore-role permissions support the copied backup.
- Protect and test external dependencies such as secrets, infrastructure configuration, and network access.
- Run AWS Backup restore testing plans or equivalent controlled restore exercises.
- Adjust AWS Backup plan lifecycle and vault retention to the required policy period.
Explanation
Correct Answer
B:Database backups alone do not reconstruct the credentials and endpoints required by the application. Restore the app in an isolated environment and verify end-to-end login.
Incorrect Answers
A:Encrypted recovery depends on usable keys and IAM grants in the restore account and Region. Protect and test external dependencies such as secrets, infrastructure configuration, and network access. Restore the app in an isolated environment and verify end-to-end login.
C:Successful backup completion does not prove recovery without actual restoration tests. Protect and test external dependencies such as secrets, infrastructure configuration, and network access. Restore the app in an isolated environment and verify end-to-end login.
D:Recovery-point retention is governed by lifecycle and vault controls rather than an application's data TTL. Protect and test external dependencies such as secrets, infrastructure configuration, and network access. Restore the app in an isolated environment and verify end-to-end login.
Question 413
An organization needs to demonstrate that backups actually permit recovery rather than only that jobs completed. Which feature or practice fits?
- Copy eligible recovery points into a separately controlled backup account and vault.
- Run AWS Backup restore testing plans or equivalent controlled restore exercises.
- Use separate backup plans or policy selections with reliable resource tags.
- Use AWS Backup plans and resource assignments for supported services.
Explanation
Correct Answer
B:Successful backup completion does not prove recovery without actual restoration tests. Inspect a restored resource and its validation results.
Incorrect Answers
A:Cross-account copies separate backup administration from compromised production principals. Run AWS Backup restore testing plans or equivalent controlled restore exercises. Inspect a restored resource and its validation results.
C:Scoped assignments apply different recovery-point schedules and lifecycles to distinct resource classes. Run AWS Backup restore testing plans or equivalent controlled restore exercises. Inspect a restored resource and its validation results.
D:AWS Backup centralizes scheduling, retention, and recovery-point management for supported resources. Run AWS Backup restore testing plans or equivalent controlled restore exercises. Inspect a restored resource and its validation results.
Question 414
A resource's backups expire earlier than regulatory policy allows because the plan's lifecycle is too short. What should be changed?
- Configure AWS Backup Vault Lock in an appropriate supported governance or compliance mode.
- Adjust AWS Backup plan lifecycle and vault retention to the required policy period.
- Use separate backup plans or policy selections with reliable resource tags.
- Copy eligible recovery points into a separately controlled backup account and vault.
Explanation
Correct Answer
B:Recovery-point retention is governed by lifecycle and vault controls rather than an application's data TTL. Create a recovery point and inspect its calculated deletion date.
Incorrect Answers
A:Vault Lock enforces retention controls that can restrict unauthorized modification and deletion. Adjust AWS Backup plan lifecycle and vault retention to the required policy period. Create a recovery point and inspect its calculated deletion date.
C:Scoped assignments apply different recovery-point schedules and lifecycles to distinct resource classes. Adjust AWS Backup plan lifecycle and vault retention to the required policy period. Create a recovery point and inspect its calculated deletion date.
D:Cross-account copies separate backup administration from compromised production principals. Recovery-point retention is governed by lifecycle and vault controls rather than an application's data TTL.
Question 415
A financial workload needs different backup retention rules for production and sandbox resources. How should schedules be scoped?
- Copy eligible recovery points into a separately controlled backup account and vault.
- Use separate backup plans or policy selections with reliable resource tags.
- Adjust AWS Backup plan lifecycle and vault retention to the required policy period.
- Use AWS Backup plans and resource assignments for supported services.
Explanation
Correct Answer
B:Scoped assignments apply different recovery-point schedules and lifecycles to distinct resource classes. Tag a sandbox and production test resource and inspect assigned plans.
Incorrect Answers
A:Cross-account copies separate backup administration from compromised production principals. Use separate backup plans or policy selections with reliable resource tags. Tag a sandbox and production test resource and inspect assigned plans.
C:Recovery-point retention is governed by lifecycle and vault controls rather than an application's data TTL. Use separate backup plans or policy selections with reliable resource tags. Tag a sandbox and production test resource and inspect assigned plans.
D:AWS Backup centralizes scheduling, retention, and recovery-point management for supported resources. Use separate backup plans or policy selections with reliable resource tags. Tag a sandbox and production test resource and inspect assigned plans.
Question 416
A secondary Region contains backup recovery points but restoration fails on missing encryption key access. What must recovery design validate?
- Adjust AWS Backup plan lifecycle and vault retention to the required policy period.
- Copy eligible recovery points into a separately controlled backup account and vault.
- Run AWS Backup restore testing plans or equivalent controlled restore exercises.
- Ensure destination-region KMS keys and restore-role permissions support the copied backup.
Explanation
Correct Answer
D:Encrypted recovery depends on usable keys and IAM grants in the restore account and Region. Restore an encrypted test recovery point using the intended disaster-recovery role.
Incorrect Answers
A:Recovery-point retention is governed by lifecycle and vault controls rather than an application's data TTL. Ensure destination-region KMS keys and restore-role permissions support the copied backup. Restore an encrypted test recovery point using the intended disaster-recovery role.
B:Cross-account copies separate backup administration from compromised production principals. Ensure destination-region KMS keys and restore-role permissions support the copied backup. Restore an encrypted test recovery point using the intended disaster-recovery role.
C:Successful backup completion does not prove recovery without actual restoration tests. Ensure destination-region KMS keys and restore-role permissions support the copied backup. Restore an encrypted test recovery point using the intended disaster-recovery role.
Question 417
A static web application uses CloudFront with two private S3 origins. The business needs automatic failover when the primary returns configured failure responses and must keep direct bucket access restricted to the distribution. Which TWO settings help meet both goals? (Select TWO.)
- Configure a CloudFront origin group with primary/secondary origins and supported failover status-code behavior.
- Use CloudFront origin access control with narrowly scoped S3 bucket authorization for the distributions.
- Use a viewer request header rewrite alone and assume it replaces CloudFront origin failover.
- Treat S3 object versioning by itself as an automatic cross-origin failover mechanism.
- Make both origin buckets publicly writable so CloudFront can access them without any access policy.
Explanation
Correct Answers
A:Origin groups let eligible requests use a secondary origin when the primary fails according to configured conditions.
B:Origin access control and bucket policies let CloudFront fetch private S3 content without making the buckets publicly readable.
Incorrect Answers
C:Header manipulation does not establish a health-aware primary/secondary origin group.
D:Versioning retains revisions in one bucket and does not route CloudFront requests to a secondary origin when primary requests fail.
E:Public write permissions are unnecessary and violate the private-origin security requirement.
Question 418
A critical application requires CloudFront to retry failed POST transactions on another origin automatically. What constraint must be considered?
- Configure a CloudFront origin group with primary and secondary origins for supported requests.
- Replicate approved static assets to an additional S3 bucket and configure a supported CloudFront origin failover strategy.
- Include the appropriate supported HTTP failure status in the origin-group failover criteria.
- CloudFront origin-group failover is limited to eligible idempotent request methods, not arbitrary POST replay.
Explanation
Correct Answer
D:Automatic origin failover for mutations could duplicate side effects, so application-level resilience is necessary. Send a POST during origin failure and inspect actual origin handling.
Incorrect Answers
A:Origin failover can route eligible requests to a secondary origin on configured origin failure responses. CloudFront origin-group failover is limited to eligible idempotent request methods, not arbitrary POST replay. Send a POST during origin failure and inspect actual origin handling.
B:Redundant origins and consistent object copies reduce dependence on one regional endpoint. CloudFront origin-group failover is limited to eligible idempotent request methods, not arbitrary POST replay. Send a POST during origin failure and inspect actual origin handling.
C:CloudFront origin-group routing responds to configured eligible error codes, not every application response. CloudFront origin-group failover is limited to eligible idempotent request methods, not arbitrary POST replay. Send a POST during origin failure and inspect actual origin handling.
Question 419
An origin has intermittent 5xx failures but the edge keeps serving a valid cached stylesheet. What explains this observation?
- Set appropriate error-response caching behavior and use invalidation where justified.
- CloudFront can serve still-valid cached objects without contacting an unhealthy origin.
- Configure a CloudFront origin group with primary and secondary origins for supported requests.
- Authorize CloudFront origin access to the backup bucket using the appropriate supported access control.
Explanation
Correct Answer
B:Edge caching isolates repeat reads until cache freshness rules require origin access. Compare cache hit and cache miss requests during an origin outage.
Incorrect Answers
A:Error caching can preserve an outage symptom after the origin has recovered. CloudFront can serve still-valid cached objects without contacting an unhealthy origin. Compare cache hit and cache miss requests during an origin outage.
C:Origin failover can route eligible requests to a secondary origin on configured origin failure responses. CloudFront can serve still-valid cached objects without contacting an unhealthy origin. Compare cache hit and cache miss requests during an origin outage.
D:Each private S3 origin needs its own correct bucket access policy for distribution fetches. CloudFront can serve still-valid cached objects without contacting an unhealthy origin. Compare cache hit and cache miss requests during an origin outage.
Question 420
A distribution's primary origin returns an HTTP code not configured for failover, so CloudFront never uses the secondary. What setting is missing?
- Configure a CloudFront origin group with primary and secondary origins for supported requests.
- Authorize CloudFront origin access to the backup bucket using the appropriate supported access control.
- Include the appropriate supported HTTP failure status in the origin-group failover criteria.
- CloudFront origin-group failover is limited to eligible idempotent request methods, not arbitrary POST replay.
Explanation
Correct Answer
C:CloudFront origin-group routing responds to configured eligible error codes, not every application response. Return the target error and verify which origin handles the next eligible request.
Incorrect Answers
A:Origin failover can route eligible requests to a secondary origin on configured origin failure responses. Include the appropriate supported HTTP failure status in the origin-group failover criteria. Return the target error and verify which origin handles the next eligible request.
B:Each private S3 origin needs its own correct bucket access policy for distribution fetches. Include the appropriate supported HTTP failure status in the origin-group failover criteria. Return the target error and verify which origin handles the next eligible request.
D:Automatic origin failover for mutations could duplicate side effects, so application-level resilience is necessary. Include the appropriate supported HTTP failure status in the origin-group failover criteria. Return the target error and verify which origin handles the next eligible request.