Amazon AWS Certified Solutions Architect - Associate SAA-C03 Practice Test 35
Question 340
A producer team frequently adds consumers in other AWS accounts; what reduces repeated producer code changes?
- Use EventBridge cross-account rules and resource policies rather than direct per-consumer SDK calls.
- Configure approved cross-account EventBridge bus policies and sending rules.
- Add an EventBridge event pattern on the compliance rule matching the approved classification fields.
- Grant the necessary cross-account event-bus access while retaining narrow publisher scope.
Explanation
Correct Answer
A:Event bus integration decouples producer implementation from the consumers' account lifecycle. Add one consumer rule and verify producer binaries remain unchanged.
Incorrect Answers
B:Central event buses accept only authorized publishers and route matched events to audit consumers. Use EventBridge cross-account rules and resource policies rather than direct per-consumer SDK calls. Add one consumer rule and verify producer binaries remain unchanged.
C:Event-pattern filtering occurs at the bus, avoiding unauthorized or irrelevant consumer invocation. Use EventBridge cross-account rules and resource policies rather than direct per-consumer SDK calls. Add one consumer rule and verify producer binaries remain unchanged.
D:Both sending rules and destination resource policies must authorize event transfer across accounts. Use EventBridge cross-account rules and resource policies rather than direct per-consumer SDK calls. Add one consumer rule and verify producer binaries remain unchanged.
Question 341
One business event fans out to different destinations, but one target requires a field-remapped payload. Which routing feature fits?
- Use an EventBridge input transformer on the applicable rule target.
- Use EventBridge cross-account rules and resource policies rather than direct per-consumer SDK calls.
- Add an EventBridge event pattern on the compliance rule matching the approved classification fields.
- Archive eligible events on the receiving EventBridge bus and replay a bounded interval when repaired.
Explanation
Correct Answer
A:An input transformer constructs target-specific payloads without rewriting the original event producer. Compare original event and transformed target payload fields.
Incorrect Answers
B:Event bus integration decouples producer implementation from the consumers' account lifecycle. Use an EventBridge input transformer on the applicable rule target. Compare original event and transformed target payload fields.
C:Event-pattern filtering occurs at the bus, avoiding unauthorized or irrelevant consumer invocation. Use an EventBridge input transformer on the applicable rule target. Compare original event and transformed target payload fields.
D:Consumer-side replay enables recovery without forcing all publishers to resend business transactions. Use an EventBridge input transformer on the applicable rule target. Compare original event and transformed target payload fields.
Question 342
An event targeting another account fails because its bus policy denies the caller. Which fix is relevant?
- Use EventBridge cross-account rules and resource policies rather than direct per-consumer SDK calls.
- Grant the necessary cross-account event-bus access while retaining narrow publisher scope.
- Configure approved cross-account EventBridge bus policies and sending rules.
- Publish limited, nonsecret event metadata through an authorized event bus.
Explanation
Correct Answer
B:Both sending rules and destination resource policies must authorize event transfer across accounts. Call PutEvents using the sending identity and inspect the destination event bus.
Incorrect Answers
A:Event bus integration decouples producer implementation from the consumers' account lifecycle. Grant the necessary cross-account event-bus access while retaining narrow publisher scope. Call PutEvents using the sending identity and inspect the destination event bus.
C:Central event buses accept only authorized publishers and route matched events to audit consumers. Grant the necessary cross-account event-bus access while retaining narrow publisher scope. Call PutEvents using the sending identity and inspect the destination event bus.
D:A focused event contract communicates incidents without sharing database credentials or broad data access. Both sending rules and destination resource policies must authorize event transfer across accounts.
Question 343
Cross-account applications need event replay after a consumer defect, but publishers should remain unaffected. What should be retained?
- Use EventBridge cross-account rules and resource policies rather than direct per-consumer SDK calls.
- Archive eligible events on the receiving EventBridge bus and replay a bounded interval when repaired.
- Configure approved cross-account EventBridge bus policies and sending rules.
- Add an EventBridge event pattern on the compliance rule matching the approved classification fields.
Explanation
Correct Answer
B:Consumer-side replay enables recovery without forcing all publishers to resend business transactions. Replay a known interval and verify downstream idempotency.
Incorrect Answers
A:Event bus integration decouples producer implementation from the consumers' account lifecycle. Archive eligible events on the receiving EventBridge bus and replay a bounded interval when repaired. Replay a known interval and verify downstream idempotency.
C:Central event buses accept only authorized publishers and route matched events to audit consumers. Archive eligible events on the receiving EventBridge bus and replay a bounded interval when repaired. Replay a known interval and verify downstream idempotency.
D:Event-pattern filtering occurs at the bus, avoiding unauthorized or irrelevant consumer invocation. Archive eligible events on the receiving EventBridge bus and replay a bounded interval when repaired. Replay a known interval and verify downstream idempotency.
Question 344
An internal compliance consumer should receive only events with approved classification tags from a shared bus. How should routing be constrained?
- Add an EventBridge event pattern on the compliance rule matching the approved classification fields.
- Use EventBridge cross-account rules and resource policies rather than direct per-consumer SDK calls.
- Use an EventBridge input transformer on the applicable rule target.
- Configure approved cross-account EventBridge bus policies and sending rules.
Explanation
Correct Answer
A:Event-pattern filtering occurs at the bus, avoiding unauthorized or irrelevant consumer invocation. Submit approved and unapproved classifications and inspect delivered events.
Incorrect Answers
B:Event bus integration decouples producer implementation from the consumers' account lifecycle. Add an EventBridge event pattern on the compliance rule matching the approved classification fields. Submit approved and unapproved classifications and inspect delivered events.
C:An input transformer constructs target-specific payloads without rewriting the original event producer. Add an EventBridge event pattern on the compliance rule matching the approved classification fields. Submit approved and unapproved classifications and inspect delivered events.
D:Central event buses accept only authorized publishers and route matched events to audit consumers. Add an EventBridge event pattern on the compliance rule matching the approved classification fields. Submit approved and unapproved classifications and inspect delivered events.
Question 345
An internet-facing application currently uses one EC2 instance in one Availability Zone. How should it survive an AZ outage?
- Enable the load balancer across multiple Availability Zone subnets with healthy targets.
- Enable the ALB in a second Availability Zone but leave all EC2 target instances in the original AZ.
- Create listener path-based routing rules with separate target groups.
- Deploy targets across at least two Availability Zones behind an Application Load Balancer.
Explanation
Correct Answer
D:An ALB routes new requests to healthy targets in surviving enabled zones. Disable targets in one AZ and verify the application remains reachable.
Incorrect Answers
A:ALBs need enabled AZ subnet mappings to provide distributed load-balancing nodes and route to targets. Deploy targets across at least two Availability Zones behind an Application Load Balancer. Disable targets in one AZ and verify the application remains reachable.
B:Adding another ALB subnet without healthy targets in the other Availability Zone leaves the application dependent on its single-AZ compute fleet. The required availability design includes application targets across at least two AZs.
C:ALB listener rules select target groups by HTTP path without deploying a second load balancer. Deploy targets across at least two Availability Zones behind an Application Load Balancer. Disable targets in one AZ and verify the application remains reachable.
Question 346
An ALB marks a working backend unhealthy because the default path redirects to a login page. What should the health check use?
- Make the readiness check reflect the application's critical dependency state.
- Create listener path-based routing rules with separate target groups.
- Deploy targets across at least two Availability Zones behind an Application Load Balancer.
- Configure a dedicated unauthenticated readiness endpoint and appropriate success-code matcher.
Explanation
Correct Answer
D:Health checks must test actual readiness without requiring an interactive user session. Request the health path from the ALB and verify the target enters healthy state.
Incorrect Answers
A:A shallow process-only check can route users to instances that cannot serve useful requests. Configure a dedicated unauthenticated readiness endpoint and appropriate success-code matcher. Request the health path from the ALB and verify the target enters healthy state.
B:ALB listener rules select target groups by HTTP path without deploying a second load balancer. Configure a dedicated unauthenticated readiness endpoint and appropriate success-code matcher. Request the health path from the ALB and verify the target enters healthy state.
C:An ALB routes new requests to healthy targets in surviving enabled zones. Configure a dedicated unauthenticated readiness endpoint and appropriate success-code matcher. Request the health path from the ALB and verify the target enters healthy state.
Question 347
An ALB receives HTTPS traffic but private targets need encrypted traffic end to end. Which target connection is needed?
- Enable scoped ALB target-group stickiness with an appropriate duration.
- Use an HTTPS target group and compatible backend TLS listener.
- Create listener path-based routing rules with separate target groups.
- Use an ALB target-group deregistration delay with app-aware draining.
Explanation
Correct Answer
B:TLS at the ALB alone does not encrypt the ALB-to-target hop; HTTPS target protocol preserves that segment. Capture target-side connections and confirm TLS handshakes.
Incorrect Answers
A:Target-group stickiness may keep a client on one target, though externalized state is preferable for full resilience. Use an HTTPS target group and compatible backend TLS listener. Capture target-side connections and confirm TLS handshakes.
C:ALB listener rules select target groups by HTTP path without deploying a second load balancer. Use an HTTPS target group and compatible backend TLS listener. Capture target-side connections and confirm TLS handshakes.
D:Deregistration delay lets in-flight requests complete while new requests route elsewhere. Use an HTTPS target group and compatible backend TLS listener. Capture target-side connections and confirm TLS handshakes.
Question 348
A target is being removed for maintenance and active requests must finish gracefully. What setting helps?
- Deploy targets across at least two Availability Zones behind an Application Load Balancer.
- Use an ALB target-group deregistration delay with app-aware draining.
- Use an HTTPS target group and compatible backend TLS listener.
- Enable scoped ALB target-group stickiness with an appropriate duration.
Explanation
Correct Answer
B:Deregistration delay lets in-flight requests complete while new requests route elsewhere. Deregister a busy target and inspect completion and new-request placement.
Incorrect Answers
A:An ALB routes new requests to healthy targets in surviving enabled zones. Use an ALB target-group deregistration delay with app-aware draining. Deregister a busy target and inspect completion and new-request placement.
C:TLS at the ALB alone does not encrypt the ALB-to-target hop; HTTPS target protocol preserves that segment. Use an ALB target-group deregistration delay with app-aware draining. Deregister a busy target and inspect completion and new-request placement.
D:Target-group stickiness may keep a client on one target, though externalized state is preferable for full resilience. Use an ALB target-group deregistration delay with app-aware draining. Deregister a busy target and inspect completion and new-request placement.
Question 349
A single ALB serves two services using example.com/pay and example.com/catalog. How should requests be directed?
- Deploy targets across at least two Availability Zones behind an Application Load Balancer.
- Use an ALB target-group deregistration delay with app-aware draining.
- Create listener path-based routing rules with separate target groups.
- Use an HTTPS target group and compatible backend TLS listener.
Explanation
Correct Answer
C:ALB listener rules select target groups by HTTP path without deploying a second load balancer. Invoke each path and confirm the intended target group handles it.
Incorrect Answers
A:An ALB routes new requests to healthy targets in surviving enabled zones. Create listener path-based routing rules with separate target groups. Invoke each path and confirm the intended target group handles it.
B:Deregistration delay lets in-flight requests complete while new requests route elsewhere. Create listener path-based routing rules with separate target groups. Invoke each path and confirm the intended target group handles it.
D:TLS at the ALB alone does not encrypt the ALB-to-target hop; HTTPS target protocol preserves that segment. Create listener path-based routing rules with separate target groups. Invoke each path and confirm the intended target group handles it.
Question 350
Users require session affinity for a legacy component during a short migration, while moving toward stateless nodes. Which load balancer setting can help temporarily?
- Use an ALB target-group deregistration delay with app-aware draining.
- Deploy targets across at least two Availability Zones behind an Application Load Balancer.
- Enable scoped ALB target-group stickiness with an appropriate duration.
- Create listener path-based routing rules with separate target groups.
Explanation
Correct Answer
C:Target-group stickiness may keep a client on one target, though externalized state is preferable for full resilience. Make repeated requests with stickiness cookies and observe target selection.
Incorrect Answers
A:Deregistration delay lets in-flight requests complete while new requests route elsewhere. Enable scoped ALB target-group stickiness with an appropriate duration. Make repeated requests with stickiness cookies and observe target selection.
B:An ALB routes new requests to healthy targets in surviving enabled zones. Target-group stickiness may keep a client on one target, though externalized state is preferable for full resilience.
D:ALB listener rules select target groups by HTTP path without deploying a second load balancer. Enable scoped ALB target-group stickiness with an appropriate duration. Make repeated requests with stickiness cookies and observe target selection.