Amazon AWS Certified Solutions Architect - Associate SAA-C03 Practice Test 37
Question 360
A worker instance has an attached EBS volume with irreplaceable local state. Why is simple Auto Scaling replacement unsafe?
- Move essential state to durable shared storage or a managed data store before relying on disposable nodes.
- Use Auto Scaling health checks and desired-capacity replacement of unhealthy instances.
- Use an Auto Scaling lifecycle hook for the termination transition.
- Configure the Auto Scaling group's subnet list across multiple Availability Zones.
Explanation
Correct Answer
A:Auto Scaling may terminate and replace instances, so nonreplicated attached state is not inherently portable. Terminate a test instance and confirm the needed data remains accessible.
Incorrect Answers
B:An Auto Scaling group replaces instances found unhealthy according to EC2 or enabled load-balancer checks. Move essential state to durable shared storage or a managed data store before relying on disposable nodes. Terminate a test instance and confirm the needed data remains accessible.
C:Lifecycle hooks pause transitions so cleanup logic can complete before the instance goes away. Move essential state to durable shared storage or a managed data store before relying on disposable nodes. Terminate a test instance and confirm the needed data remains accessible.
D:A group can place replacements in healthy zones when capacity is available. Move essential state to durable shared storage or a managed data store before relying on disposable nodes. Terminate a test instance and confirm the needed data remains accessible.
Question 361
A company runs an active API in one Region and a warm standby in another, with automatic DNS failover required. What routing policy is appropriate?
- Route 53 can return the secondary record even if its endpoint is not actually healthy.
- Use a suitable active-active Route 53 routing policy with evaluated endpoint health.
- Configure Route 53 primary and secondary failover records with applicable health checks.
- Create two weighted Route 53 records with no meaningful endpoint health checks and assume this guarantees failover.
Explanation
Correct Answer
C:Failover records return the healthy secondary when the primary is deemed unhealthy. Fail the primary health target and inspect authoritative DNS responses.
Incorrect Answers
A:Without secondary health validation, DNS failover presumes that secondary as an available fallback. Configure Route 53 primary and secondary failover records with applicable health checks. Fail the primary health target and inspect authoritative DNS responses.
B:Latency or weighted records can serve healthy endpoints while removing unhealthy answers. Configure Route 53 primary and secondary failover records with applicable health checks. Fail the primary health target and inspect authoritative DNS responses.
D:Weighted records distribute DNS responses but do not implement the required primary/secondary health-triggered switchover on their own. Use the primary and secondary failover record types with health checks.
Question 362
Two active Regions should both serve traffic, excluding an unhealthy regional endpoint. Which DNS arrangement fits?
- Create explicit primary and secondary records under a Route 53 failover routing policy.
- Route 53 can return the secondary record even if its endpoint is not actually healthy.
- Configure Route 53 primary and secondary failover records with applicable health checks.
- Use a suitable active-active Route 53 routing policy with evaluated endpoint health.
Explanation
Correct Answer
D:Latency or weighted records can serve healthy endpoints while removing unhealthy answers. Disable one Region's health endpoint and inspect DNS answer changes.
Incorrect Answers
A:An ordinary simple A record does not express active/passive health-based routing behavior. Use a suitable active-active Route 53 routing policy with evaluated endpoint health. Disable one Region's health endpoint and inspect DNS answer changes.
B:Without secondary health validation, DNS failover presumes that secondary as an available fallback. Use a suitable active-active Route 53 routing policy with evaluated endpoint health. Disable one Region's health endpoint and inspect DNS answer changes.
C:Failover records return the healthy secondary when the primary is deemed unhealthy. Use a suitable active-active Route 53 routing policy with evaluated endpoint health. Disable one Region's health endpoint and inspect DNS answer changes.
Question 363
A health check polls a homepage that still returns 200 during a database failure. What should be monitored instead?
- Use a CloudWatch alarm-based Route 53 health check driven by the private endpoint's metrics.
- Route 53 can return the secondary record even if its endpoint is not actually healthy.
- Configure Route 53 primary and secondary failover records with applicable health checks.
- Point the Route 53 health check at an application endpoint that reflects required dependency health.
Explanation
Correct Answer
D:Traffic failover requires a health signal that corresponds to useful service availability. Fail the database and verify the primary health check becomes unhealthy.
Incorrect Answers
A:A CloudWatch metric/alarm can reflect private workload health without exposing the endpoint publicly. Point the Route 53 health check at an application endpoint that reflects required dependency health. Fail the database and verify the primary health check becomes unhealthy.
B:Without secondary health validation, DNS failover presumes that secondary as an available fallback. Point the Route 53 health check at an application endpoint that reflects required dependency health. Fail the database and verify the primary health check becomes unhealthy.
C:Failover records return the healthy secondary when the primary is deemed unhealthy. Point the Route 53 health check at an application endpoint that reflects required dependency health. Fail the database and verify the primary health check becomes unhealthy.
Question 364
A Route 53 failover test succeeds at the authoritative DNS level but users remain on the old endpoint for several minutes. What explains the delay?
- Route 53 can return the secondary record even if its endpoint is not actually healthy.
- Use a suitable active-active Route 53 routing policy with evaluated endpoint health.
- DNS resolvers and clients can retain cached records until their TTLs and refresh behavior allow change.
- Create explicit primary and secondary records under a Route 53 failover routing policy.
Explanation
Correct Answer
C:DNS health changes affect new answers, not every existing cached resolution or active connection instantly. Compare authoritative answers with a client's cached record during failover.
Incorrect Answers
A:Without secondary health validation, DNS failover presumes that secondary as an available fallback. DNS resolvers and clients can retain cached records until their TTLs and refresh behavior allow change. Compare authoritative answers with a client's cached record during failover.
B:Latency or weighted records can serve healthy endpoints while removing unhealthy answers. DNS resolvers and clients can retain cached records until their TTLs and refresh behavior allow change. Compare authoritative answers with a client's cached record during failover.
D:An ordinary simple A record does not express active/passive health-based routing behavior. DNS resolvers and clients can retain cached records until their TTLs and refresh behavior allow change. Compare authoritative answers with a client's cached record during failover.
Question 365
A health check target is private inside a VPC and cannot be reached by public Route 53 checkers. Which pattern provides a health signal?
- Point the Route 53 health check at an application endpoint that reflects required dependency health.
- Use a CloudWatch alarm-based Route 53 health check driven by the private endpoint's metrics.
- Use a suitable active-active Route 53 routing policy with evaluated endpoint health.
- Route 53 can return the secondary record even if its endpoint is not actually healthy.
Explanation
Correct Answer
B:A CloudWatch metric/alarm can reflect private workload health without exposing the endpoint publicly. Mark the private metric unhealthy and observe the DNS health check state.
Incorrect Answers
A:Traffic failover requires a health signal that corresponds to useful service availability. Use a CloudWatch alarm-based Route 53 health check driven by the private endpoint's metrics. Mark the private metric unhealthy and observe the DNS health check state.
C:Latency or weighted records can serve healthy endpoints while removing unhealthy answers. Use a CloudWatch alarm-based Route 53 health check driven by the private endpoint's metrics. Mark the private metric unhealthy and observe the DNS health check state.
D:Without secondary health validation, DNS failover presumes that secondary as an available fallback. Use a CloudWatch alarm-based Route 53 health check driven by the private endpoint's metrics. Mark the private metric unhealthy and observe the DNS health check state.
Question 366
A record uses Route 53 alias routing to an ALB and should reflect its backend health. Which setting matters?
- Route 53 can return the secondary record even if its endpoint is not actually healthy.
- Use a CloudWatch alarm-based Route 53 health check driven by the private endpoint's metrics.
- Enable Evaluate Target Health where supported for the alias target.
- DNS resolvers and clients can retain cached records until their TTLs and refresh behavior allow change.
Explanation
Correct Answer
C:Alias health evaluation can consider supported AWS target health when selecting DNS results. Make every target unhealthy and observe the alias record's health evaluation.
Incorrect Answers
A:Without secondary health validation, DNS failover presumes that secondary as an available fallback. Enable Evaluate Target Health where supported for the alias target. Make every target unhealthy and observe the alias record's health evaluation.
B:A CloudWatch metric/alarm can reflect private workload health without exposing the endpoint publicly. Enable Evaluate Target Health where supported for the alias target. Make every target unhealthy and observe the alias record's health evaluation.
D:DNS health changes affect new answers, not every existing cached resolution or active connection instantly. Enable Evaluate Target Health where supported for the alias target. Make every target unhealthy and observe the alias record's health evaluation.
Question 367
The secondary failover record lacks a health check, and the primary health check fails. What result is expected?
- Use a CloudWatch alarm-based Route 53 health check driven by the private endpoint's metrics.
- Route 53 can return the secondary record even if its endpoint is not actually healthy.
- Create explicit primary and secondary records under a Route 53 failover routing policy.
- Configure Route 53 primary and secondary failover records with applicable health checks.
Explanation
Correct Answer
B:Without secondary health validation, DNS failover presumes that secondary as an available fallback. Disable the secondary service and inspect the authoritative failover response.
Incorrect Answers
A:A CloudWatch metric/alarm can reflect private workload health without exposing the endpoint publicly. Route 53 can return the secondary record even if its endpoint is not actually healthy. Disable the secondary service and inspect the authoritative failover response.
C:An ordinary simple A record does not express active/passive health-based routing behavior. Route 53 can return the secondary record even if its endpoint is not actually healthy. Disable the secondary service and inspect the authoritative failover response.
D:Failover records return the healthy secondary when the primary is deemed unhealthy. Route 53 can return the secondary record even if its endpoint is not actually healthy. Disable the secondary service and inspect the authoritative failover response.
Question 368
A site currently sends all DNS queries to an outage-prone primary even when a backup is online. Which basic record relation must be declared?
- Route 53 can return the secondary record even if its endpoint is not actually healthy.
- Create primary and secondary Route 53 records but mark both as Primary and omit the secondary failover designation.
- Create explicit primary and secondary records under a Route 53 failover routing policy.
- Use a suitable active-active Route 53 routing policy with evaluated endpoint health.
Explanation
Correct Answer
C:An ordinary simple A record does not express active/passive health-based routing behavior. Query DNS before and after marking the primary unhealthy.
Incorrect Answers
A:Without secondary health validation, DNS failover presumes that secondary as an available fallback. Create explicit primary and secondary records under a Route 53 failover routing policy. Query DNS before and after marking the primary unhealthy.
B:Two records designated as Primary do not implement the explicit primary/secondary failover relationship required for the existing standby. Configure the supported primary and secondary failover record roles.
D:Latency or weighted records can serve healthy endpoints while removing unhealthy answers. Create explicit primary and secondary records under a Route 53 failover routing policy. Query DNS before and after marking the primary unhealthy.
Question 369
A database-backed service must automatically survive an Availability Zone failure and also reduce analytics SELECT load on the transaction writer. It can tolerate slightly stale reporting reads. Which TWO database capabilities best fit? (Select TWO.)
- Deploy a supported RDS Multi-AZ configuration with managed failover for the database engine.
- Scale the application ALB to increase the database writer’s SQL read capacity without database changes.
- Use the Multi-AZ standby as the normal read-only reporting endpoint in a traditional Multi-AZ DB instance deployment.
- Provision RDS read replicas and direct reporting clients to their replica endpoints.
- Replace every database backup with a single read replica and claim a replica is an immutable recovery copy.
Explanation
Correct Answers
A:A Multi-AZ deployment supplies a standby/failover capability; it is a high-availability control rather than a read-throughput feature by itself.
D:Read replicas can offload eligible SELECTs from the writer, with asynchronous lag accounted for by the reporting application.
Incorrect Answers
B:An ALB is not a SQL read replica and cannot directly move SELECT workload away from the primary database.
C:The standby in a standard RDS Multi-AZ DB instance is for failover and cannot serve ordinary reporting queries.
E:A read replica can propagate unwanted changes and is not an independent point-in-time backup strategy.
Question 370
An RDS Multi-AZ DB instance deployment has one passive standby; read-only queries overwhelm the writer. What additional architecture is needed?
- Add appropriate RDS read replicas or choose a Multi-AZ DB cluster offering readable standbys when supported.
- A traditional Multi-AZ DB instance standby is for failover, not readable query offload.
- Deploy a supported RDS Multi-AZ configuration for the database engine.
- Use an RDS Multi-AZ DB cluster with two readable standby DB instances.
Explanation
Correct Answer
A:A traditional Multi-AZ DB instance standby does not serve read queries, so HA alone does not scale reads. Direct test reads to the reader endpoint and observe writer load.
Incorrect Answers
B:Read scaling requires a supported read replica or a different readable Multi-AZ cluster architecture. Add appropriate RDS read replicas or choose a Multi-AZ DB cluster offering readable standbys when supported. Direct test reads to the reader endpoint and observe writer load.
C:RDS provisions standby capacity in a separate AZ and manages failover on supported configurations. Add appropriate RDS read replicas or choose a Multi-AZ DB cluster offering readable standbys when supported. Direct test reads to the reader endpoint and observe writer load.
D:Unlike traditional one-standby Multi-AZ instances, Multi-AZ DB clusters can expose reader capacity. Add appropriate RDS read replicas or choose a Multi-AZ DB cluster offering readable standbys when supported. Direct test reads to the reader endpoint and observe writer load.