Task 3.3: Identify AWS compute services.

• AMemory optimized

  Incorrect

  Memory optimized instances are for workloads that process large data sets in memory. These jobs are limited by the processor.

• BCompute optimized

  Correct

  Compute optimized instances are designed for compute-intensive applications that benefit from high-performance processors; batch processing and media transcoding are among their use cases.

• CStorage optimized

  Incorrect

  Storage optimized instances are for high, sequential read and write access to very large data sets on local storage.

• DBurstable performance (T) instances

  Incorrect

  Burstable instances give a baseline CPU level with short bursts above it. Consistently high CPU work such as video encoding calls for fixed performance instances.

Match the instance category to the resource the workload runs out of first: processor, memory, or local storage I/O.

• AAmazon EC2 instances in an Auto Scaling group

  Incorrect

  Auto Scaling adjusts the number of instances, but the team still manages the instances and pays for every one that is running, busy or not.

• BAn Amazon EC2 Reserved Instance running a script that checks the bucket

  Incorrect

  A Reserved Instance is a commitment billed for the whole term, and the script runs on a server the team must manage.

• CAmazon ECS tasks on a cluster of EC2 instances

  Incorrect

  Containers on EC2 still need the team to provision and manage the cluster's instances.

• DAWS Lambda

  Correct

  Lambda runs code in response to events, such as an object arriving in S3, without servers to manage, and you pay only for the compute time you use.

Short, event-driven jobs at unpredictable times are the case serverless functions are built for: nothing runs, and nothing is billed, between uploads.

• ALaunches new instances when CPU utilization rises

  Incorrect

  Adding and removing instances as demand changes is the job of Amazon EC2 Auto Scaling, which registers new instances with the load balancer.

• BCaches static files in edge locations near users

  Incorrect

  Caching content at edge locations is what Amazon CloudFront does.

• CTranslates the domain name into the servers' IP addresses

  Incorrect

  Translating domain names into IP addresses is DNS, which is Amazon Route 53's job.

• DDistributes incoming traffic across targets in one or more Availability Zones

  Correct

  Elastic Load Balancing automatically distributes incoming traffic across multiple targets, such as EC2 instances and containers, in one or more Availability Zones.

• ESends requests only to targets that pass health checks

  Correct

  The load balancer monitors the health of its registered targets and routes traffic only to the healthy ones.

A load balancer spreads requests and steers around unhealthy targets; Auto Scaling changes how many targets there are. Together they give elasticity and availability.

• AAmazon Elastic Container Service (Amazon ECS)

  Incorrect

  ECS is AWS's own container orchestration service. It runs containers well, but it is not Kubernetes.

• BAmazon Elastic Kubernetes Service (Amazon EKS)

  Correct

  EKS is a managed Kubernetes service: AWS runs the Kubernetes control plane, and you keep using standard Kubernetes tooling.

• CAWS Lambda

  Incorrect

  Lambda runs functions in response to events. It does not run Kubernetes workloads.

• DAWS Elastic Beanstalk

  Incorrect

  Elastic Beanstalk deploys and manages web applications for you; it is not a managed Kubernetes service.

On AWS, "containers" splits into ECS (AWS's orchestrator) and EKS (managed Kubernetes). An existing Kubernetes estate points to EKS.

• AThe EC2 launch type, on instances the team manages

  Incorrect

  With the EC2 launch type the team still provisions and manages the cluster's instances — what it wants to stop doing.

• BAn EC2 Auto Scaling group of container hosts

  Incorrect

  Auto Scaling changes how many instances run, but the team still owns and patches them.

• CAWS Fargate

  Correct

  Fargate is serverless compute for containers: you don't provision or manage servers, and you pay for the resources your containers request.

• DMemory optimized EC2 instances

  Incorrect

  A different instance family is still a set of servers the team must run.

ECS decides where containers run; Fargate removes the servers underneath, so there is no cluster capacity left to manage.