Study guide
Technical reference and lesson notes
Purpose of This Lesson
This lesson introduces a broad group of AWS services spanning web application development, mobile backends, machine learning, and cost management. These topics are grouped together because they appear in certification scenarios but generally represent a smaller portion of the exam than core areas such as networking, security, storage, compute, and resilience.
The required objective is breadth rather than exhaustive implementation knowledge. You should be able to recognize what these service categories are designed to accomplish, identify their common business use cases, and select an appropriate service when a scenario clearly points to one.
Key Concepts
Learn the service purpose first
For lower-frequency services, prioritize the following questions:
- What business problem does the service solve?
- Is it intended for web applications, mobile applications, machine learning, or financial visibility?
- What type of input does it accept and what output does it produce?
- Does it reduce the need to build or operate infrastructure directly?
- What security, integration, scalability, or operational requirement does it address?
Use case recognition is more valuable than memorizing features
Certification scenarios often describe a requirement in business or architectural terms rather than naming the service directly. For example, a question may ask for a managed capability that accelerates application development, provides mobile application functionality, analyzes data with machine learning, or improves visibility into cloud expenditure.
The key skill is mapping the requirement to the correct AWS service category without confusing adjacent offerings.
These services still fit into broader architecture principles
Even when a question focuses on a specialized service, evaluate it using the same architectural principles used elsewhere in AWS:
- Security: identity, access control, encryption, and data protection
- Reliability: fault tolerance, service limits, backup, and recovery requirements
- Performance: latency, throughput, scaling, and regional placement
- Cost optimization: consumption model, operational overhead, and unnecessary capacity
- Operational excellence: monitoring, automation, governance, and maintainability
Exam-Relevant Takeaways
- Expect breadth across web, mobile, machine learning, and cost management services rather than deep implementation detail for every service.
- Know the primary purpose and typical use case of each service covered in the wider section.
- Read the scenario for the business outcome first; do not choose a service merely because it is familiar.
- Distinguish managed application capabilities from services that require you to design and operate the underlying infrastructure.
- Consider security, integration, scalability, and cost even when the question emphasizes a specialized feature.
- Avoid overstudying obscure configuration details unless the question specifically introduces a limitation, integration, or architectural tradeoff.
Architecture Decision Guide
| Scenario clue | What to determine | Decision approach |
|---|---|---|
| The requirement involves building or enhancing a web application | Application platform, frontend/backend needs, integration, and scale | Select the service that best matches the required level of managed application functionality |
| The requirement involves a mobile application | Authentication, APIs, synchronization, notifications, analytics, and backend integration | Look for a managed mobile-oriented capability instead of assembling unrelated infrastructure without a stated need |
| The requirement involves machine learning | Type of data, inference or training needs, model ownership, and operational skill available | Choose the service based on whether the organization needs a prebuilt capability, a managed development workflow, or greater control over models and infrastructure |
| The requirement involves cloud spending | Visibility, allocation, forecasting, budgets, optimization, or governance | Identify whether the primary need is reporting, alerting, analysis, or cost reduction |
| The scenario mentions a specialized service but provides few technical details | The intended business outcome | Prefer the service whose primary purpose most directly matches that outcome |
Common Exam Traps
- Choosing the most complex service: A fully customizable solution may be inappropriate when the requirement can be met with a managed capability.
- Confusing service categories: Web, mobile, machine learning, and cost tools may all support application teams, but they solve different primary problems.
- Focusing on implementation before the requirement: Do not begin by comparing minor features. First identify the desired business result.
- Ignoring operational overhead: Two solutions may provide similar functionality while differing significantly in infrastructure management, scaling, and maintenance effort.
- Assuming specialized means uncommon or irrelevant: A service may have a narrow purpose but still be the best answer when the scenario explicitly matches that purpose.
- Overlooking the main exam domains: Specialized services should be evaluated alongside security, reliability, performance, and cost—not in isolation.
Real-World Engineer Notes
A practical study and design strategy is to maintain a service-selection matrix. For every specialized AWS service, record:
- Its primary purpose.
- The most common business problem it solves.
- The services it is commonly confused with.
- Its major security and integration considerations.
- The operational burden it removes or introduces.
This approach is more useful than memorizing isolated product descriptions. In a real architecture, these services are usually components of a larger design involving identity, networking, data stores, observability, deployment automation, and cost controls.
Quick Reference Summary
- This topic group is broad and relatively light compared with AWS core architecture domains.
- Focus on service purpose, business use cases, and high-level capabilities.
- Use scenario requirements—not service familiarity—as the basis for selection.
- Apply the standard AWS design lenses: security, reliability, performance, operations, and cost.
- Study enough detail to recognize the correct service and reject plausible but mismatched alternatives.
Flashcards
1. What is the primary study objective for this service group?
Recognize each service’s purpose, common use cases, and basic capabilities rather than memorizing exhaustive implementation details.
2. Why are web, mobile, machine learning, and cost management services grouped together?
They span different AWS categories but generally appear less frequently than the core architecture domains and can be covered at a lighter level.
3. What should be identified before comparing AWS service features?
The business outcome and the specific requirement expressed by the scenario.
4. What architectural principles still apply to specialized AWS services?
Security, reliability, performance, cost optimization, and operational excellence.
5. What is a common mistake when selecting a specialized service?
Choosing a familiar or highly customizable service instead of the managed service that directly matches the requirement.
6. What should you know about a service for a scenario-based exam question?
Its primary purpose, common use cases, basic capabilities, and the types of requirements that distinguish it from related services.
7. Why should operational overhead be considered during service selection?
Managed services can reduce infrastructure provisioning, scaling, and maintenance responsibilities, which may be central to the scenario.
8. How can a service-selection matrix improve exam preparation?
It organizes each service by purpose, use case, competing services, and operational considerations, making requirement-to-service mapping easier.
Practice Questions
Question 1
A study plan has limited time remaining. An architect has already covered IAM, VPC networking, storage, compute, databases, resilience, and monitoring. Which approach is most appropriate for the web, mobile, machine learning, and cost management topics?
A. Memorize every API operation and configuration option for every service.
B. Learn the primary purpose, common use cases, and high-level capabilities of the services.
C. Skip the topics because they are not part of AWS architecture.
D. Focus only on pricing calculations.
Correct answer: B
The appropriate objective is broad service recognition and use-case understanding. These topics still matter, but they generally do not require the same depth as core architecture domains in this lesson.
Question 2
A scenario names a specialized AWS service but provides only a business requirement and a few architectural constraints. What should the architect do first?
A. Select the named service immediately.
B. Compare every available AWS service in the same category.
C. Identify the required business outcome and map it to the service’s primary purpose.
D. Choose the service with the greatest number of features.
Correct answer: C
The service name or category should be evaluated against the actual requirement. Exam questions reward selecting the service that directly solves the stated problem, not the one with the largest feature set.
Question 3
A team is evaluating a managed capability for a specialized application requirement. One option provides extensive customization but requires the team to operate more infrastructure. Another provides the required capability with less operational effort. No requirement calls for custom infrastructure or advanced control. Which option is generally preferable?
A. The option with the most customization.
B. The option with the greatest number of configuration settings.
C. The managed option that satisfies the requirement with less operational overhead.
D. A self-managed solution running on general-purpose compute.
Correct answer: C
When the requirements do not justify additional control, a managed capability is usually preferable because it can reduce infrastructure administration and maintenance.