Amazon AWS Certified Solutions Architect - Associate SAA-C03 Practice Test 45
Question 440
A regional EFS workload's operators want backups in addition to its built-in AZ durability. What separate control is suitable?
- Configure AWS Backup protection for EFS with tested restore procedures.
- Mount Amazon EFS from the tasks with appropriate access-point and network permissions.
- Prefer appropriate local instance-store scratch storage rather than a shared EFS namespace.
- Use a regional EFS file system for multi-AZ file-storage resilience.
Explanation
Correct Answer
A:Multi-AZ storage availability is not equivalent to recovery from logical deletion or ransomware. Delete a staged file and restore it from an approved recovery point.
Incorrect Answers
B:EFS decouples persistent shared files from disposable task storage. Configure AWS Backup protection for EFS with tested restore procedures. Delete a staged file and restore it from an approved recovery point.
C:Local ephemeral scratch can remove network file-system dependence when data is disposable. Configure AWS Backup protection for EFS with tested restore procedures. Delete a staged file and restore it from an approved recovery point.
D:EFS One Zone stores data in one AZ, unlike regional EFS multi-AZ storage. Configure AWS Backup protection for EFS with tested restore procedures. Delete a staged file and restore it from an approved recovery point.
Question 441
A two-Region app has replicated data but the disaster recovery Region lacks the production IAM roles. What should the DR design include?
- Ensure recovery-Region key access and an approved replication or re-encryption design for the protected data.
- Provision necessary IAM and workload role definitions and credentials in the recovery Region or account.
- Define consistent write ownership or conflict-resolution semantics for replicated state.
- Provide a resilient authentication and identity dependency available during regional failover.
Explanation
Correct Answer
B:Data replication alone does not recreate the application's authorization and deployment dependencies. Promote the recovery stack and verify access to all required AWS services.
Incorrect Answers
A:Cross-Region storage copies do not necessarily make source-Region cryptographic keys usable elsewhere. Provision necessary IAM and workload role definitions and credentials in the recovery Region or account. Promote the recovery stack and verify access to all required AWS services.
C:Multi-Region serving capacity does not guarantee globally serialized data updates. Provision necessary IAM and workload role definitions and credentials in the recovery Region or account. Promote the recovery stack and verify access to all required AWS services.
D:A recovered application cannot authenticate users if identity services remain bound to the failed Region. Provision necessary IAM and workload role definitions and credentials in the recovery Region or account. Promote the recovery stack and verify access to all required AWS services.
Question 442
A service uses an active-passive regional design, but client DNS points permanently to the failed primary. Which component must become health-aware?
- Pre-stage or rapidly scale standby capacity according to tested failover load targets.
- Use Route 53 failover routing or a suitable global traffic failover mechanism.
- Provide a resilient authentication and identity dependency available during regional failover.
- Make upload destinations region-aware and replicate or route writes according to the DR state model.
Explanation
Correct Answer
B:Regional recovery requires directing new client requests to the functioning endpoint. Disable the primary and inspect client routing to the secondary.
Incorrect Answers
A:Data readiness and sufficient serving capacity are separate dimensions of regional resilience. Use Route 53 failover routing or a suitable global traffic failover mechanism. Disable the primary and inspect client routing to the secondary.
C:A recovered application cannot authenticate users if identity services remain bound to the failed Region. Use Route 53 failover routing or a suitable global traffic failover mechanism. Disable the primary and inspect client routing to the secondary.
D:Static assets and dynamic upload locations have different state and routing dependencies. Use Route 53 failover routing or a suitable global traffic failover mechanism. Disable the primary and inspect client routing to the secondary.
Question 443
An active-active global application has conflicting writes when the same account is changed in both Regions. What architecture requirement is missing?
- Define consistent write ownership or conflict-resolution semantics for replicated state.
- Pre-stage or rapidly scale standby capacity according to tested failover load targets.
- Ensure recovery-Region key access and an approved replication or re-encryption design for the protected data.
- Provision necessary IAM and workload role definitions and credentials in the recovery Region or account.
Explanation
Correct Answer
A:Multi-Region serving capacity does not guarantee globally serialized data updates. Write from two Regions simultaneously and verify the selected conflict rule.
Incorrect Answers
B:Data readiness and sufficient serving capacity are separate dimensions of regional resilience. Define consistent write ownership or conflict-resolution semantics for replicated state. Write from two Regions simultaneously and verify the selected conflict rule.
C:Cross-Region storage copies do not necessarily make source-Region cryptographic keys usable elsewhere. Define consistent write ownership or conflict-resolution semantics for replicated state. Write from two Regions simultaneously and verify the selected conflict rule.
D:Data replication alone does not recreate the application's authorization and deployment dependencies. Define consistent write ownership or conflict-resolution semantics for replicated state. Write from two Regions simultaneously and verify the selected conflict rule.
Question 444
The DR Region contains database replicas but cannot reach an identity provider hosted only in the primary Region. What should be redesigned?
- Provide a resilient authentication and identity dependency available during regional failover.
- Provision necessary IAM and workload role definitions and credentials in the recovery Region or account.
- Make upload destinations region-aware and replicate or route writes according to the DR state model.
- Use Route 53 failover routing or a suitable global traffic failover mechanism.
Explanation
Correct Answer
A:A recovered application cannot authenticate users if identity services remain bound to the failed Region. Disable the primary Region's IdP path and test sign-in to the recovery app.
Incorrect Answers
B:Data replication alone does not recreate the application's authorization and deployment dependencies. Provide a resilient authentication and identity dependency available during regional failover. Disable the primary Region's IdP path and test sign-in to the recovery app.
C:Static assets and dynamic upload locations have different state and routing dependencies. Provide a resilient authentication and identity dependency available during regional failover. Disable the primary Region's IdP path and test sign-in to the recovery app.
D:Regional recovery requires directing new client requests to the functioning endpoint. Provide a resilient authentication and identity dependency available during regional failover. Disable the primary Region's IdP path and test sign-in to the recovery app.
Question 445
A service's public assets survive regional failover but its S3 upload bucket is hardcoded to the primary Region. Which dependency should be changed?
- Provision necessary IAM and workload role definitions and credentials in the recovery Region or account.
- Ensure recovery-Region key access and an approved replication or re-encryption design for the protected data.
- Use Route 53 failover routing or a suitable global traffic failover mechanism.
- Make upload destinations region-aware and replicate or route writes according to the DR state model.
Explanation
Correct Answer
D:Static assets and dynamic upload locations have different state and routing dependencies. Fail over the application and confirm new uploads persist in the designated Region.
Incorrect Answers
A:Data replication alone does not recreate the application's authorization and deployment dependencies. Make upload destinations region-aware and replicate or route writes according to the DR state model. Fail over the application and confirm new uploads persist in the designated Region.
B:Cross-Region storage copies do not necessarily make source-Region cryptographic keys usable elsewhere. Make upload destinations region-aware and replicate or route writes according to the DR state model. Fail over the application and confirm new uploads persist in the designated Region.
C:Regional recovery requires directing new client requests to the functioning endpoint. Make upload destinations region-aware and replicate or route writes according to the DR state model. Fail over the application and confirm new uploads persist in the designated Region.
Question 446
A regional outage removes the primary KMS key but the standby service uses ciphertext copied from the primary. What must be verified?
- Define consistent write ownership or conflict-resolution semantics for replicated state.
- Ensure recovery-Region key access and an approved replication or re-encryption design for the protected data.
- Make upload destinations region-aware and replicate or route writes according to the DR state model.
- Provision necessary IAM and workload role definitions and credentials in the recovery Region or account.
Explanation
Correct Answer
B:Cross-Region storage copies do not necessarily make source-Region cryptographic keys usable elsewhere. Restore and decrypt a test artifact exclusively from recovery-Region resources.
Incorrect Answers
A:Multi-Region serving capacity does not guarantee globally serialized data updates. Ensure recovery-Region key access and an approved replication or re-encryption design for the protected data. Restore and decrypt a test artifact exclusively from recovery-Region resources.
C:Static assets and dynamic upload locations have different state and routing dependencies. Ensure recovery-Region key access and an approved replication or re-encryption design for the protected data. Restore and decrypt a test artifact exclusively from recovery-Region resources.
D:Data replication alone does not recreate the application's authorization and deployment dependencies. Ensure recovery-Region key access and an approved replication or re-encryption design for the protected data. Restore and decrypt a test artifact exclusively from recovery-Region resources.
Question 447
A business requires quarterly proof of cross-Region recovery under a five-minute objective. How should compliance evidence be collected?
- Execute scheduled full-stack failover drills and record measured RTO, RPO, and dependencies.
- Provision necessary IAM and workload role definitions and credentials in the recovery Region or account.
- Ensure recovery-Region key access and an approved replication or re-encryption design for the protected data.
- Use Route 53 failover routing or a suitable global traffic failover mechanism.
Explanation
Correct Answer
A:Documented design diagrams do not prove actual recovery behavior without tests. Run a production-like game day and compare time-stamped health metrics to objectives.
Incorrect Answers
B:Data replication alone does not recreate the application's authorization and deployment dependencies. Execute scheduled full-stack failover drills and record measured RTO, RPO, and dependencies. Run a production-like game day and compare time-stamped health metrics to objectives.
C:Cross-Region storage copies do not necessarily make source-Region cryptographic keys usable elsewhere. Execute scheduled full-stack failover drills and record measured RTO, RPO, and dependencies. Run a production-like game day and compare time-stamped health metrics to objectives.
D:Regional recovery requires directing new client requests to the functioning endpoint. Execute scheduled full-stack failover drills and record measured RTO, RPO, and dependencies. Run a production-like game day and compare time-stamped health metrics to objectives.
Question 448
An active-passive service has healthy data in standby but too little compute to absorb peak traffic after failover. What should be provisioned?
- Define consistent write ownership or conflict-resolution semantics for replicated state.
- Pre-stage or rapidly scale standby capacity according to tested failover load targets.
- Provide a resilient authentication and identity dependency available during regional failover.
- Use Route 53 failover routing or a suitable global traffic failover mechanism.
Explanation
Correct Answer
B:Data readiness and sufficient serving capacity are separate dimensions of regional resilience. Shift peak-equivalent test traffic and verify error rate and response time.
Incorrect Answers
A:Multi-Region serving capacity does not guarantee globally serialized data updates. Pre-stage or rapidly scale standby capacity according to tested failover load targets. Shift peak-equivalent test traffic and verify error rate and response time.
C:A recovered application cannot authenticate users if identity services remain bound to the failed Region. Pre-stage or rapidly scale standby capacity according to tested failover load targets. Shift peak-equivalent test traffic and verify error rate and response time.
D:Regional recovery requires directing new client requests to the functioning endpoint. Pre-stage or rapidly scale standby capacity according to tested failover load targets. Shift peak-equivalent test traffic and verify error rate and response time.
Question 449
An EC2 database needs separately tunable SSD IOPS and throughput, but provisioning additional volume GiB would waste money. The application still cannot reach configured performance because its EC2 host saturates EBS bandwidth. Which TWO controls address the distinct constraints? (Select TWO.)
- Check the EC2 instance’s EBS-optimized throughput and queue-depth limits before raising volume throughput further.
- Switch the database onto EBS sc1 cold HDD as a low-latency transaction device.
- Use an EBS gp3 volume and independently provision justified IOPS and throughput settings.
- Increase gp2 capacity indefinitely while ignoring the EC2 EBS bandwidth ceiling.
- Move the database’s live block device into an S3 Glacier Deep Archive object.
Explanation
Correct Answers
A:The instance has its own EBS bandwidth ceiling; tuning a volume above that bottleneck will not improve observed I/O throughput.
C:Gp3 separates provisioned capacity from IOPS and throughput within service limits, avoiding gp2 size-for-performance coupling.
Incorrect Answers
B:Cold HDD storage is inappropriate for the stated high-IOPS, low-latency database I/O need.
D:Additional size would not fix a saturated instance-level limit and would undermine the specified cost goal.
E:An archival object class is not a directly attached transactional block volume for the running database.
Question 450
A latency-sensitive transactional database requires sustained very high IOPS and suitable durability. What EBS family is appropriate?
- Use a gp3 EBS volume and provision the required IOPS and throughput.
- Choose an eligible SSD-backed EBS boot volume instead of st1 or sc1.
- Evaluate Provisioned IOPS SSD io2 volumes with supported instance limits.
- Use EBS Elastic Volumes ModifyVolume with filesystem follow-up as needed.
Explanation
Correct Answer
C:Io2 is designed for demanding transactional I/O and high durability. Measure latency and sustained IOPS during peak workload.
Incorrect Answers
A:Gp3 separates baseline volume size from provisioned performance settings within limits. Evaluate Provisioned IOPS SSD io2 volumes with supported instance limits. Measure latency and sustained IOPS during peak workload.
B:Throughput-optimized and cold HDD volumes are not supported as boot volumes. Evaluate Provisioned IOPS SSD io2 volumes with supported instance limits. Measure latency and sustained IOPS during peak workload.
D:Elastic Volumes supports supported type, size and performance modification in place. Evaluate Provisioned IOPS SSD io2 volumes with supported instance limits. Measure latency and sustained IOPS during peak workload.