SaveMyCert
Log in
5 of 5 free questions left today·for 10 a day
CLF-C02 · Domain 2

Security and Compliance practice questions

Security and Compliance is worth 30% of the CLF-C02 exam — the 2nd-heaviest of the 4 domains. The shared responsibility model, AWS security and governance concepts, identity and access management, and security resources. 6 fully worked examples are further down this page, answers included.

Exam weight
30%
the 2nd-heaviest of the 4 domains
Questions
173
across 4 topics
Free, no account
5/day
a free account allows 10 a day
Explanations
Every option
right and wrong

Build a practice session

5 free questions left today.

Domains

How many?

5 free questions left today.

Mode

Ready when you are

10 fresh questions drawn across 1 of 4 domains, in Learn mode.

Review what you missed

Every question you answer incorrectly, and every question you flag while practising, is saved here automatically. Finish a session and you can come back to re-drill just those.

6 sample Security and Compliance questions, fully explained

Questions from the CLF-C02 bank mapped to domain 2, with the answer key and the reasoning behind every option. None of them repeat the examples on the main CLF-C02 practice page.

Question 1Security and Compliance

Under the AWS shared responsibility model, which activity is an example of security IN the cloud?

Choose one.

  • a
    Applying security patches to the hypervisor

    The hypervisor is part of the virtualization software AWS operates, and customers never patch it on any service.

  • b
    Destroying storage media that is retired from a data center

    Media disposal is part of the hardware lifecycle that AWS manages; customers never handle physical devices.

  • c
    Operating the network links that connect Availability Zones

    The global infrastructure of Regions, Availability Zones, and the cabling between them is built and secured by AWS.

  • d
    Configuring network ACLs and subnet routing for a workload Correct

    Network and firewall configuration for customer resources reflects the customer's decisions about allowed traffic, so it is security IN the cloud.

The concept

Security IN the cloud is everything the customer creates, configures, or grants access to: data, identities, guest operating systems, network configuration, and encryption choices.

Why that’s the answer

Configuring network ACLs and routing is the customer's job because only the customer knows which traffic their workload should permit; AWS supplies the virtual networking, but the rules encode customer intent. The three distractors all live in layers the customer can never touch. The hypervisor is host virtualization software AWS operates, retiring and destroying physical disks is part of AWS's hardware and media-disposal process, and the network connecting Availability Zones is AWS's global infrastructure. A reliable test is whether the activity requires access to AWS hardware or host software: all three distractors do, so all three are security OF the cloud.

How to reason it out
  1. Recall that IN the cloud means the customer's data, access, and configuration layers.
  2. Check each option for whether it requires access to AWS hardware, host software, or facilities.
  3. Hypervisor patching, media destruction, and inter-AZ networking all require infrastructure access, so they are AWS's.
  4. Network ACL and routing configuration expresses the customer's traffic decisions, so it is the customer's responsibility.

Exam tip: Network and firewall configuration for your resources is always your responsibility, even though AWS provides the networking features.

AWS Shared Responsibility Model: Security OF the Cloud vs IN the Cloud — the lesson that teaches this.

Question 2Security and Compliance

Which TWO statements about the AWS shared responsibility model are accurate? (Select TWO.)

Choose TWO.

  • a
    The customer maintains the host operating systems on the physical servers that run EC2.

    Host operating systems sit beneath the hypervisor and are AWS's responsibility. On EC2 the customer maintains only the guest OS inside its instances.

  • b
    The model applies to Amazon EC2 and other infrastructure services, not to managed services.

    The model applies to every AWS service. Managed services change where the line sits, not whether there is one.

  • c
    The division of responsibilities shifts depending on how managed the AWS service is. Correct

    The more AWS operates for you (RDS, Lambda), the higher AWS's side reaches; on EC2 the customer manages more.

  • d
    AWS becomes responsible for customer data once it is stored in a managed service.

    Customer data stays the customer's responsibility on every service; a managed service moves operational work, not data ownership.

  • e
    Patch management is carried out by both AWS and the customer, each in its own layer. Correct

    Patch management is one of the shared controls: AWS patches infrastructure and managed platforms, the customer patches guest operating systems and its applications.

The concept

The shared responsibility model applies to every AWS service, its boundary moves with how managed a service is, and a few controls are shared, with each party acting in its own layer.

Why that’s the answer

Two statements are accurate. The boundary shifts with the service: on EC2 the customer patches the guest OS, while on RDS and Lambda AWS does. Patch management is a shared control, split by layer rather than handed to one party. The host-OS statement confuses the host with the guest OS. The infrastructure-only statement is false because managed services move the line instead of removing the model. The data statement is the most common misconception: no service, however managed, takes over the customer's data.

How to reason it out
  1. Check host versus guest: host OS and hypervisor are AWS's.
  2. Remember the model covers every service; only the line's position changes.
  3. Apply the anchor: customer data is never transferred to AWS.
  4. Recall the shared controls: patch management, configuration management, awareness and training.

