Home / SAA-C03 / Objective 3.2

Domain 3: Design High-Performing Architectures · 24% of the exam · Full exam outline

3.2 Design high-performing and elastic compute solutions

What this objective covers · 5% of the exam

AWS compute services with appropriate use cases (for example, AWS Batch, Amazon EMR, AWS Fargate); Distributed computing concepts supported by AWS global infrastructure and edge services; Queuing and messaging concepts (for example, publish/subscribe); Scalability capabilities with appropriate use cases (for example, Amazon EC2 Auto Scaling, AWS Auto Scaling); Serverless technologies and patterns (for example, AWS Lambda, Fargate); The orchestration of containers (for example, Amazon ECS, Amazon EKS); Decoupling workloads so that components can scale independently; Identifying metrics and conditions to perform scaling actions; Selecting the appropriate compute options and features (for example, EC2 instance types) to meet business requirements; Selecting the appropriate resource type and size (for example, the amount of Lambda memory) to meet business requirements

Practice questions

Question 1easy

An insurer is moving its claims system to AWS. The system's components exchange messages through an on-premises Apache ActiveMQ broker using JMS, and the team wants to migrate without rewriting that messaging code. Which service fits?

Included in Sample: sample every domain.See plans

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

Amazon MQ is the managed broker AWS recommends for migrating applications that depend on existing broker APIs such as JMS and on engines like ActiveMQ, so the components can keep their messaging code.

SNS is a managed publish-subscribe service, so it fits the idea of messaging. It delivers through topics to endpoints such as queues, functions and email, not as a JMS broker, so the existing code would still have to change.

SQS is AWS's queue for decoupling components and is recommended for new applications, so it is a natural first thought. Using it means moving the components onto its own web services API, which is the rewrite the team wants to avoid.

AWS Batch also manages work queues, which can make it sound related. It provisions compute for submitted batch jobs and does not provide a message broker for application components.

Question 2easy

A cloud gaming startup hosts game servers in a Region several hundred kilometers from a large metropolitan player base, and players there notice input lag. The startup wants to run compute close to that city while still managing it with the usual EC2 tools. What should it use?

Included in Master: master every domain.See plans