Situation and constraints
Lumen Market has outgrown a single application process. When a customer places an order, the application must ask a worker to generate an invoice, notify several interested systems, and react to selected business events. Analysts also want to query sales files and publish dashboards. A separate team wants to build a demand-forecasting model, while customer service needs a managed contact center.
Management calls all of this “data processing” and asks for one AWS service. The phrase is too broad. Moving a message safely between application components is not the same as broadcasting a notification. Routing events is not the same as querying files with SQL. A dashboard is not a machine-learning training platform, and a contact center is not an event bus.
The Cloud Practitioner task is to recognize the category and select a plausible service from the business need. Lumen is not designing an event schema, analytics lakehouse, or ML pipeline in this lesson.
The decision to make
Lumen should split the work into three capability groups.
Application integration connects software components without requiring them to do everything in one synchronous request. Amazon Simple Queue Service (Amazon SQS) provides queues, Amazon Simple Notification Service (Amazon SNS) publishes messages to subscribers, and Amazon EventBridge routes matching events from sources to targets.
Analytics and machine learning turn stored data into answers or predictive capabilities. Amazon Athena runs interactive SQL queries against data in Amazon S3. Amazon QuickSight—now presented in current AWS documentation as Amazon Quick Sight within Amazon Quick—provides business intelligence, dashboards, and visualizations. Amazon SageMaker AI provides managed tools for building, training, and deploying machine-learning models.
Business applications solve a business function directly. Amazon Connect is the exam-guide name for AWS's contact-center service; current AWS documentation describes the legacy contact-center product as Amazon Connect Customer within a broader Amazon Connect portfolio.
A practical mental model
Imagine Lumen's company as an office.
An SQS queue is an inbox where each task waits until a worker retrieves and processes it. SNS is a loudspeaker that publishes one message to multiple subscribed destinations. EventBridge is a switchboard with rules that examine events and route matching events to targets.
Athena is an analyst who can use SQL to ask ad-hoc questions of files already stored in S3. QuickSight is the presentation team that turns data into dashboards and visual explanations. SageMaker AI is a managed workshop for data scientists and developers to build, train, and deploy ML models. Amazon Connect is the customer-service floor that handles interactions and routes customers to agents.
The analogy prevents a common mistake: choosing based on the word “event” or “data” alone. The desired outcome—buffer work, fan out a message, route events, query, visualize, train a model, or operate a contact center—determines the category.
Application integration choices
When the order API must hand one invoice job to a worker and tolerate the worker being temporarily unavailable, Amazon SQS is the strongest starting point. The queue decouples the producer from the consumer and retains a message until it is processed according to queue behavior. SQS is pull-based from the consumer's perspective and supports worker-style buffering.
When Lumen must publish one promotion notice to several subscribed endpoints, Amazon SNS fits the fan-out and notification model. A topic can deliver published messages to multiple subscribers. SNS is not a work backlog that one worker claims in the same way as an SQS queue.
When systems emit business or AWS service events and Lumen wants rules to route matching events to different targets, Amazon EventBridge fits. An event bus receives events, and rules match patterns or schedules to send events onward. It is strong for event routing and integration across AWS services, custom applications, and supported partners.
These services can work together. SNS can fan out to SQS queues, giving multiple consumer groups their own buffered copy. EventBridge can route a matching event to a target. At this level, the key is the primary intent, not an exhaustive architecture comparison. Use the shared SQS versus SNS versus EventBridge reference for more depth.
| Need | Service signal |
|---|---|
| Buffer a task for a worker | Amazon SQS queue |
| Publish one message to multiple subscribers | Amazon SNS topic |
| Route matching events from sources to targets | Amazon EventBridge event bus and rules |
Analytics, AI, and business outcomes
Lumen stores daily sales exports in S3. Analysts who know SQL need occasional answers without operating a database server. Amazon Athena is a serverless interactive query service that can analyze structured, semi-structured, and unstructured data in S3 using SQL. It queries data; it does not primarily build executive dashboards.
Business users want recurring visual reports and interactive dashboards. Amazon Quick Sight, the current name for the business-intelligence capability that evolved from Amazon QuickSight, connects to data sources and produces visualizations and dashboards. The curriculum preserves the manifest label Amazon QuickSight because the current CLF-C02 in-scope appendix writes “Amazon Quick Sight” and existing Arcflow references use the earlier product spelling. The underlying exam distinction remains business intelligence and visualization.
The forecasting team wants to build and train a machine-learning model from historical demand. Amazon SageMaker AI is a managed ML service for building, training, and deploying models. It is not the automatic answer to every use of the word “AI,” and Cloud Practitioner learners are not expected to design training infrastructure.
Customer service wants voice and chat interactions, intelligent routing, queues for agents, and contact-center operations. Amazon Connect identifies the business-application category. Current AWS documentation calls the legacy contact-center product Amazon Connect Customer. This is different from connecting networks or integrating application messages; the word “Connect” names a business service here.
Recommended reasoning
Lumen should translate each request into a verb.
- Buffer an invoice task: choose SQS.
- Broadcast a notification: choose SNS.
- Route matching events: choose EventBridge.
- Query S3 data with SQL: choose Athena.
- Visualize data for business users: choose QuickSight / Quick Sight.
- Build, train, and deploy an ML model: choose SageMaker AI.
- Operate customer communications and a contact center: choose Amazon Connect.
This verb-first approach is safer than memorizing categories in isolation. It also makes plausible alternatives easier to reject. Athena can return query results but is not the dashboard layer. Quick Sight can visualize and analyze data but is not the managed model-development platform. SNS delivers messages but is not a contact center for human agents.
Lumen should also avoid assuming these managed services remove customer responsibility. It still controls identities, data access, configuration, retention, and how its application responds to errors or duplicate delivery behavior.
Where the manifest services fit
Amazon SQS, Amazon SNS, and Amazon EventBridge are application integration services with different message movement models. Their shared comparison reference and individual EventBridge reference provide deeper mechanics.
Amazon Athena is serverless interactive SQL analysis for data in S3. Amazon QuickSight is the manifest's stable label for the business-intelligence and visualization capability now documented as Amazon Quick Sight inside Amazon Quick. Use Arcflow's existing Athena and QuickSight references for their established service boundaries.
Amazon SageMaker AI is managed machine learning for model development, training, and deployment. Amazon Connect is the manifest and exam-guide label for the contact-center business application, currently documented as Amazon Connect Customer.
Common exam confusion
- SQS versus SNS: SQS buffers messages for consumers; SNS publishes messages to subscribers.
- SNS versus EventBridge: SNS centers on topic publication and fan-out. EventBridge centers on matching and routing events with rules.
- Athena versus Quick Sight: Athena queries data, especially in S3, using SQL. Quick Sight creates business-intelligence analyses, dashboards, and visualizations.
- Analytics versus machine learning: Analytics explains or explores data. ML trains models to recognize patterns or make predictions.
- SageMaker AI versus every AI service: SageMaker AI supports ML model workflows; purpose-built AI services may solve narrower tasks.
- Amazon Connect versus network connectivity: Amazon Connect is a business application for customer communications, not a VPC connection service.
- Product rename versus changed exam intent: Current AWS names have evolved, but the decision signals—visualize business data and operate a contact center—remain stable.
Recall prompts
- Which service would buffer an invoice task until a worker can process it?
- Which service would publish one message to several subscribers?
- What requirement points toward EventBridge rather than SQS?
- How do Athena and Quick Sight serve different analytics needs?
- What work does SageMaker AI support?
- Which business problem does Amazon Connect Customer address?
- Why is the desired verb a useful service-selection clue?
Summary
Lumen should select services by the capability it needs. SQS buffers work, SNS fans out published messages, and EventBridge routes matching events. Athena queries S3 data with SQL, Quick Sight provides business intelligence and dashboards, and SageMaker AI supports managed ML model workflows. Amazon Connect serves the contact-center business function.
Current AWS branding has changed around QuickSight and Amazon Connect, while the CLF-C02 guide and curriculum manifest retain their exam-facing labels. That naming drift does not change the foundational reasoning: identify the category and outcome before choosing a service.
Official references: CLF-C02 Domain 3, Amazon SQS, Amazon SNS, Amazon EventBridge, Amazon Athena, Amazon Quick, Amazon SageMaker AI, and Amazon Connect Customer.