Exam tip: Managed services move the line upward; they never move your data or your access decisions to AWS.

AWS Shared Responsibility Model: Security OF the Cloud vs IN the Cloud — the lesson that teaches this.

Question 3Security and Compliance

Under the AWS shared responsibility model, who is responsible for the secure disposal of decommissioned storage devices that previously held customer data?

Choose one.

  • a
    The customer, as the owner of the data on the device

    Owning the data does not give the customer access to AWS hardware. Disposing of physical media is part of the infrastructure AWS operates.

  • b
    The customer, when the data on it was not encrypted

    Encryption is a customer choice, but it does not change who handles the hardware. AWS decommissions storage devices whether or not the data was encrypted.

  • c
    AWS, as the operator of the storage hardware Correct

    Hardware lifecycle, including secure decommissioning and destruction of storage media, is part of security OF the cloud.

  • d
    Both AWS and the customer, as a shared control

    Media disposal is not one of the shared controls (patch management, configuration management, awareness and training); the customer has no layer of it to perform.

The concept

AWS is responsible for the hardware that runs its services, from procurement to secure decommissioning of storage devices.

Why that’s the answer

Decommissioning storage media requires physical access to AWS hardware, which customers never have, so it belongs to AWS's security OF the cloud. AWS follows its own media-disposal process for retired devices. The tempting distractors tie the hardware to the customer's data or encryption choices, but those decide how the customer protects the data, not who handles the device. It is not a shared control either: only patch management, configuration management, and awareness and training are shared.

How to reason it out
  1. Identify the layer: a physical storage device is hardware.
  2. Recall that customers never access AWS hardware.
  3. Check the shared-control list; media disposal is not on it.
  4. Assign the task to AWS.

Exam tip: Anything that needs hands on AWS hardware, including disposing of old disks, is AWS's job.

AWS Shared Responsibility Model: Security OF the Cloud vs IN the Cloud — the lesson that teaches this.

Question 4Security and Compliance

A company stores confidential documents in Amazon S3. Under the AWS shared responsibility model, who is responsible for protecting the contents of those documents and controlling who can access them?

Choose one.

  • a
    AWS

    AWS secures the storage infrastructure beneath the data but never decides how customer data should be protected or who may see it.

  • b
    AWS for public buckets and the customer for private buckets

    Whether a bucket is public is itself a customer configuration decision; data responsibility does not change with the bucket's access setting.

  • c
    The customer Correct

    Customer data is always the customer's responsibility, including classifying it, controlling access to it, and choosing whether to encrypt it, on every AWS service.

  • d
    Responsibility is shared equally between AWS and the customer

    Data protection is not one of the shared controls; the contents of and access to customer data belong entirely to the customer.

The concept

Customer data is one of the responsibilities that never moves: on every AWS service, the customer owns its classification, protection, encryption, and access control.

Why that’s the answer

AWS operates the S3 service and secures the infrastructure it runs on, but it cannot know which documents are sensitive, which users deserve access, or whether encryption should be applied, so those decisions and their consequences belong to the customer. The AWS option fails because operating a storage service is different from owning the data in it. The public-versus-private split is a fabricated rule: bucket access settings are themselves customer configurations, so they cannot transfer responsibility to AWS. The shared option fails because the only shared controls are patch management, configuration management, and awareness and training; data protection is a purely customer-side, customer-specific concern.

How to reason it out
  1. Identify the subject of the question: the customer's data and access to it, not the storage infrastructure.
  2. Apply the anchor: customer data is always the customer's responsibility, without exception.
  3. Reject any option that makes data responsibility conditional on a configuration setting or service type.
  4. Reject shared responsibility because data protection is not among the three shared controls.

Exam tip: Your data is always your responsibility; no AWS service, however managed, takes ownership of protecting its contents.

AWS Shared Responsibility Model: Security OF the Cloud vs IN the Cloud — the lesson that teaches this.

Question 5Security and Compliance

Who applies security patches to the hypervisor that isolates Amazon EC2 instances belonging to different customers?

Choose one.

  • a
    The customer, since EC2 is an infrastructure service

    EC2 does give the customer the guest OS, but the hypervisor sits below it and is operated by AWS.

  • b
    AWS and the customer together, as shared patch management

    Patch management is shared, but each party patches its own layer. The hypervisor is in AWS's layer; the customer's layer starts at the guest OS.

  • c
    The customer, when the instances run on Dedicated Hosts

    Dedicated Hosts give the customer a physical server for its own instances, but AWS still operates and patches the virtualization layer on it.

  • d
    AWS, whichever tenancy option the instances use Correct

    The hypervisor is part of security OF the cloud. AWS patches it on shared tenancy, Dedicated Instances and Dedicated Hosts alike.

