Which service combination processes hundreds of simultaneous user requests efficiently?
A company needs to simultaneously process hundreds of requests from different users. Which combination of AWS services should the company use to build an operationally efficient solution?
Community Insight
Tests whether you can match a workload pattern (bursty, high-volume, decoupled request processing) to serverless services — the trap is picking data-orchestration or analytics tools that do not perform request processing at all.
The question asks which AWS service pairing delivers an operationally efficient way to process hundreds of concurrent user requests. Amazon SQS plus AWS Lambda is correct because the queue decouples and buffers incoming requests while Lambda scales processing elastically without server management.
Option B (AWS Data Pipeline with Amazon EC2) attracts learners who equate 'processing data' with 'processing requests'; Data Pipeline orchestrates batch data movement between storage and compute, not high-volume concurrent request handling, and EC2 requires capacity management that undercuts operational efficiency.
Community Discussion (104 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Amazon SQS is a fully managed queue that absorbs hundreds of simultaneous user requests, buffering them so producers and consumers stay decoupled and no downstream component is overwhelmed. AWS Lambda then polls the queue and scales concurrency automatically, so the processing tier grows and shrinks with the actual workload with no servers to provision. Together they deliver the operational efficiency the question asks for: no infrastructure management, automatic scaling, and built-in durability and retry behavior. That directly matches "simultaneously process hundreds of requests from different users."Why the Other Options Are Wrong
AWS Data Pipeline (option B) is an orchestration service for scheduled, batch-oriented data movement between AWS compute/storage services and on-premises sources — as AnnieApples put it, it "moves data between AWS compute / storage services and on prem data," which is unrelated to fan-out request handling, and EC2 instances would reintroduce the capacity planning the scenario is trying to avoid. Amazon Kinesis with Athena (option C) is a streaming-ingest plus interactive query pattern suited to analytics on streaming data, not per-request transactional processing. AWS Amplify with AWS AppSync (option D) targets building web and mobile front ends with managed GraphQL APIs; AppSync resolvers could invoke compute, but the pairing provides no queue-based buffering or elastic batch consumers for hundreds of concurrent requests, and Amplify is a front-end hosting and tooling service.Community Comment Notes
Community sentiment overwhelmingly favors option A, with multiple learners independently walking through the decoupling and auto-scaling rationale — AnnieApples dismisses Data Pipeline as irrelevant, and ArkieKT explains that SQS "acts as a buffer, storing incoming requests and decoupling the request generation from the actual processing." Proctored_Expert and man5484 add scalability and reliability points, while cqrm3n stresses asynchronous communication and automatic scaling. Several voters, including Uchendum, simply state "SQS helps with the question," and one commenter (Jaccky) questions why the item is considered controversial at all — a hint that the intended pairing is straightforward once Data Pipeline is ruled out.Note: the source key for this item is unmarked, so this analysis is based on the question wording and the AWS service definitions above.
Official Reference
Exam Strategy
When a stem stresses high concurrency plus operational efficiency, look for fully managed, auto-scaling services and eliminate any option containing a batch-orchestration or analytics service (Data Pipeline, Athena). Ask yourself whether each service in the pair actually performs request processing — one irrelevant component invalidates the whole combination.
Frequently Asked Questions
Why is AWS Data Pipeline not the right choice for processing hundreds of requests?
Data Pipeline orchestrates scheduled batch data movement between storage and compute services, not high-volume concurrent request handling, and pairing it with EC2 adds server management overhead.
Does Lambda scale automatically when messages arrive in an SQS queue?
Yes. Lambda polls the queue and scales concurrency with the backlog, so hundreds of queued requests are processed in parallel without provisioning capacity.
Related Analysis
Practice All CLF-C02 Questions
Access 120 questions with complete answers and detailed explanations.
View Full CLF-C02 Practice Test →