Exam Bundle

AWS Lambda runs event-driven code with server infrastructure managed by AWS. This does not address the need for A company runs Docker containers and wants AWS-native container orchestration without requiring Kubernetes. The appropriate Amazon ECS applies because ECS is AWS-native container orchestration for deploying and operating containers.

Amazon EKS is a managed Kubernetes platform. This does not address the need for A company runs Docker containers and wants AWS-native container orchestration without requiring Kubernetes. The appropriate Amazon ECS applies because ECS is AWS-native container orchestration for deploying and operating containers.

Amazon EC2 Auto Scaling: EC2 Auto Scaling adds or removes instances to maintain configured capacity and respond to demand. This does not address the need for A company runs Docker containers and wants AWS-native container orchestration without requiring Kubernetes. The appropriate Amazon ECS applies because ECS is AWS-native container orchestration for deploying and operating containers.

AWS Lambda runs event-driven code with server infrastructure managed by AWS. That does not meet the requirement: A microservices team needs to schedule and manage container tasks using AWS container services.

Amazon EKS is a managed Kubernetes platform. That does not meet the requirement: A microservices team needs to schedule and manage container tasks using AWS container services.

Amazon EC2 Auto Scaling: EC2 Auto Scaling adds or removes instances to maintain configured capacity and respond to demand. That does not meet the requirement: A microservices team needs to schedule and manage container tasks using AWS container services.

Amazon EC2 Auto Scaling: EC2 Auto Scaling adds or removes instances to maintain configured capacity and respond to demand. This does not address the need for A microservices team needs to schedule and manage container tasks using AWS container services. The appropriate Amazon ECS applies because ECS is AWS-native container orchestration for deploying and operating containers.

AWS Lambda runs event-driven code with server infrastructure managed by AWS. This does not address the need for A microservices team needs to schedule and manage container tasks using AWS container services. The appropriate Amazon ECS applies because ECS is AWS-native container orchestration for deploying and operating containers.

Amazon EKS is a managed Kubernetes platform. This does not address the need for A microservices team needs to schedule and manage container tasks using AWS container services. The appropriate Amazon ECS applies because ECS is AWS-native container orchestration for deploying and operating containers.

AWS Lambda runs event-driven code with server infrastructure managed by AWS. That does not meet the requirement: Consider this AWS requirement: An engineering team uses Kubernetes APIs and wants managed Kubernetes control-plane operations.

Amazon S3 stores objects in buckets via object APIs. That does not meet the requirement: Consider this AWS requirement: An engineering team uses Kubernetes APIs and wants managed Kubernetes control-plane operations.

Amazon ECS: Orchestrates container tasks through AWS APIs. That does not meet the requirement: Consider this AWS requirement: An engineering team uses Kubernetes APIs and wants managed Kubernetes control-plane operations.

AWS Lambda runs event-driven code with server infrastructure managed by AWS. This does not address the need for An engineering team uses Kubernetes APIs and wants managed Kubernetes control-plane operations. The appropriate Amazon EKS applies because EKS provides a managed Kubernetes service retaining Kubernetes ecosystem APIs.

Amazon S3 stores objects in buckets via object APIs. This does not address the need for An engineering team uses Kubernetes APIs and wants managed Kubernetes control-plane operations. The appropriate Amazon EKS applies because EKS provides a managed Kubernetes service retaining Kubernetes ecosystem APIs.

Amazon ECS: Orchestrates container tasks through AWS APIs. This does not address the need for An engineering team uses Kubernetes APIs and wants managed Kubernetes control-plane operations. The appropriate Amazon EKS applies because EKS provides a managed Kubernetes service retaining Kubernetes ecosystem APIs.

AWS Lambda runs event-driven code with server infrastructure managed by AWS. That does not meet the requirement: A platform group needs an AWS service to run Kubernetes-based applications.

Amazon S3 stores objects in buckets via object APIs. That does not meet the requirement: A platform group needs an AWS service to run Kubernetes-based applications.

Amazon ECS: Orchestrates container tasks through AWS APIs. That does not meet the requirement: A platform group needs an AWS service to run Kubernetes-based applications.

Amazon ECS: Orchestrates container tasks through AWS APIs. This does not address the need for A platform group needs an AWS service to run Kubernetes-based applications. The appropriate Amazon EKS applies because EKS provides a managed Kubernetes service retaining Kubernetes ecosystem APIs.

AWS Lambda runs event-driven code with server infrastructure managed by AWS. This does not address the need for A platform group needs an AWS service to run Kubernetes-based applications. The appropriate Amazon EKS applies because EKS provides a managed Kubernetes service retaining Kubernetes ecosystem APIs.

Amazon S3 stores objects in buckets via object APIs. This does not address the need for A platform group needs an AWS service to run Kubernetes-based applications. The appropriate Amazon EKS applies because EKS provides a managed Kubernetes service retaining Kubernetes ecosystem APIs.

AWS Batch on EC2: Schedules batch computing jobs that may use managed EC2 environments. That does not meet the requirement: A technical reviewer evaluates this need: A team runs container tasks but does not want to provision or operate the underlying compute instances.

Amazon S3 stores objects in buckets via object APIs. That does not meet the requirement: A technical reviewer evaluates this need: A team runs container tasks but does not want to provision or operate the underlying compute instances.

Amazon EC2 dedicated host allocates physical EC2 server capacity with host-level control. That does not meet the requirement: A technical reviewer evaluates this need: A team runs container tasks but does not want to provision or operate the underlying compute instances.

Amazon S3 stores objects in buckets via object APIs. This does not address the need for A team runs container tasks but does not want to provision or operate the underlying compute instances. The appropriate AWS Fargate applies because Fargate is serverless compute capacity for supported ECS and EKS container workloads.

Amazon EC2 dedicated host allocates physical EC2 server capacity with host-level control. This does not address the need for A team runs container tasks but does not want to provision or operate the underlying compute instances. The appropriate AWS Fargate applies because Fargate is serverless compute capacity for supported ECS and EKS container workloads.

AWS Batch on EC2: Schedules batch computing jobs that may use managed EC2 environments. This does not address the need for A team runs container tasks but does not want to provision or operate the underlying compute instances. The appropriate AWS Fargate applies because Fargate is serverless compute capacity for supported ECS and EKS container workloads.

AWS Batch on EC2: Schedules batch computing jobs that may use managed EC2 environments. That does not meet the requirement: A service owner wants task-level containers with infrastructure capacity managed for supported orchestration.

Amazon S3 stores objects in buckets via object APIs. That does not meet the requirement: A service owner wants task-level containers with infrastructure capacity managed for supported orchestration.

Amazon EC2 dedicated host allocates physical EC2 server capacity with host-level control. That does not meet the requirement: A service owner wants task-level containers with infrastructure capacity managed for supported orchestration.

Amazon S3 stores objects in buckets via object APIs. This does not address the need for A service owner wants task-level containers with infrastructure capacity managed for supported orchestration. The appropriate AWS Fargate applies because Fargate is serverless compute capacity for supported ECS and EKS container workloads.

Amazon EC2 dedicated host allocates physical EC2 server capacity with host-level control. This does not address the need for A service owner wants task-level containers with infrastructure capacity managed for supported orchestration. The appropriate AWS Fargate applies because Fargate is serverless compute capacity for supported ECS and EKS container workloads.

AWS Batch on EC2: Schedules batch computing jobs that may use managed EC2 environments. This does not address the need for A service owner wants task-level containers with infrastructure capacity managed for supported orchestration. The appropriate AWS Fargate applies because Fargate is serverless compute capacity for supported ECS and EKS container workloads.