Sign in
Home/AWS/AWS Certified Cloud Practitioner (CLF-C02)/Free questions

AWS Certified Cloud Practitioner (CLF-C02) — Free Practice Questions

10 free sample questions from a bank of 977, with the correct answers and explanations. No signup required — start practising right now.

1A company plans to use an Amazon Snowball Edge device to transfer files to the AWS Cloud. Which activities related to a Snowball Edge device are available to the company at no cost?
  • Use of the Snowball Edge appliance for a 10-day period
  • The transfer of data out of Amazon S3 and to the Snowball Edge appliance
  • The transfer of data from the Snowball Edge appliance into Amazon S3
  • Daily use of the Snowball Edge appliance after 10 days
Answer: C

The short version

C — Ingest into S3 from Snowball Edge is free. Data transfer into AWS from a Snowball Edge appliance into S3 carries no transfer charge. Device use time and outbound moves are billable, which isolates inbound as the no-cost activity.

Key concepts in this question

  • Snowball Edge transfer model: rugged device stages on-prem data then ships or uploads into AWS storage.
  • Inbound free rule: AWS waives transfer-in to S3, encouraging migration without network fees.
  • Device time billing: appliance rental days and extra days beyond the window incur charges.
  • Outbound billing: moving data out of S3 to the device or internet follows normal egress pricing.

Why C is correct

AWS pricing exempts uploads into S3 from transfer fees, and Snowball ingest is treated as an upload path. The appliance physically or logically lands objects into the bucket, so no per-GB ingest fee applies. That makes transfer from the device into S3 the only no-cost option listed.

Why the others are wrong

  • A. Ten-day appliance use includes the service and rental window, not a free transfer activity.
  • B. Transfer out of S3 toward the device is egress and follows paid outbound rates.
  • D. Daily use after ten days is explicitly extra billed time, not free.

CLF-C02 exam tip

Into S3 is free, out of S3 is paid, device days are always paid, so pick ingest into S3.

2A company has deployed applications on Amazon EC2 instances. The company needs to assess application vulnerabilities and must identify infrastructure deployments that do not meet best practices. Which AWS service can the company use to meet these requirements?
  • AWS Trusted Advisor
  • Amazon Inspector
  • AWS Config
  • Amazon GuardDuty
Answer: B

The short version

B — Amazon Inspector finds EC2 vulnerabilities and bad practices. Inspector scans instances and container images for CVEs plus CIS benchmark drift. That combined vulnerability and best practice check matches the dual requirement exactly.

Key concepts in this question

  • Inspector scope: agent or agentless scans of EC2, ECR images and Lambda for exposures and deviations.
  • Vulnerability detection: matches installed software against CVE feeds to flag patch needs.
  • Best practice drift: checks CIS baselines for open ports, weak configs and risky permissions.
  • Advisor Config GuardDuty: guidance, compliance recording and threat detection, not CVE scanning of hosts.

Why B is correct

The company needs both app vulnerability assessment and infrastructure deployment review on EC2. Inspector is the purpose-built service for host and image inspection against CVE plus CIS rules. No other listed service performs package-level CVE matching on EC2 fleets.

Why the others are wrong

  • A. Trusted Advisor gives cost and limit guidance without CVE scanning of EC2 software.
  • C. Config records resource changes and rule compliance but does not scan binaries for CVEs.
  • D. GuardDuty detects malicious runtime behavior, not patchable app vulnerabilities.

CLF-C02 exam tip

EC2 CVE plus best practice scan always means Inspector, while threats mean GuardDuty.

3A company has a centralized group of users with large file storage requirements that have exceeded the space available on premises. The company wants to extend its file storage capabilities for this group while retaining the performance benefit of sharing content locally. What is the MOST operationally efficient AWS solution for this scenario?
  • Create an Amazon S3 bucket for each user. Mount each bucket by using an S3 file system mounting utility.
  • Configure and deploy an AWS Storage Gateway file gateway. Connect each user’s workstation to the file gateway.
  • Move each user’s working environment to Amazon WorkSpaces. Set up an Amazon WorkDocs account for each user.
  • Deploy an Amazon EC2 instance and attach an Amazon Elastic Block Store (Amazon EBS) Provisioned IOPS volume. Share the EBS volume directly with the users.
