Amazon AWS Certified Solutions Architect - Associate SAA-C03 Practice Test 61
Question 600
A production API should use backup ALB only after primary endpoint health fails. Which DNS strategy fits?
- Use Route 53 failover records with meaningful health checks.
- Use Route 53 geolocation routing with coverage and fallback records.
- Use weighted DNS records for blue and green targets.
- Deploy Route 53 Resolver inbound endpoints and on-premises forwarding rules.
Explanation
Correct Answer
A:Failover records select a secondary endpoint when the primary becomes unhealthy. Simulate an application-level health failure.
Incorrect Answers
B:Geolocation policies route by query-origin geography, not endpoint latency. Use Route 53 failover records with meaningful health checks. Simulate an application-level health failure.
C:Weighted routing distributes DNS answers according to configured proportions. Use Route 53 failover records with meaningful health checks. Simulate an application-level health failure.
D:Private VPC DNS is reachable from on-premises only through suitable resolver integration. Failover records select a secondary endpoint when the primary becomes unhealthy.
Question 601
A private hosted zone resolves for EC2 but not for on-premises users. Which hybrid DNS connectivity fits?
- Configure Route 53 Resolver outbound endpoints and forwarding rules.
- Configure Route 53 latency-based routing records for regional endpoints.
- Deploy Route 53 Resolver inbound endpoints and on-premises forwarding rules.
- Use a private hosted zone for VPC resolution alongside an appropriate public hosted zone.
Explanation
Correct Answer
C:Private VPC DNS is reachable from on-premises only through suitable resolver integration. Resolve a private domain name from the office network.
Incorrect Answers
A:Outbound DNS forwarding sends VPC queries for selected zones to external resolvers. Deploy Route 53 Resolver inbound endpoints and on-premises forwarding rules. Resolve a private domain name from the office network.
B:Latency policies use measurements to choose eligible regional answers. Deploy Route 53 Resolver inbound endpoints and on-premises forwarding rules. Resolve a private domain name from the office network.
D:Split-horizon DNS provides different answers based on query resolution context. Deploy Route 53 Resolver inbound endpoints and on-premises forwarding rules. Resolve a private domain name from the office network.
Question 602
EC2 workloads need to resolve data-center.internal through the existing corporate DNS servers. Which Resolver direction is correct?
- Configure Route 53 latency-based routing records for regional endpoints.
- Deploy Route 53 Resolver inbound endpoints and on-premises forwarding rules.
- Configure Route 53 Resolver outbound endpoints and forwarding rules.
- Use weighted DNS records for blue and green targets.
Explanation
Correct Answer
C:Outbound DNS forwarding sends VPC queries for selected zones to external resolvers. Resolve a private data-center hostname from EC2.
Incorrect Answers
A:Latency policies use measurements to choose eligible regional answers. Configure Route 53 Resolver outbound endpoints and forwarding rules. Resolve a private data-center hostname from EC2.
B:Private VPC DNS is reachable from on-premises only through suitable resolver integration. Configure Route 53 Resolver outbound endpoints and forwarding rules. Resolve a private data-center hostname from EC2.
D:Weighted routing distributes DNS answers according to configured proportions. Outbound DNS forwarding sends VPC queries for selected zones to external resolvers.
Question 603
An application switches regional DNS answers but some clients still connect to a failed endpoint. What network behavior should be considered?
- Account for DNS TTL and caching before defining failover recovery times.
- Use weighted DNS records for blue and green targets.
- Configure Route 53 latency-based routing records for regional endpoints.
- Use a private hosted zone for VPC resolution alongside an appropriate public hosted zone.
Explanation
Correct Answer
A:Previously cached DNS responses can outlive changes in authoritative routing answers. Measure client-side cache expiry during failover.
Incorrect Answers
B:Weighted routing distributes DNS answers according to configured proportions. Account for DNS TTL and caching before defining failover recovery times. Measure client-side cache expiry during failover.
C:Latency policies use measurements to choose eligible regional answers. Account for DNS TTL and caching before defining failover recovery times. Measure client-side cache expiry during failover.
D:Split-horizon DNS provides different answers based on query resolution context. Account for DNS TTL and caching before defining failover recovery times. Measure client-side cache expiry during failover.
Question 604
A company needs the same domain to resolve to internal addresses inside its VPC and public addresses elsewhere. Which DNS pattern fits?
- Deploy Route 53 Resolver inbound endpoints and on-premises forwarding rules.
- Configure Route 53 latency-based routing records for regional endpoints.
- Use a private hosted zone for VPC resolution alongside an appropriate public hosted zone.
- Use weighted DNS records for blue and green targets.
Explanation
Correct Answer
C:Split-horizon DNS provides different answers based on query resolution context. Query from inside and outside the VPC.
Incorrect Answers
A:Private VPC DNS is reachable from on-premises only through suitable resolver integration. Use a private hosted zone for VPC resolution alongside an appropriate public hosted zone. Query from inside and outside the VPC.
B:Latency policies use measurements to choose eligible regional answers. Use a private hosted zone for VPC resolution alongside an appropriate public hosted zone. Query from inside and outside the VPC.
D:Weighted routing distributes DNS answers according to configured proportions. Use a private hosted zone for VPC resolution alongside an appropriate public hosted zone. Query from inside and outside the VPC.
Question 605
IoT devices continuously generate events that must be delivered into S3 without writing custom consumer servers. Which managed service fits?
- Configure appropriate Firehose buffering size and interval.
- Use Firehose with an approved destination and S3 error backup settings.
- Use Amazon Data Firehose with an S3 destination and supported buffering.
- Use a supported Lambda transformation step in the Firehose delivery pipeline.
Explanation
Correct Answer
C:Firehose manages delivery of streaming records to supported destinations. Verify S3 delivery objects and error records.
Incorrect Answers
A:Delivery buffering batches records into larger objects under eligible conditions. Use Amazon Data Firehose with an S3 destination and supported buffering. Verify S3 delivery objects and error records.
B:Managed delivery pipelines can preserve failed transformed/delivered records for review. Use Amazon Data Firehose with an S3 destination and supported buffering. Verify S3 delivery objects and error records.
D:Firehose can invoke Lambda transforms for eligible delivery records. Use Amazon Data Firehose with an S3 destination and supported buffering. Verify S3 delivery objects and error records.
Question 606
A streaming app requires multiple independent readers and explicit event replay for several days. Which ingestion service fits?
- Use SNS Standard as the sole persistent log and assume consumers can replay its events several days later.
- Use Kinesis Data Streams with sufficient configured retention.
- Use Amazon Data Firehose with an S3 destination and supported buffering.
- Choose more evenly distributed Kinesis partition keys for hot data.
Explanation
Correct Answer
B:Data Streams supports multiple consumers with ordered shard records and retention. Stop and restart a consumer from an earlier iterator.
Incorrect Answers
A:SNS distributes events to subscribers but is not itself a durable ordered stream with multi-day consumer replay. Kinesis Data Streams can retain records for replay when its configured retention covers the required window.
C:Firehose manages delivery of streaming records to supported destinations. Use Kinesis Data Streams with sufficient configured retention. Stop and restart a consumer from an earlier iterator.
D:Partition key skew can saturate a shard independent of total stream capacity. Use Kinesis Data Streams with sufficient configured retention. Stop and restart a consumer from an earlier iterator.
Question 607
A batch data producer wants periodic buffered S3 objects rather than one small object per sensor message. What Firehose setting matters?
- Use a supported Lambda transformation step in the Firehose delivery pipeline.
- Configure appropriate Firehose buffering size and interval.
- Use Firehose with an approved destination and S3 error backup settings.
- Use Kinesis Data Streams with sufficient configured retention.
Explanation
Correct Answer
B:Delivery buffering batches records into larger objects under eligible conditions. Observe object sizes and delivery latency.
Incorrect Answers
A:Firehose can invoke Lambda transforms for eligible delivery records. Configure appropriate Firehose buffering size and interval. Observe object sizes and delivery latency.
C:Managed delivery pipelines can preserve failed transformed/delivered records for review. Configure appropriate Firehose buffering size and interval. Observe object sizes and delivery latency.
D:Data Streams supports multiple consumers with ordered shard records and retention. Delivery buffering batches records into larger objects under eligible conditions.
Question 608
A stream's shard is throttled because all records use one constant partition key. What data-ingestion correction matters?
- Monitor IteratorAge and processing throughput against stream capacity.
- Use Kinesis Data Streams or another durable ordered log for replay-based consumers.
- Choose more evenly distributed Kinesis partition keys for hot data.
- Use Kinesis Data Streams with sufficient configured retention.
Explanation
Correct Answer
C:Partition key skew can saturate a shard independent of total stream capacity. Inspect per-shard write throttles.
Incorrect Answers
A:Consumer lag measures how far behind event processing has fallen. Choose more evenly distributed Kinesis partition keys for hot data. Inspect per-shard write throttles.
B:SNS pub/sub delivery does not replace a retention-based replayable data stream. Choose more evenly distributed Kinesis partition keys for hot data. Inspect per-shard write throttles.
D:Data Streams supports multiple consumers with ordered shard records and retention. Choose more evenly distributed Kinesis partition keys for hot data. Inspect per-shard write throttles.
Question 609
A company streams JSON telemetry into a governed S3 landing bucket. It wants managed ingest, lightweight record transformation, and evidence of unsuccessful delivery. Which THREE Firehose-related components should it configure? (Select THREE.)
- Configure the supported Lambda record transformation within the Firehose delivery pipeline.
- Use an S3 static website configuration as the managed telemetry ingestion engine.
- Deploy a single local file on an EC2 instance as the only buffer and assume it is managed Firehose.
- Configure Firehose delivery logging and approved error/failed-record handling for the S3 destination.
- Make every malformed record vanish silently and disable all delivery logging.
- Use Amazon Data Firehose with an S3 destination and compatible buffering/delivery settings.
Explanation
Correct Answers
A:A Firehose Lambda transform can validate or reshape eligible source records before delivery to S3.
D:Delivery failure metrics, logging, and failed-record paths provide operational evidence and bounded recovery options.
F:Firehose provides managed delivery to supported destinations including S3 without a self-managed streaming cluster.
Incorrect Answers
B:A public website endpoint cannot replace a Firehose stream and its delivery pipeline.
C:A host-local buffer lacks the managed stream ingestion, Lambda integration, and durability model described.
E:Dropping failed records without logging violates the evidence and recovery requirement.
Question 610
A Kinesis consumer reads events too slowly and processing lag grows. What metric should direct scaling decisions?
- Monitor IteratorAge and processing throughput against stream capacity.
- Choose more evenly distributed Kinesis partition keys for hot data.
- Use Kinesis Data Streams or another durable ordered log for replay-based consumers.
- Use Amazon Data Firehose with an S3 destination and supported buffering.
Explanation
Correct Answer
A:Consumer lag measures how far behind event processing has fallen. Increase consumer capacity and compare IteratorAge.
Incorrect Answers
B:Partition key skew can saturate a shard independent of total stream capacity. Monitor IteratorAge and processing throughput against stream capacity. Increase consumer capacity and compare IteratorAge.
C:SNS pub/sub delivery does not replace a retention-based replayable data stream. Monitor IteratorAge and processing throughput against stream capacity. Increase consumer capacity and compare IteratorAge.
D:Firehose manages delivery of streaming records to supported destinations. Monitor IteratorAge and processing throughput against stream capacity. Increase consumer capacity and compare IteratorAge.