5 exercises — loose coupling, stateless design, fault tolerance, RPO/RTO disaster recovery, and the shared responsibility model. Architecture vocabulary for Solutions Architect exams.
0 / 18 completed
1 / 18
A solutions architect describes a design as using loose coupling. What does loose coupling mean in a cloud architecture?
Loose coupling is one of the five AWS Well-Architected Framework pillars' most-tested concepts. A loosely coupled architecture:
• Services communicate through APIs, message queues (SQS), or event buses (EventBridge) — not directly • A failure in Service A doesn't automatically fail Service B • Services can be scaled, deployed, or updated independently • Contrast with tight coupling: services call each other synchronously, share databases, or rely on shared in-process state
Loose coupling patterns on exams: • Web tier → SQS queue → processing tier (classic decoupling) • API Gateway → Lambda (each Lambda is independent) • SNS fan-out → multiple SQS queues (one publisher, many consumers) • EventBridge rules routing domain events to different consumers
Anti-patterns the exam tests against: • Tight coupling: Service A calls Service B's private database directly • Synchronous chains: A calls B which calls C which calls D — one failure fails all
2 / 18
A question asks which architecture is stateless. An architect says: "Our API servers are stateless." What does this mean — and why does it matter for cloud scalability?
Stateless servers are a foundational cloud architecture concept. A stateless server:
• Does not store user session data or application state in local memory or local disk • Every request is self-contained — any server in the fleet can handle any request • Session data lives in ElastiCache (Redis/Memcached) or DynamoDB • File uploads are stored in S3, not local disk
Why it matters for scalability: If your servers store session state locally, users are "stuck" to the same server (sticky sessions). You can't freely add or remove instances because the state moves with the instance.
With stateless servers + external state store: → Auto Scaling can add/remove instances freely → All instances are identical and interchangeable → No sticky sessions required at the load balancer
Exam signal: "stateless" → use external cache/database for state → enables horizontal scaling "Sticky sessions" → the app is currently stateful → architecture improvement question → refactor to stateless + ElastiCache
3 / 18
A company needs an architecture that continues to function even when components fail. The exam calls this property _____.
Fault tolerance means the system continues operating — possibly at reduced capacity — when one or more components fail, without any intervention or downtime.
Distinguish these related terms:
• Fault tolerant — the system keeps running through failures (zero downtime) • Highly available — the system recovers quickly from failures (minimal downtime, often through automatic failover) • Resilient — the system can withstand disruptions and recover (broader concept covering both) • Elastic — the system automatically scales resources to match demand
Fault tolerance patterns: • Multi-AZ with synchronous replication → database failover in seconds • Read replicas for database read traffic • Multi-region active-active for extreme fault tolerance • S3 Cross-Region Replication • Route 53 health checks with failover routing
On the exam: "Continue operating even if one component fails" → fault tolerance "Recover quickly from failures" → high availability "Automatically adjust capacity" → elasticity "Design for failure" → AWS principle: assume components will fail, architect accordingly
4 / 18
An AWS exam scenario says: "The application must achieve an RPO of 1 hour and RTO of 4 hours." What does this mean for the disaster recovery design?
RPO and RTO are the two fundamental disaster recovery metrics. They appear in every disaster recovery question on all major cloud certification exams.
RPO (Recovery Point Objective): The maximum acceptable amount of data loss measured in time. "RPO = 1 hour" → after a disaster, you can tolerate losing at most 1 hour of data. → Requires backups or replication at least every hour.
RTO (Recovery Time Objective): The maximum acceptable time the system can be down after a disaster. "RTO = 4 hours" → the system must be back online within 4 hours of the failure. → Determines your DR strategy: backup restore (cheaper, longer RTO) vs. warm standby vs. hot standby.
DR strategy tiers (cheapest → most expensive, longest → shortest RTO/RPO): 1. Backup and restore — hours RTO, highest RPO 2. Pilot light — core services always on, scale up on disaster 3. Warm standby — scaled-down copy always running 4. Multi-site active-active — near-zero RTO/RPO, highest cost
Lower RPO/RTO = more expensive. The exam may ask: "which DR strategy meets an RPO of 15 minutes at lowest cost?" → warm standby.
5 / 18
A senior architect says: "We follow the shared responsibility model." A junior engineer asks: "Who is responsible for patching the operating system on our EC2 instances?"
The AWS Shared Responsibility Model is tested on every AWS certification. The key principle:
AWS is responsible for: "Security OF the cloud" • Physical hardware, facilities, power • Network infrastructure • Hypervisor • Managed service software (e.g. the RDS database engine patches — AWS patches those)
Customer is responsible for: "Security IN the cloud" • EC2 OS patches • Application code • Data encryption (at rest and in transit) • IAM user and role management • Security Group and NACL configuration • Network traffic protection
The model shifts based on service type: • EC2 (IaaS) → customer manages OS and above • RDS (PaaS) → AWS manages OS and DB engine; customer manages data and access • Lambda (serverless) → AWS manages runtime; customer manages code and IAM • S3 (managed storage) → AWS manages infrastructure; customer manages data, access policies, encryption choice
Exam trick: questions about "who patches the OS" for managed services (RDS, Elastic Beanstalk) → AWS. For EC2 → customer.
6 / 18
// PR Description
```diff
--- a/README.md
+++ b/README.md
@@ -12,4 +12,4 @@
This service utilizes a serverless architecture leveraging AWS Lambda and API Gateway.
The backend employs DynamoDB for persistent data storage and SQS for asynchronous task processing.
We're aiming for high availability with automated scaling.
```
The team lead comments on this PR: 'I'm seeing a lot of mentions of 'serverless'. Can you elaborate on why we chose this architecture and what benefits it offers beyond just cost savings?' Which of the following best describes the core concept being communicated?
This question tests understanding of the term 'serverless' in an architectural context. The correct answer highlights that serverless refers to abstracting away infrastructure management – it doesn't mean there are no servers involved; rather, AWS manages them for you. Misconceptions often arise from thinking 'serverless' means a complete absence of control, or a lack of dependency on external services; the key is the managed aspect.
7 / 18
The team lead comments on this PR: 'I'm seeing a lot of mentions of 'serverless'. Can you elaborate on why we chose this architecture and what benefits it offers beyond just cost savings?' Which of the following best describes the core concept being communicated?
Option A: Serverless architectures are inherently more secure than traditional server-based deployments. Option B: Serverless architectures utilize containerization technology for efficient resource allocation. Option C: Serverless architectures allow developers to focus on code without managing underlying servers, abstracting away operational concerns and promoting agility. Option D: Serverless architectures always result in the lowest possible latency due to their distributed nature.
The team lead is probing for a deeper understanding of 'serverless' beyond just cost. While serverless *can* offer cost savings, the primary benefit being communicated here is the abstraction of server management—this is what makes it 'serverless'. Option A is incorrect as security is still a shared responsibility. Option B is partially correct (serverless often uses containers), but misses the core point of reduced operational overhead. Option D is misleading; while latency can be minimized, it's not an inherent characteristic of serverless.
8 / 18
// PR Description
```diff
--- a/README.md
+++ b/README.md
@@ -12,4 +12,4 @@
This service utilizes a serverless architecture leveraging AWS Lambda and API Gateway.
The backend employs DynamoDB for persistent data storage and SQS for asynchronous task processing.
We're aiming for high availability with automated scaling.
```
The team lead comments on this PR: 'I'm seeing a lot of mentions of 'serverless'. Can you elaborate on why we chose this architecture and what benefits it offers beyond just cost savings?' Which of the following best describes the core concept being communicated?
This question tests understanding of the term 'serverless' in an architectural context. The correct answer highlights that serverless refers to abstracting away infrastructure management – it doesn't mean there are no servers involved; rather, AWS manages them for you. Misconceptions often arise from thinking 'serverless' means a complete absence of control, or a lack of dependency on external services; the key is the managed aspect.
9 / 18
The team lead comments on this PR: 'I'm seeing a lot of mentions of 'serverless'. Can you elaborate on why we chose this architecture and what benefits it offers beyond just cost savings?' Which of the following best describes the core concept being communicated?
Option A: Serverless architectures are inherently more secure than traditional server-based deployments. Option B: Serverless architectures utilize containerization technology for efficient resource allocation. Option C: Serverless architectures allow developers to focus on code without managing underlying servers, abstracting away operational concerns and promoting agility. Option D: Serverless architectures always result in the lowest possible latency due to their distributed nature.
The team lead is probing for a deeper understanding of 'serverless' beyond just cost. While serverless *can* offer cost savings, the primary benefit being communicated here is the abstraction of server management—this is what makes it 'serverless'. Option A is incorrect as security is still a shared responsibility. Option B is partially correct (serverless often uses containers), but misses the core point of reduced operational overhead. Option D is misleading; while latency can be minimized, it's not an inherent characteristic of serverless.
10 / 18
// PR Description
```diff
--- a/README.md
+++ b/README.md
@@ -12,4 +12,4 @@
This service utilizes a serverless architecture leveraging AWS Lambda and API Gateway.
The backend employs DynamoDB for persistent data storage and SQS for asynchronous task processing.
We're aiming for high availability with automated scaling.
```
The team lead comments on this PR: 'I'm seeing a lot of mentions of 'serverless'. Can you elaborate on why we chose this architecture and what benefits it offers beyond just cost savings?' Which of the following best describes the core concept being communicated?
This question tests understanding of the term 'serverless' in an architectural context. The correct answer highlights that serverless refers to abstracting away infrastructure management – it doesn't mean there are no servers involved; rather, AWS manages them for you. Misconceptions often arise from thinking 'serverless' means a complete absence of control, or a lack of dependency on external services; the key is the managed aspect.
11 / 18
The team lead comments on this PR: 'I'm seeing a lot of mentions of 'serverless'. Can you elaborate on why we chose this architecture and what benefits it offers beyond just cost savings?' Which of the following best describes the core concept being communicated?
Option A: Serverless architectures are inherently more secure than traditional server-based deployments. Option B: Serverless architectures utilize containerization technology for efficient resource allocation. Option C: Serverless architectures allow developers to focus on code without managing underlying servers, abstracting away operational concerns and promoting agility. Option D: Serverless architectures always result in the lowest possible latency due to their distributed nature.
The team lead is probing for a deeper understanding of 'serverless' beyond just cost. While serverless *can* offer cost savings, the primary benefit being communicated here is the abstraction of server management—this is what makes it 'serverless'. Option A is incorrect as security is still a shared responsibility. Option B is partially correct (serverless often uses containers), but misses the core point of reduced operational overhead. Option D is misleading; while latency can be minimized, it's not an inherent characteristic of serverless.
12 / 18
// PR Description
```diff
--- a/README.md
+++ b/README.md
@@ -12,4 +12,4 @@
This service utilizes a serverless architecture leveraging AWS Lambda and API Gateway.
The backend employs DynamoDB for persistent data storage and SQS for asynchronous task processing.
We're aiming for high availability with automated scaling.
```
The team lead comments on this PR: 'I'm seeing a lot of mentions of 'serverless'. Can you elaborate on why we chose this architecture and what benefits it offers beyond just cost savings?' Which of the following best describes the core concept being communicated?
This question tests understanding of the term 'serverless' in an architectural context. The correct answer highlights that serverless refers to abstracting away infrastructure management – it doesn't mean there are no servers involved; rather, AWS manages them for you. Misconceptions often arise from thinking 'serverless' means a complete absence of control, or a lack of dependency on external services; the key is the managed aspect.
13 / 18
The team lead comments on this PR: 'I'm seeing a lot of mentions of 'serverless'. Can you elaborate on why we chose this architecture and what benefits it offers beyond just cost savings?' Which of the following best describes the core concept being communicated?
Option A: Serverless architectures are inherently more secure than traditional server-based deployments. Option B: Serverless architectures utilize containerization technology for efficient resource allocation. Option C: Serverless architectures allow developers to focus on code without managing underlying servers, abstracting away operational concerns and promoting agility. Option D: Serverless architectures always result in the lowest possible latency due to their distributed nature.
The team lead is probing for a deeper understanding of 'serverless' beyond just cost. While serverless *can* offer cost savings, the primary benefit being communicated here is the abstraction of server management—this is what makes it 'serverless'. Option A is incorrect as security is still a shared responsibility. Option B is partially correct (serverless often uses containers), but misses the core point of reduced operational overhead. Option D is misleading; while latency can be minimized, it's not an inherent characteristic of serverless.
14 / 18
Sarah, a DevOps engineer, is explaining the architecture to Ben, a new team member. She says: 'We're using a microservices approach with each service running in its own container on Kubernetes.' Ben asks, 'What does that actually *mean* in terms of how we manage updates and deployments?' Which of the following best describes the core concept Sarah is conveying?
Microservices architecture means breaking down an application into smaller, independent services. Each service can be updated and deployed separately without needing to redeploy the entire system—a key benefit for agility and reducing downtime. Ben's question highlights the practical implication of this approach: independent deployability.
15 / 18
During a standup meeting, David, a senior architect, mentions 'event-driven architecture'. Maria, a junior developer, asks, 'Can you give me an example of why we might choose this over a more traditional request/response model?' Which of the following best illustrates the primary advantage of event-driven design?
Event-driven architecture focuses on asynchronous communication between services through events. This allows services to react to changes in real-time without directly waiting for a response from another service—crucial for building scalable and responsive systems. Maria's question probes the core benefit of this design pattern.
16 / 18
You are reviewing a PR that describes a new data processing pipeline built using AWS Glue and S3. The lead engineer comments: 'We're leveraging the serverless nature of these services to minimize operational overhead.' What does 'serverless' *specifically* refer to in this context?
When discussing serverless in the cloud, it refers to a model where the provider (AWS) handles all underlying infrastructure management – scaling, patching, and availability. This allows developers to focus solely on writing code without worrying about operational details. The engineer's comment highlights this key characteristic.
17 / 18
In a Slack channel discussing disaster recovery plans, Alex asks: 'What does an RTO of 30 minutes mean for our application?' Which of the following best describes the meaning of RTO (Recovery Time Objective)?
RTO (Recovery Time Objective) defines the *maximum* amount of time that a business or service can be unavailable after an outage. It's a critical metric in disaster recovery planning, setting expectations for how quickly operations must resume following an incident—not simply 'downtime'. Understanding RTO is crucial for designing effective DR strategies.
18 / 18
A cloud architect is explaining the benefits of a stateless application. John asks: 'If our web server doesn't store any session data, does that mean it's more scalable?' Which statement best explains why stateless applications are often easier to scale in the cloud?
Stateless applications do not retain client session information. This means each request is treated independently, allowing any instance of the application to handle a request – simplifying scaling. Scaling stateless systems involves simply adding more instances without worrying about state synchronization or data consistency across them.
What will I practice in "Cloud Architecture & Design Vocabulary — Certification Language Exercises"?
This is a Certification Prep exercise set. It walks through 18 scenario-based multiple-choice questions built around real usage of Certification Prep terminology that IT professionals encounter on the job.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to complete with no account, sign-up, or paywall.
How many questions are in this exercise?
This set contains 18 questions. Each one shows immediate feedback and a detailed explanation after you answer, so you learn the correct usage right away rather than waiting for a final score.
Do I need prior experience to complete this exercise?
No prior experience is required. Each question includes a full explanation covering the reasoning behind the correct answer, so the exercise itself teaches the Certification Prep vocabulary as you go.
Can I retry the exercise if I get questions wrong?
Yes — use the "Try again" button on the results screen to reset your answers and go through all the questions again. There is no limit on attempts.
Is my progress saved?
Your answers and score for the current session are tracked in the browser as you go. No account or login is needed, and there is nothing to install.
What if I don't understand a term used in a question?
Read the explanation shown after you answer each question — it breaks down the correct term in plain English with a real-world example. You can also check the site Glossary for quick definitions.
How is this different from reading a blog article on the topic?
Exercises like this one are interactive drills that test and reinforce specific vocabulary through multiple-choice questions, while blog articles explain concepts in prose. Practising here after reading builds active recall, not just passive recognition.
Where can I find more Certification Prep exercises?
See the Certification Prep exercises hub for the full set of related pages, or browse all exercise categories from the main Exercises index.
Can I use this exercise to prepare for a technical interview?
Yes — Certification Prep vocabulary comes up often in technical discussions and interviews. Pair this exercise with our dedicated Interview Preparation section for role-specific practice.