Answer: B

The short version

B — File gateway keeps local performance with cloud scale. A Storage Gateway file gateway presents SMB plus NFS locally while backing to S3. Users keep LAN-speed sharing and the group escapes on-prem capacity limits.

Key concepts in this question

  • File gateway role: on-prem appliance caching hot files and tiering to S3 for durable scale.
  • Local share benefit: workstations mount the gateway, so collaboration stays on the LAN.
  • Per-user buckets and WorkSpaces: add management overhead without shared local caching.
  • EBS direct share: a single block volume cannot scale or share efficiently across many users.

Why B is correct

The need is centralized users, large files, overfull local disks, plus retained local share speed. File gateway solves all three with a cached local endpoint backed by unlimited S3. It is the most operationally efficient because no per-user buckets or desktop rebuilds are needed.

Why the others are wrong

  • A. Per-user S3 mounts lose POSIX locking and local caching while adding bucket sprawl.
  • C. Moving to WorkSpaces plus WorkDocs rebuilds desktops instead of extending file storage.
  • D. Sharing one EBS volume directly limits scale and multi-writer access across users.

CLF-C02 exam tip

Extend local file shares to cloud means file gateway, not per-user buckets or EBS.

4According to security best practices, how should an Amazon EC2 instance be given access to an Amazon S3 bucket?
  • Hard code an IAM user’s secret key and access key directly in the application, and upload the file.
  • Store the IAM user’s secret key and access key in a text file on the EC2 instance, read the keys, then upload the file.
  • Have the EC2 instance assume a role to obtain the privileges to upload the file.
  • Modify the S3 bucket policy so that any service can upload to it at any time.
Answer: C

The short version

C — EC2 assumes a role for S3 access. An instance profile supplies temporary credentials to the application without stored keys. That follows least privilege and removes key rotation work for the team.

Key concepts in this question

  • IAM role for EC2: policy attached via instance profile, credentials vended through metadata service.
  • Temporary credentials: auto-rotated short-lived tokens that the SDK fetches transparently each hour.
  • Instance metadata service: local endpoint that vends role credentials to code without config files.
  • Hardcoded keys: long-lived secrets in code or files that leak and need manual rotation.
  • Open bucket policy: grants the world access and violates least privilege entirely.

Why C is correct

Security best practice forbids embedding user keys on instances. Assuming a role gives only the S3 actions needed, scoped by policy and rotated by AWS through the metadata service. The application simply uses the default credential chain with no secret handling, which also enables CloudTrail auditing of role sessions for compliance review.

Why the others are wrong

  • A. Hardcoding keys in the app exposes secrets in code and images with no rotation.
  • B. Storing keys in a text file on the instance still leaves long-lived secrets on disk.
  • D. Opening the bucket to any service removes authentication and audit control.

CLF-C02 exam tip

EC2 to AWS service always means assume a role with an instance profile, never hardcode user keys anywhere.

5Which option is a customer responsibility when using Amazon DynamoDB under the AWS Shared Responsibility Model?
  • Physical security of DynamoDB
  • Patching of DynamoDB
  • Access to DynamoDB tables
  • Encryption of data at rest in DynamoDB
Answer: C

The short version

C — Customer controls access to DynamoDB tables. Under shared responsibility AWS runs the managed database, while the customer owns data, identities and access policies. Table access grants are therefore the customer duty.

Key concepts in this question

  • Shared responsibility split: AWS secures the cloud infra, customer secures data and access in the cloud.
  • Managed service shift: patching, AZ resilience and at-rest defaults move to AWS for DynamoDB.
  • Customer retained duties: IAM policies, key management choices and table-level grants stay with the user.
  • Physical versus logical control: racks and hosts are AWS, while who can read items is customer logic.

Why C is correct

