SOA-C02 Security and Compliance Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  Amazon EC2: Full control over virtual servers including OS and software.

  Why this is correct

  Amazon EC2 is an Infrastructure-as-a-Service offering that provides resizable virtual machines (instances) with complete control over the guest OS, including kernel, software stack, and installed applications. You choose instance types based on CPU, memory, storage, and network performance, and you can customize the OS via Amazon Machine Images (AMIs). While this deep control lets you configure the environment exactly as needed, it also means you are responsible for patching the OS and maintaining the software, unlike managed or serverless alternatives. Services such as AWS Systems Manager can assist with patch management, but the fundamental control remains with you.

• ✗

  Amazon EC2: Run code without provisioning or managing servers.

  Why it's wrong here

  This statement describes AWS Lambda, not Amazon EC2. Lambda is a function-as-a-service platform that executes code in response to events without requiring you to provision, configure, or manage servers; AWS handles all capacity provisioning and scaling automatically. In contrast, EC2 requires you to launch virtual machines, select instance types, manage the OS, update security patches, and handle scaling manually or via Auto Scaling groups. Thus, the hallmark of Lambda—zero server management—is the opposite of EC2's operational model.

• ✓

  AWS Lambda: Run code without provisioning or managing servers.

  Why this is correct

  AWS Lambda is a serverless compute service that runs code in response to events such as API calls, S3 object uploads, or database changes, without you provisioning or managing any underlying servers. You upload your code, configure triggers and runtime (e.g., Python, Node.js, Java), and Lambda automatically executes and scales the function horizontally based on the incoming request rate. Cold starts may introduce latency, but the infrastructure, including OS patching and capacity management, is entirely AWS's responsibility. This makes Lambda ideal for event-driven, short-lived workloads where managing servers would add undue operational overhead.

• ✗

  AWS Lambda: Managed container orchestration service.

  Why it's wrong here

  This option actually describes Amazon ECS, not AWS Lambda. ECS is a fully managed container orchestration service that simplifies running Docker containers across clusters of EC2 instances or via AWS Fargate, handling scheduling, load balancing, and scaling of containers. Lambda, by contrast, is designed for executing discrete, stateless functions in a serverless execution environment—it does not manage container lifecycle, placement, or orchestration. While Lambda can be triggered by events and runs code, it does not provide container-level control like custom container images or cluster management, which is the core of ECS.

• ✓

  Amazon ECS: Managed container orchestration service.

  Why this is correct

  Amazon ECS is a highly scalable, high-performance container orchestration service that supports Docker containers and allows you to run and scale containerized applications across a cluster of Amazon EC2 instances or using AWS Fargate for serverless consumption. You define task definitions specifying the container images, CPU, memory, and networking, and ECS manages the placement, scheduling, scaling, and health monitoring of those containers. Unlike bare EC2, ECS abstracts the orchestration layer, but unlike Lambda, it still requires you to manage or provision the underlying compute resources unless you use Fargate, which removes that requirement further.

• ✗

  Amazon ECS: Deploy web applications without managing infrastructure.

  Why it's wrong here

  This statement describes AWS Elastic Beanstalk, not Amazon ECS. Elastic Beanstalk is a platform-as-a-service that automatically handles capacity provisioning, load balancing, scaling, and application health monitoring while letting you simply upload your web application code. ECS, on the other hand, requires you to understand container orchestration concepts such as clusters, task definitions, and services; it does not abstract away infrastructure to that degree. With ECS you are responsible for defining how containers are deployed and managed, whereas Elastic Beanstalk automatically manages the infrastructure for you, focusing on ease of deployment for web applications.

Go deeper

Related to this question