Amazon AWS Certified Solutions Architect - Associate SAA-C03 Practice Test 78
Question 770
A production migration proposes deleting one of two NAT gateways solely to halve hourly fees; both AZs must independently survive one-zone outages and current cross-AZ traffic is material. Which constraint should control the decision?
- Compare one shared NAT gateway with per-AZ gateways using actual hourly, processing and cross-AZ charges, then retain one if the accepted failure boundary and total cost justify it.
- Keep zonal NAT egress with independent same-AZ routing unless a tested alternative meets fault tolerance and all-in pricing.
- Route approved outbound IPv6 traffic through an egress-only internet gateway instead of IPv4 NAT translation.
- Use the supported S3 and DynamoDB gateway endpoints and retire the unused NAT gateway after testing.
Explanation
Correct Answer
B:A single shared zonal NAT may lower fixed cost but adds cross-AZ transfers and creates an egress dependency on its host AZ. Review the AZ outage test and monthly gateway plus transfer line items.
Incorrect Answers
A:For low-volume noncritical traffic, another NAT gateway's fixed hourly fee can exceed the saved cross-zone transfer cost. Keep zonal NAT egress with independent same-AZ routing unless a tested alternative meets fault tolerance and all-in pricing. Review the AZ outage test and monthly gateway plus transfer line items.
C:An egress-only internet gateway permits outbound-initiated IPv6 flows and blocks unsolicited inbound initiation without NAT gateway processing. Keep zonal NAT egress with independent same-AZ routing unless a tested alternative meets fault tolerance and all-in pricing. Review the AZ outage test and monthly gateway plus transfer line items.
D:Gateway endpoints can serve those two services without NAT hourly or processing charges, provided route tables and policies are correct. A single shared zonal NAT may lower fixed cost but adds cross-AZ transfers and creates an egress dependency on its host AZ.
Question 771
Private EC2 instances make large same-Region S3 requests through a NAT gateway, and the team needs private service access without paying endpoint-hour or NAT processing fees for those requests. Which endpoint is suitable?
- Keep both endpoints and configure S3 interface endpoint private DNS for the inbound Resolver path so VPC calls use the gateway endpoint.
- Attach an S3 gateway endpoint to the private subnet route tables with appropriate endpoint and bucket permissions.
- Provision the S3 interface endpoint for eligible on-premises private access and account for its PrivateLink fees.
- Use a DynamoDB gateway VPC endpoint in the same Region and associate the consuming subnets' route tables.
Explanation
Correct Answer
B:S3 gateway endpoints carry eligible in-VPC S3 calls without an additional endpoint hourly charge or NAT gateway translation. Trace S3 routes and compare the NAT processed-byte metric before and after.
Incorrect Answers
A:Using the gateway for local VPC traffic while reserving interface routing for hybrid clients can reduce billed interface traffic without breaking private on-premises access. Attach an S3 gateway endpoint to the private subnet route tables with appropriate endpoint and bucket permissions. Trace S3 routes and compare the NAT processed-byte metric before and after.
C:Gateway endpoints are scoped to their VPC route tables; S3 interface endpoints expose private network interfaces reachable through supported hybrid routing. Attach an S3 gateway endpoint to the private subnet route tables with appropriate endpoint and bucket permissions. Trace S3 routes and compare the NAT processed-byte metric before and after.
D:A DynamoDB gateway endpoint routes eligible requests directly without an extra hourly endpoint charge or NAT processing. Attach an S3 gateway endpoint to the private subnet route tables with appropriate endpoint and bucket permissions. Trace S3 routes and compare the NAT processed-byte metric before and after.
Question 772
A VPC reads a large DynamoDB table at sustained throughput through an internet egress gateway. The company wants to avoid network-appliance processing fees while retaining AWS private routing. What is the least extra-charged service path?
- Attach an S3 gateway endpoint to the private subnet route tables with appropriate endpoint and bucket permissions.
- Keep both endpoints and configure S3 interface endpoint private DNS for the inbound Resolver path so VPC calls use the gateway endpoint.
- Use a DynamoDB gateway VPC endpoint in the same Region and associate the consuming subnets' route tables.
- Price required endpoint-hours and processed bytes against existing NAT hours and data volume before replacing the path.
Explanation
Correct Answer
C:A DynamoDB gateway endpoint routes eligible requests directly without an extra hourly endpoint charge or NAT processing. Validate DynamoDB API calls and confirm the gateway endpoint route is selected.
Incorrect Answers
A:S3 gateway endpoints carry eligible in-VPC S3 calls without an additional endpoint hourly charge or NAT gateway translation. Use a DynamoDB gateway VPC endpoint in the same Region and associate the consuming subnets' route tables. Validate DynamoDB API calls and confirm the gateway endpoint route is selected.
B:Using the gateway for local VPC traffic while reserving interface routing for hybrid clients can reduce billed interface traffic without breaking private on-premises access. Use a DynamoDB gateway VPC endpoint in the same Region and associate the consuming subnets' route tables. Validate DynamoDB API calls and confirm the gateway endpoint route is selected.
D:Interface endpoints have fixed and usage-based fees; their cost advantage depends on traffic and how many zonal interfaces are needed. A DynamoDB gateway endpoint routes eligible requests directly without an extra hourly endpoint charge or NAT processing.
Question 773
A data center connects to AWS over Direct Connect and must use private IPs to reach S3. A VPC's S3 gateway endpoint works for EC2 but cannot serve on-premises clients. Which supported connectivity mechanism fits?
- Keep both endpoints and configure S3 interface endpoint private DNS for the inbound Resolver path so VPC calls use the gateway endpoint.
- Attach an S3 gateway endpoint to the private subnet route tables with appropriate endpoint and bucket permissions.
- Provision the S3 interface endpoint for eligible on-premises private access and account for its PrivateLink fees.
- Price required endpoint-hours and processed bytes against existing NAT hours and data volume before replacing the path.
Explanation
Correct Answer
C:Gateway endpoints are scoped to their VPC route tables; S3 interface endpoints expose private network interfaces reachable through supported hybrid routing. Query the endpoint DNS from on premises and verify successful private S3 calls.
Incorrect Answers
A:Using the gateway for local VPC traffic while reserving interface routing for hybrid clients can reduce billed interface traffic without breaking private on-premises access. Provision the S3 interface endpoint for eligible on-premises private access and account for its PrivateLink fees. Query the endpoint DNS from on premises and verify successful private S3 calls.
B:S3 gateway endpoints carry eligible in-VPC S3 calls without an additional endpoint hourly charge or NAT gateway translation. Provision the S3 interface endpoint for eligible on-premises private access and account for its PrivateLink fees. Query the endpoint DNS from on premises and verify successful private S3 calls.
D:Interface endpoints have fixed and usage-based fees; their cost advantage depends on traffic and how many zonal interfaces are needed. Gateway endpoints are scoped to their VPC route tables; S3 interface endpoints expose private network interfaces reachable through supported hybrid routing.
Question 774
A hybrid application uses a billed S3 interface endpoint for every VPC request even though local applications could use an existing free gateway endpoint; on-premises clients still need interface connectivity. Which DNS and endpoint arrangement can reduce interface processing fees?
- Keep both endpoints and configure S3 interface endpoint private DNS for the inbound Resolver path so VPC calls use the gateway endpoint.
- Create healthy interface endpoint ENIs in each consuming AZ and verify private DNS and availability against additional endpoint-hour cost.
- Provision the S3 interface endpoint for eligible on-premises private access and account for its PrivateLink fees.
- Attach an S3 gateway endpoint to the private subnet route tables with appropriate endpoint and bucket permissions.
Explanation
Correct Answer
A:Using the gateway for local VPC traffic while reserving interface routing for hybrid clients can reduce billed interface traffic without breaking private on-premises access. Resolve S3 names from the VPC and on premises and check endpoint usage charges.
Incorrect Answers
B:Zonal endpoint placement can avoid cross-AZ private routing and a single-zone dependency while adding per-AZ endpoint charges. Keep both endpoints and configure S3 interface endpoint private DNS for the inbound Resolver path so VPC calls use the gateway endpoint. Resolve S3 names from the VPC and on premises and check endpoint usage charges.
C:Gateway endpoints are scoped to their VPC route tables; S3 interface endpoints expose private network interfaces reachable through supported hybrid routing. Keep both endpoints and configure S3 interface endpoint private DNS for the inbound Resolver path so VPC calls use the gateway endpoint. Resolve S3 names from the VPC and on premises and check endpoint usage charges.
D:S3 gateway endpoints carry eligible in-VPC S3 calls without an additional endpoint hourly charge or NAT gateway translation. Keep both endpoints and configure S3 interface endpoint private DNS for the inbound Resolver path so VPC calls use the gateway endpoint. Resolve S3 names from the VPC and on premises and check endpoint usage charges.
Question 775
A low-volume Lambda service calls a single supported AWS service through a NAT gateway. An architect proposes three paid interface endpoint ENIs and claims they always cost less. What is the proper decision?
- Keep both endpoints and configure S3 interface endpoint private DNS for the inbound Resolver path so VPC calls use the gateway endpoint.
- Create healthy interface endpoint ENIs in each consuming AZ and verify private DNS and availability against additional endpoint-hour cost.
- Price required endpoint-hours and processed bytes against existing NAT hours and data volume before replacing the path.
- Provision the S3 interface endpoint for eligible on-premises private access and account for its PrivateLink fees.
Explanation
Correct Answer
C:Interface endpoints have fixed and usage-based fees; their cost advantage depends on traffic and how many zonal interfaces are needed. Compare billed hours and processed-byte projections for the same call volume.
Incorrect Answers
A:Using the gateway for local VPC traffic while reserving interface routing for hybrid clients can reduce billed interface traffic without breaking private on-premises access. Price required endpoint-hours and processed bytes against existing NAT hours and data volume before replacing the path. Compare billed hours and processed-byte projections for the same call volume.
B:Zonal endpoint placement can avoid cross-AZ private routing and a single-zone dependency while adding per-AZ endpoint charges. Price required endpoint-hours and processed bytes against existing NAT hours and data volume before replacing the path. Compare billed hours and processed-byte projections for the same call volume.
D:Gateway endpoints are scoped to their VPC route tables; S3 interface endpoints expose private network interfaces reachable through supported hybrid routing. Price required endpoint-hours and processed bytes against existing NAT hours and data volume before replacing the path. Compare billed hours and processed-byte projections for the same call volume.
Question 776
Two AZs host critical consumers of an interface endpoint, but all endpoint ENIs sit in AZ-a. AZ-b sends most traffic and must operate during an AZ-a failure. What tradeoff should be evaluated?
- Price required endpoint-hours and processed bytes against existing NAT hours and data volume before replacing the path.
- Provision the S3 interface endpoint for eligible on-premises private access and account for its PrivateLink fees.
- Create healthy interface endpoint ENIs in each consuming AZ and verify private DNS and availability against additional endpoint-hour cost.
- Attach an S3 gateway endpoint to the private subnet route tables with appropriate endpoint and bucket permissions.
Explanation
Correct Answer
C:Zonal endpoint placement can avoid cross-AZ private routing and a single-zone dependency while adding per-AZ endpoint charges. Test endpoint DNS and service requests from both AZs during a failure simulation.
Incorrect Answers
A:Interface endpoints have fixed and usage-based fees; their cost advantage depends on traffic and how many zonal interfaces are needed. Create healthy interface endpoint ENIs in each consuming AZ and verify private DNS and availability against additional endpoint-hour cost. Test endpoint DNS and service requests from both AZs during a failure simulation.
B:Gateway endpoints are scoped to their VPC route tables; S3 interface endpoints expose private network interfaces reachable through supported hybrid routing. Create healthy interface endpoint ENIs in each consuming AZ and verify private DNS and availability against additional endpoint-hour cost. Test endpoint DNS and service requests from both AZs during a failure simulation.
D:S3 gateway endpoints carry eligible in-VPC S3 calls without an additional endpoint hourly charge or NAT gateway translation. Zonal endpoint placement can avoid cross-AZ private routing and a single-zone dependency while adding per-AZ endpoint charges.
Question 777
A private Network Load Balancer returns addresses from every enabled AZ to clients in AZ-a. Healthy zonal targets already exist locally, and cross-AZ client-to-NLB traffic dominates transfer fees. What setting should be evaluated?
- Enable the NLB's 100% Availability Zone DNS affinity where client resolver support and capacity permit.
- Supply and maintain enough healthy targets in every served AZ before relying on purely zonal NLB target selection.
- Disable cross-zone load balancing for the applicable NLB and target group after confirming zonal target capacity.
- Distinguish same-AZ and cross-AZ client-to-NLB and NLB-to-target flows before selecting an affinity or cross-zone setting.
Explanation
Correct Answer
A:Zonal DNS affinity directs supported clients toward local NLB addresses instead of distributing them equally across AZs. Measure cross-AZ client flows and verify enough healthy zonal capacity.
Incorrect Answers
B:Cross-zone disablement is safe only where zonal targets can serve the clients directed to each enabled AZ. Enable the NLB's 100% Availability Zone DNS affinity where client resolver support and capacity permit. Measure cross-AZ client flows and verify enough healthy zonal capacity.
C:Avoiding unnecessary NLB-to-target cross-zone forwarding can reduce billed inter-AZ traffic when local target populations are sufficient. Enable the NLB's 100% Availability Zone DNS affinity where client resolver support and capacity permit. Measure cross-AZ client flows and verify enough healthy zonal capacity.
D:A single Region can still contain billable inter-AZ legs; the right optimization depends on which hop crosses zones. Enable the NLB's 100% Availability Zone DNS affinity where client resolver support and capacity permit. Measure cross-AZ client flows and verify enough healthy zonal capacity.
Question 778
A Network Load Balancer forwards much of its AZ-a traffic to targets in AZ-b because cross-zone load balancing was enabled. Each AZ has adequate healthy targets and must remain independently serviceable. Which optimization is relevant?
- Disable cross-zone load balancing for the applicable NLB and target group after confirming zonal target capacity.
- Supply and maintain enough healthy targets in every served AZ before relying on purely zonal NLB target selection.
- Distinguish same-AZ and cross-AZ client-to-NLB and NLB-to-target flows before selecting an affinity or cross-zone setting.
- Co-locate the high-volume worker and the read-serving replica in one AZ while preserving required multi-AZ recovery paths.
Explanation
Correct Answer
A:Avoiding unnecessary NLB-to-target cross-zone forwarding can reduce billed inter-AZ traffic when local target populations are sufficient. Compare target placement, failure behavior and inter-AZ bytes before and after.
Incorrect Answers
B:Cross-zone disablement is safe only where zonal targets can serve the clients directed to each enabled AZ. Disable cross-zone load balancing for the applicable NLB and target group after confirming zonal target capacity. Compare target placement, failure behavior and inter-AZ bytes before and after.
C:A single Region can still contain billable inter-AZ legs; the right optimization depends on which hop crosses zones. Disable cross-zone load balancing for the applicable NLB and target group after confirming zonal target capacity. Compare target placement, failure behavior and inter-AZ bytes before and after.
D:Same-AZ steady-state communication can reduce cross-AZ billed bytes without removing independent recovery capacity. Avoiding unnecessary NLB-to-target cross-zone forwarding can reduce billed inter-AZ traffic when local target populations are sufficient.
Question 779
A team switches off NLB cross-zone balancing to save money, but one enabled AZ has no registered healthy targets. Users routed to that AZ experience failures. What prerequisite was ignored?
- Supply and maintain enough healthy targets in every served AZ before relying on purely zonal NLB target selection.
- Disable cross-zone load balancing for the applicable NLB and target group after confirming zonal target capacity.
- Enable the NLB's 100% Availability Zone DNS affinity where client resolver support and capacity permit.
- Co-locate the high-volume worker and the read-serving replica in one AZ while preserving required multi-AZ recovery paths.
Explanation
Correct Answer
A:Cross-zone disablement is safe only where zonal targets can serve the clients directed to each enabled AZ. Inspect target health and verify successful requests via each AZ address.
Incorrect Answers
B:Avoiding unnecessary NLB-to-target cross-zone forwarding can reduce billed inter-AZ traffic when local target populations are sufficient. Supply and maintain enough healthy targets in every served AZ before relying on purely zonal NLB target selection. Inspect target health and verify successful requests via each AZ address.
C:Zonal DNS affinity directs supported clients toward local NLB addresses instead of distributing them equally across AZs. Supply and maintain enough healthy targets in every served AZ before relying on purely zonal NLB target selection. Inspect target health and verify successful requests via each AZ address.
D:Same-AZ steady-state communication can reduce cross-AZ billed bytes without removing independent recovery capacity. Cross-zone disablement is safe only where zonal targets can serve the clients directed to each enabled AZ.
Question 780
A batch worker in AZ-a repeatedly exchanges terabytes with a reporting reader in AZ-b. Both run in the same Region, and the architecture has other AZs for independent recovery. What placement change is worth testing?
- Co-locate the high-volume worker and the read-serving replica in one AZ while preserving required multi-AZ recovery paths.
- Distinguish same-AZ and cross-AZ client-to-NLB and NLB-to-target flows before selecting an affinity or cross-zone setting.
- Disable cross-zone load balancing for the applicable NLB and target group after confirming zonal target capacity.
- Enable the NLB's 100% Availability Zone DNS affinity where client resolver support and capacity permit.
Explanation
Correct Answer
A:Same-AZ steady-state communication can reduce cross-AZ billed bytes without removing independent recovery capacity. Compare application latency, inter-AZ charges and failover tests after placement.
Incorrect Answers
B:A single Region can still contain billable inter-AZ legs; the right optimization depends on which hop crosses zones. Co-locate the high-volume worker and the read-serving replica in one AZ while preserving required multi-AZ recovery paths. Compare application latency, inter-AZ charges and failover tests after placement.
C:Avoiding unnecessary NLB-to-target cross-zone forwarding can reduce billed inter-AZ traffic when local target populations are sufficient. Co-locate the high-volume worker and the read-serving replica in one AZ while preserving required multi-AZ recovery paths. Compare application latency, inter-AZ charges and failover tests after placement.
D:Zonal DNS affinity directs supported clients toward local NLB addresses instead of distributing them equally across AZs. Same-AZ steady-state communication can reduce cross-AZ billed bytes without removing independent recovery capacity.