DynamoDB removes OS and patch work from the customer, but it cannot decide which principals or apps may read specific tables. Defining IAM and table policies is the customer access decision that the model reserves. Options naming physical or patch work therefore belong to AWS.

Why the others are wrong

  • A. Physical security of data centers is always an AWS responsibility.
  • B. Patching the managed DynamoDB fleet is handled by AWS, not the table owner.
  • D. Default at-rest protection for the service is provided by the AWS platform layer.

CLF-C02 exam tip

Managed database plus who can access rows always means customer owns access control.

6Which option is a perspective that includes foundational capabilities of the AWS Cloud Adoption Framework (AWS CAF)?
  • Sustainability
  • Performance efficiency
  • Governance
  • Reliability
Answer: C

The short version

C — Governance is a CAF foundational perspective. The Cloud Adoption Framework organizes transformation into business, people, governance, platform, security and operations. Governance alone among the choices is in that six set.

Key concepts in this question

  • CAF perspectives: six lenses that structure cloud readiness and migration planning work.
  • Governance meaning: oversight, risk, compliance and value tracking for cloud portfolios.
  • Well-Architected pillars: sustainability, performance, reliability and others belong to architecture review, not CAF.
  • Distractor test: exam swaps pillar names into CAF stems to check framework recall.

Why C is correct

AWS documents Governance as one of the six CAF perspectives alongside business and people on the organizational side. Performance efficiency, sustainability and reliability are Well-Architected pillars for workloads, not CAF adoption views. Only Governance matches the CAF list, so C is correct.

Why the others are wrong

  • A. Sustainability is a Well-Architected pillar for environmental impact, not a CAF perspective.
  • B. Performance efficiency guides workload design in Well-Architected, not adoption planning.
  • D. Reliability is also a Well-Architected pillar, not one of the six CAF views.

CLF-C02 exam tip

CAF equals business people governance platform security operations, pillars are different.

7A company is running and managing its own Docker environment on Amazon EC2 instances. The company wants an alternative to help manage cluster size, scheduling, and environment maintenance. Which AWS service meets these requirements?
  • AWS Lambda
  • Amazon RDS
  • AWS Fargate
  • Amazon Athena
Answer: C

The short version

C — AWS Fargate removes cluster and scheduler care. Fargate runs containers serverless on ECS or EKS without managing EC2 hosts. Cluster size, scheduling and host patching move to AWS while teams ship task definitions.

Key concepts in this question

  • Self-managed Docker pain: capacity planning, scheduler tuning and host maintenance on EC2.
  • Fargate model: pay per vCPU plus memory for tasks, no host provisioning or scaling groups.
  • Task definition focus: teams define image plus CPU plus networking while AWS places tasks.
  • Lambda RDS Athena: event functions, relational DB and SQL queries, none schedule Docker fleets.
  • Operational shift: Fargate keeps container portability while removing host operations.

Why C is correct

The company wants Docker without EC2 cluster chores. Fargate schedules tasks onto AWS-managed capacity and scales per task count without node management. That directly offloads size, placement and host upkeep from the team while preserving Docker packaging.

Why the others are wrong

  • A. Lambda runs short functions, not long-lived Docker clusters with custom schedulers.
  • B. RDS manages relational databases and has no container orchestration role.
  • D. Athena queries S3 with SQL and does not run or schedule containers.

CLF-C02 exam tip

Docker on EC2 pain plus want no hosts always means Fargate serverless for containers.

8A company wants to run a NoSQL database on Amazon EC2 instances. Which task is the responsibility of AWS in this scenario?
  • Update the guest operating system of the EC2 instances.
  • Maintain high availability at the database layer.
  • Patch the physical infrastructure that hosts the EC2 instances.
  • Configure the security group firewall.
Answer: C

The short version

C — AWS patches physical hosts for EC2 NoSQL. When users run their own database on EC2, AWS still owns the building, hosts and hypervisor layer. Guest OS, database HA and firewall rules stay customer work in this model.

