Amazon Web Services SAA-C03 Exam With Confidence Using Practice Dumps

Among the listed choices, the best solution is to place an AWS Lambda function in the same VPC and use it as the EventBridge target. EventBridge natively supports Lambda as a target, and a Lambda function that runs in the VPC can call the private API without exposing that API publicly. The internet-facing ALB and NLB options violate the requirement to avoid public IP exposure. The direct-target option is also not expressed correctly for a plain private API endpoint, because modern direct private API targeting in EventBridge requiresconnections and VPC Lattice resource configurations, not simply naming a private VPC endpoint as a raw target. Therefore, Lambda as the bridge component is the correct answer from the provided choices. (AWS Documentation)

============

The best answer ismessage batching. AWS documentation explains that SQS batch actions let applications send, receive, or delete up to 10 messages at a time. AWS also notes that batching can be combined with horizontal scaling to improve throughput with fewer requests and connections. That makes batching the most relevant feature for handling sudden traffic increases efficiently. FIFO queues address strict ordering and deduplication, visibility timeout controls how long a received message stays hidden from other consumers, and long polling reduces empty responses and unnecessary polling cost. None of those features directly improve throughput as effectively as batching for traffic spikes.

============

Amazon SQS is the AWS-recommended service for handling decoupled, scalable, ordered, durable message ingestion with potentially large workloads. It supports payloads up to 256 KB directly and up to several MB using S3-backed large-payload extensions.

Lambda functions can process messages from SQS with automatic scaling. ECS with the Fargate launch type provides a serverless container platform for the frontend, scaling based on demand without managing servers.

SNS (Options B and D) is not a queue, does not provide durable message buffering, and is not appropriate for variable, bursty workloads that may exceed backend throughput. Lambda@Edge (Options A and D) is unsuitable for backend order processing because it runs at CloudFront edge locations with strict limitations.