The concept

The hypervisor and host operating systems are part of the infrastructure AWS operates, so AWS patches them whatever tenancy the customer chooses.

Why that’s the answer

The hypervisor is virtualization software that AWS runs beneath every customer's instances, so patching it is security OF the cloud. EC2 being an infrastructure service moves the guest OS to the customer, not the layer underneath. Shared patch management splits the work by layer, and the hypervisor is in AWS's layer. Dedicated Hosts change who shares the physical server, not who operates the virtualization software on it.

How to reason it out
  1. Place the hypervisor: below the guest OS, part of AWS's infrastructure.
  2. Separate guest OS (customer on EC2) from host and hypervisor (AWS).
  3. Note that tenancy choices change hardware sharing, not responsibility for the hypervisor.
  4. Assign hypervisor patching to AWS.

Exam tip: Guest OS on EC2 = customer; host OS and hypervisor = AWS, whatever the tenancy.

AWS Shared Responsibility Model: Security OF the Cloud vs IN the Cloud — the lesson that teaches this.

Question 6Security and Compliance

A company runs its workload entirely on fully managed serverless services. Who is responsible for creating the execution roles its functions assume and deciding what each role may access?

Choose one.

  • a
    AWS, since the services are fully managed by AWS

    Fully managed means AWS operates the platform; it does not mean AWS decides what the customer's resources may access.

  • b
    AWS creates the roles, and the customer reviews them

    AWS cannot know which permissions a workload needs; the customer creates the roles and their policies.

  • c
    AWS, by attaching AWS managed policies to each role

    AWS publishes managed policies, but it does not attach them to the customer's roles; the customer chooses which policies each execution role gets.

  • d
    The customer, as part of managing access to its resources Correct

    Identity and access management is security IN the cloud on every service, including serverless ones: the customer creates the execution roles and grants their permissions.

The concept

Identity and access management is the customer's responsibility on every AWS service, however managed the service is.

Why that’s the answer

A more managed service moves operational work such as patching to AWS, but not access decisions. AWS provides IAM and publishes managed policies as tools; only the customer knows which resources each function should reach, so creating execution roles and granting permissions stays security IN the cloud. Service-linked roles are a separate case: a service creates them for itself with AWS-defined permissions, but the roles the customer's own functions run as are the customer's. The tempting distractors hand part of the role work to AWS, which the model does not do.

How to reason it out
  1. Identify the task: deciding what the customer's functions can access.
  2. Apply the anchor: access management is customer work on every service.
  3. Ignore the "fully managed" framing; it moves operations, not access decisions.
  4. Choose the customer.

Exam tip: Serverless moves patching to AWS, never permissions.

AWS Shared Responsibility Model: Security OF the Cloud vs IN the Cloud — the lesson that teaches this.

What CLF-C02 domain 2 tests, topic by topic

The official exam guide breaks Security and Compliance into 4 topics. The question bank follows the same split, so a weak topic shows up as a cluster of misses you can go back and read.

Published CLF-C02 practice questions per topic in Security and Compliance
TopicWhat it coversQuestions
Understand the AWS shared responsibility modelExam guide task 2.1. Recognizing the components of the shared responsibility model: what the customer is responsible for, what AWS is responsible for, what is shared, and how responsibilities shift depending on the service used (e.g. EC2 vs RDS vs Lambda).46
Understand AWS Cloud security, governance, and compliance conceptsExam guide task 2.2. Where to find compliance information (AWS Artifact) and how compliance needs vary by geography/industry; security logs and encryption in transit vs at rest; services customers use to secure resources (Amazon Inspector, Security Hub, GuardDuty, Shield); governance services — monitoring with CloudWatch, auditing with CloudTrail and Config, and reporting with access reports; compliance requirements that vary among AWS services.43
Identify AWS access management capabilitiesExam guide task 2.3. IAM fundamentals: protecting the root user, the principle of least privilege, IAM Identity Center; access keys and password policies; credential storage (Secrets Manager, Systems Manager); MFA, cross-account IAM roles, federated identity; groups and users, custom vs managed policies, and root-user-only tasks.43
Identify components and resources for securityExam guide task 2.4. AWS security features and services (AWS WAF, Firewall Manager, Shield, GuardDuty); third-party security products from AWS Marketplace; where to find security guidance (AWS Knowledge Center, Security Center, Security Blog); recognizing security issues with Trusted Advisor.41
Total173

Revise Security and Compliance before you drill it

Other CLF-C02 domains

Security and Compliance: your questions

Security and Compliance is domain 2 of the CLF-C02 exam guide and carries 30% of the scored content — the 2nd-heaviest of the 4 domains. On a 65-question paper that works out to roughly 20 questions, though AWS does not publish an exact per-domain count and individual exam forms vary.

Source

The domain weight and topic list on this page come from the official CLF-C02 exam guide.