Key concepts in this question

  • EC2 shared model: AWS guards facilities plus physical hosts, customer guards OS upward.
  • Self-managed NoSQL: install, tune, replicate and back up the engine on rented VMs.
  • Physical patching scope: firmware plus host hypervisor upkeep never surfaces to the tenant.
  • Security groups and OS: virtual firewall plus guest patching are tenant controls.

Why C is correct

The scenario keeps database logic on customer EC2, so only lower layers shift to AWS. Patching the physical boxes that host those instances is squarely the cloud provider duty. Guest updates, DB availability design and group rules remain with the deployer by the shared model.

Why the others are wrong

  • A. Guest OS updates inside the instance belong to the customer on EC2.
  • B. Database layer HA for self-run NoSQL must be architected by the customer.
  • D. Security group firewall configuration is customer network policy.

CLF-C02 exam tip

EC2 self-managed always splits at the hypervisor, AWS below the line, you above it.

9Which AWS services or tools can identify rightsizing opportunities for Amazon EC2 instances? (Choose two.)
  • AWS Cost Explorer
  • AWS Billing Conductor
  • Amazon CodeGuru
  • Amazon SageMaker
  • AWS Compute Optimizer
Answer: A, E

The short version

AE — Cost Explorer plus Compute Optimizer find rightsizing. Explorer surfaces underused spend by instance, Optimizer recommends smaller types from utilization. Together they cover cost view plus sizing action for EC2.

Key concepts in this question

  • Cost Explorer analytics: visualizes spend and usage trends to spot idle or oversized EC2.
  • Compute Optimizer ML: analyzes CloudWatch metrics and suggests optimal families and sizes.
  • Billing Conductor and CodeGuru: billing group logic and code review, neither sizes EC2 hosts.
  • SageMaker: ML platform for models, not fleet rightsizing guidance.

Why AE is correct

Rightsizing needs both waste discovery and concrete target sizes. Cost Explorer identifies candidates through cost and usage views, while Compute Optimizer adds data-driven downsizing picks. The pair is the documented AWS path for EC2 rightsizing opportunities.

Why the others are wrong

  • B. Billing Conductor manages custom billing, not utilization-based sizing.
  • C. CodeGuru improves application code quality, not EC2 instance selection.
  • D. SageMaker trains models and does not analyze EC2 fleet efficiency.

CLF-C02 exam tip

EC2 rightsizing pair is always Cost Explorer to see waste plus Compute Optimizer to pick size.

10Which of the following are benefits of using AWS Trusted Advisor? (Choose two.)
  • Providing high-performance container orchestration
  • Creating and rotating encryption keys
  • Detecting underutilized resources to save costs
  • Improving security by proactively monitoring the AWS environment
  • Implementing enforced tagging across AWS resources
Answer: C, D

The short version

CD — Trusted Advisor saves cost and hardens security. Underused resource checks cut spend, while security checks flag open ports and weak controls. Those two pillars match the settled benefits exactly.

Key concepts in this question

  • Trusted Advisor pillars: cost, performance, security, fault tolerance and service limits guidance.
  • Underutilized detection: flags idle EC2, EBS and RDS for downsizing or stop actions.
  • Security monitoring: checks groups, S3 exposure and IAM use for proactive risk cuts.
  • Non-benefits: orchestration, key rotation and tagging enforcement belong to other services.

Why CD is correct

Trusted Advisor continuously scans the account against best practice rules for waste and risk. Cost rules surface idle capacity for savings, and security rules surface misconfigurations before exploit. C plus D therefore name two native Advisor outcomes that teams act on weekly.

Why the others are wrong

  • A. High-performance orchestration is an ECS or EKS function, not an Advisor check.
  • B. Key creation and rotation is a KMS duty, not a Trusted Advisor benefit.
  • E. Enforced tagging needs Organizations policies or Config rules, not Advisor alone.

CLF-C02 exam tip

Trusted Advisor benefits to memorize are cost waste savings plus security posture checks first.

Want the full bank of 977 questions for AWS Certified Cloud Practitioner (CLF-C02)? See all practice exams.