Home / SAA-C03 / Objective 2.1

Domain 2: Design Resilient Architectures · 26% of the exam · Full exam outline

2.1 Design scalable and loosely coupled architectures

What this objective covers · 13% of the exam

API creation and management (for example, Amazon API Gateway, REST API); AWS managed services with appropriate use cases (for example, AWS Transfer Family, Amazon SQS, AWS Secrets Manager); Caching strategies; Design principles for microservices (for example, stateless workloads compared with stateful workloads); Event-driven architectures; Horizontal scaling and vertical scaling; How to appropriately use edge accelerators (for example, content delivery network [CDN]); How to migrate applications into containers; Load balancing concepts (for example, Application Load Balancer [ALB]); Multi-tier architectures; Queuing and messaging concepts (for example, publish/subscribe); Serverless technologies and patterns (for example, AWS Fargate, AWS Lambda); Storage types with associated characteristics (for example, object, file, block); The orchestration of containers (for example, Amazon ECS, Amazon EKS); When to use read replicas; Workflow orchestration (for example, AWS Step Functions); Designing event-driven, microservice, and/or multi-tier architectures based on requirements; Determining scaling strategies for components used in an architecture design; Determining the AWS services required to achieve loose coupling based on requirements; Determining when to use containers; Determining when to use serverless technologies and patterns; Recommending appropriate compute, storage, networking, and database technologies based on requirements; Using purpose-built AWS services for workloads

Practice questions

Question 1easy

A broadcaster's migration team will move several hundred Java services off on-premises virtual machines. During the move, each service is packaged into a container image and run on Amazon ECS, and its source code is left untouched. Which of the 7 Rs describes this plan?

Included in Sample: sample every domain.See plans

Choose an answer to check it. Afterward, select any option to review its explanation.

Repurchase also ends with something new running, but the new thing is a different version or product that replaces the application. The broadcaster keeps its own Java services and changes only how they run.

Retire is for applications you want to decommission or archive, so their servers can be shut down. The team is keeping every service in use and moving it, so nothing is being retired.

Replatform moves an application to the cloud while introducing some level of optimization. Migrating virtual machines into containers without making any code changes is one of its listed use cases, which is what the team is doing.

Retain fits applications that stay in the source environment or are not ready to migrate. These services are leaving the on-premises virtual machines for Amazon ECS, so they are not being kept where they are.

Question 2easy

A retailer runs separate services for /cart and /search and wants one public endpoint that sends each request to a different target group based on its URL path. Which load balancer fits?

Included in Sample: sample every domain.See plans

Choose an answer to check it. Afterward, select any option to review its explanation.

An ALB works at layer 7 and evaluates listener rules against the request content, so a path condition can forward /cart and /search to different target groups.

Listeners are defined by protocol and port, not URL path, and Classic Load Balancers are the previous generation that AWS recommends migrating away from.

Gateway Load Balancers exist to insert virtual appliances such as firewalls into the traffic path; they do not do HTTP path routing for application services.

An NLB is the right choice for layer 4 TCP/UDP traffic at very high rates, but at layer 4 it never looks at URL paths, so it cannot route on /cart versus /search.