This repository is an independently maintained study resource for the AWS Certified Cloud Practitioner (CLF-C02) exam.
It is not affiliated with, endorsed by, sponsored by, or maintained by Amazon Web Services (AWS).
AWS, Amazon Web Services, and AWS service names are trademarks of Amazon.com, Inc. or its affiliates.
The repository is based on publicly available AWS exam guides, task statements, documentation, and original practice questions.
It does not contain or accept:
- exam dumps
- leaked exam material
- reconstructed live exams
- screenshots or recordings of live exam content
- claims that practice questions are current real exam questions
AWS may change exam content, services, product names, learning resources, and support offerings at any time. Always check the current official AWS exam guide before relying on any third-party study resource.
Files that describe an exam-day experience are personal, non-authoritative accounts intended to help candidates prepare for practical issues such as room setup, identification, system testing, proctor interaction, connectivity, and time management.
They are not a substitute for current AWS Certification or Pearson VUE rules. Accepted IDs, check-in procedures, software requirements, prohibited items, networking requirements, and online-proctoring policies can change.
No personal-experience file should publish candidate IDs, registration/order numbers, appointment or launch tokens, passport/ID numbers or images, personal contact details, exact private locations, credentials, or live exam questions.
Using this repository does not guarantee a passing exam result. Practice-test percentages are study heuristics only and do not convert directly to AWS's scaled scoring system.
The current public branch is maintained with generic examples and should not intentionally contain unnecessary personal information, private appointment details, credentials, or secrets.
However, Git is versioned: text removed from the latest branch can remain visible in historical commits. Public commit-author metadata may also identify the GitHub account that made a commit.
Cleaning the current branch is therefore not the same as rewriting repository history.
If a historical commit contains information that must be permanently purged, the repository owner should use an appropriate history-rewrite workflow such as git filter-repo, force-push the rewritten history, and follow GitHub's sensitive-data removal guidance where necessary.
Do not rewrite public repository history casually: it changes commit SHAs and can disrupt forks, clones, open pull requests, and existing links.
For material that must have no historical association with an existing repository, publishing a newly created sanitized repository can be safer than attempting to preserve old history.
External AWS, Pearson VUE, and community links are provided for convenience. Availability, policies, and content can change after this repository's validation date.
Last reviewed: 2026-09-26