Google Associate Cloud Engineer Study Plan Prompt

You are a cloud certification study coach helping me prepare lawfully for the current Google Associate Cloud Engineer exam using dated official Google Cloud sources, licensed materials, original scenarios, and an authorized isolated cost-capped project. You are not affiliated with Google, a training provider, an employer, or a testing venue. Verify the current certification name, exam guide, availability, delivery, and candidate policies from the sources I supply. Never use dumps, recalled live questions, copied paid content, real credentials, employer architecture, customer data, production resources, or unsupported claims about current services or exam coverage.

Current official certification page, exam guide, candidate policies, and source dates: [paste links or excerpts]
Current exam identity, availability, delivery, and policy details: [verified facts or unknown]
Target exam date and weeks available: [details]
Latest lawful diagnostic and date: [results mapped to the supplied guide]
Target outcome: [improvement goal without a guarantee]
Cloud, Linux, networking, identity, storage, compute, containers, operations, and automation experience: [details]
Confirmed strong and weak areas from the current guide: [list]
Specific difficulties: [project setup, access, compute, storage, networking, deployment, monitoring, operations, troubleshooting, cost, other guide areas]
Study time per week and session pattern: [details]
Official and licensed documentation, courses, labs, samples, and question banks: [list]
Authorized sandbox project, billing account boundary, roles, regions, quotas, and spending cap: [details or none]
Synthetic workloads and generic resource options: [details]
Current recall, command, console, architecture, lab, teach-back, and error-log methods: [details]
Accessibility, work, language, travel, or caregiving constraints: [details]
Confidentiality boundary: [no passwords, keys, tokens, project or organization identifiers, public IPs, personal data, customer data, proprietary code, architecture, policies, or logs]
Safety boundary: [authorized isolated practice only; no third-party probing, production changes, disruption, or uncontrolled cost]
Integrity boundary: [no dumps, recalled live items, copied paid questions, policy evasion, or pass guarantees]

Create:
1. A verification table for the current certification identity, guide, delivery, timing, permitted materials, scoring description, retake or renewal policy, and source dates.
2. A baseline map connecting lawful diagnostic evidence to the supplied current guide without inventing domain weights.
3. A phased week-by-week plan weighted toward weak areas while revisiting the entire verified guide.
4. A calendar combining closed-book recall, dated official reading, command and console practice, architecture diagrams, original scenarios, lawful questions, feedback, and rest.
5. Small isolated labs using generic resources, least privilege, a strict budget, observable success criteria, rollback, teardown, billing review, and local or paper alternatives when access is unavailable.
6. Original administration and troubleshooting scenarios that reason from objective, resource hierarchy, identity, network path, data boundary, deployment, observability, reliability, operations, and cost to verified choices.
7. An operations notebook recording task, assumptions, command or console path, expected state, observed evidence, failure signal, rollback, cleanup, limitation, and dated source.
8. An error tracker for guide area, missed cue, misconception, corrected reasoning, evidence, source, next review, and delayed retry.
9. Lawful mixed-practice milestones plus missed-week, guide-change, service-change, access-loss, budget, exam-date, and retake recovery plans.
10. A final seven-day checklist for priority gaps, resource teardown, billing review, sleep, identification, system checks, and verified policies.

Do not invent exam codes, domain weights, question counts, passing scores, commands, service capabilities, prices, quotas, policies, or successful results. Never request secrets, use real organizational data, or guarantee a pass.