AWS ECS u0026 EKS: Container Services Essentials Quiz Quiz

Explore foundational concepts of AWS ECS and EKS container services with this quiz designed for beginners. Assess your understanding of container orchestration, deployment, and key differences between ECS and EKS to boost your cloud knowledge.

  1. ECS Launch Types

    Which ECS launch type allows you to run containers on your own virtual machines?

    1. Batch
    2. Lambda
    3. EC2
    4. Fargate

    Explanation: EC2 launch type in ECS lets you manage your own virtual machines for running containers. Fargate is a serverless option where you do not manage the underlying infrastructure. Lambda is used for serverless computing, not for ECS containers. Batch is a separate service focused on batch computing, not direct container orchestration.

  2. EKS and Kubernetes Compatibility

    What container orchestration platform does EKS primarily support for managing workloads?

    1. Docker Compose
    2. Mesos
    3. Swarm
    4. Kubernetes

    Explanation: EKS is designed to provide managed Kubernetes, which is a leading open-source orchestration system. Swarm and Mesos are different orchestration tools and are not the primary platform for EKS. Docker Compose is mainly for local development, not for production-level orchestration in EKS.

  3. Service Discovery

    In ECS, which method can be used to enable service discovery for containers within the same cluster?

    1. Manual container linking
    2. Static IP assignment
    3. QR code scanning
    4. DNS-based

    Explanation: DNS-based service discovery allows ECS containers to locate each other using human-readable names. Static IP assignment is less scalable and not typically used for dynamic containers. QR code scanning does not apply in this context. Manual container linking is outdated and not recommended for modern deployments.

  4. Task and Pod Definitions

    What is the equivalent concept in Kubernetes for an ECS Task Definition?

    1. Service
    2. NodeGroup
    3. Elastic Block Store
    4. Pod Specification

    Explanation: A Pod Specification in Kubernetes defines the containers and their settings, similar to how an ECS Task Definition specifies containers, resources, and configurations. Service exposes applications and balances traffic but does not define containers. NodeGroup manages worker nodes, not container settings. Elastic Block Store is storage, unrelated to container definitions.

  5. Scaling Containers

    Which technique allows you to automatically increase the number of running containers in ECS based on CPU usage?

    1. Spot Pricing
    2. Auto Scaling policies
    3. CloudFront distribution
    4. Reserved Instances

    Explanation: Auto Scaling policies can monitor metrics like CPU and adjust the number of containers dynamically. Reserved Instances involve cost savings for virtual machines, unrelated to scaling containers. CloudFront distribution is for content delivery, not orchestration. Spot Pricing is a cost management feature, not a scaling mechanism.

  6. Networking Modes

    Which ECS networking mode allows each container to have its own unique IP address within a virtual network?

    1. privateSubnet
    2. host
    3. bridge
    4. awsvpc

    Explanation: The awsvpc networking mode assigns each container a unique IP address in your virtual network, enabling better isolation and direct addressing. Bridge and host networking modes do not assign unique addresses to individual containers, leading to less isolation. privateSubnet is a network component, not a networking mode.

  7. Cluster Management

    What is the main responsibility of the control plane in an EKS cluster?

    1. Providing Wi-Fi access
    2. Storing container images
    3. Scheduling pods to nodes
    4. Encrypting data at rest

    Explanation: The control plane schedules pods to nodes, manages cluster state, and maintains the desired state. Storing container images is handled outside the control plane, often in a registry. Encrypting data at rest is a storage responsibility, not specific to the control plane. Wi-Fi access is not relevant in this context.

  8. Load Balancing

    When deploying a service in ECS, which component is typically used to distribute incoming network traffic to multiple container instances?

    1. Edge Location
    2. Direct Connect
    3. Recipe File
    4. Load Balancer

    Explanation: A Load Balancer distributes incoming requests across multiple running container instances, ensuring high availability. Recipe File is not a component used for distribution. Direct Connect is a dedicated network connection, unrelated to traffic balancing. Edge Location refers to content delivery points, not load distribution.

  9. EKS Worker Nodes

    In EKS, what are worker nodes primarily responsible for?

    1. Running pods and containers
    2. Generating invoices
    3. Managing user accounts
    4. Updating the control plane

    Explanation: Worker nodes run the pods and container workloads, handling the actual compute resources. Managing user accounts is a separate administrative role. Updating the control plane is an advanced operation not handled by worker nodes. Generating invoices is unrelated to cluster operations.

  10. Container Images

    On both ECS and EKS, what must be specified in your configuration to launch an application container?

    1. Container Image URI
    2. Access Point Name
    3. Subnet Mask
    4. Email Alias

    Explanation: The Container Image URI identifies the specific container image required to launch your application. Access Point Name is a networking term not related to containers. Email Alias and Subnet Mask are unrelated to container configurations. The correct specification ensures the proper software runs on the service.