These free Google Cloud study guides help you organise your learning around cloud projects, identity, networking, application hosting and operational visibility. Use the learning-path comparison, topic explanations, reference glossary, six-week plan and original scenarios to connect study notes with useful decisions. Choose the path that matches your current experience and intended goal, then practise explaining why a solution fits the requirement.
Want free reference PDFs? Email freelearning@ciscoforall.com with your exam code and name. We will send an available older reference file free of charge. Availability varies. See the request section below.
These are learning orientations, not official exam blueprints. Confirm the exact qualification or exam and its current scope before using any resource as a preparation checklist.
| Learning path | Who it suits | Core topics | Practice activity |
|---|---|---|---|
| Cloud foundations | New cloud learners | Shared responsibility and resource organisation | Draw an application and identify which operational tasks remain yours. |
| Cloud administration | Administrators supporting workloads | Access, deployment, monitoring and recovery | Prepare a small deployment checklist with a rollback condition. |
| Cloud architecture | Designers comparing solutions | Availability, service selection and business constraints | Compare two designs against the same requirements. |
| Data and analytics | Learners organising analytical workloads | Data sources, transformations and access | Trace a dataset from ingestion to a report. |
Choose one target and write down what you want to understand or perform. A learner building foundations needs a different sequence from someone reviewing an unfamiliar area before an exam. Use your current experience to identify the first gap, and give that gap a specific practice activity instead of collecting more files without a plan.
Keep a resource register with the document name, topic, publication date and applicable product or framework version. Older reference PDFs can explain foundations, but they may describe retired credential names or earlier behaviour. Mark version-dependent steps for verification. The learning paths on this page help organise study; they do not replace the current provider objectives.
A small retailer wants separate development and production environments. Begin by listing the applications, owners and data involved. Describe which resources belong together and where access should differ. Resource organisation should help people understand ownership and boundaries; a convenient folder name alone does not provide security.
Create a resource register with purpose, owner, environment and recovery needs. For a written exercise, place a test application and a customer-facing application in different operational contexts. Explain how a developer would test a change without accidentally changing the live service. Identify an approval point and a way to compare deployed configuration with the intended baseline.
A user can sign in and still lack permission to perform a particular action. Describe authentication and authorisation separately. Start with a job requirement such as reading a report, then work out the narrowest access that supports it. Avoid using a broad role simply because the first test failed.
Write three personas: developer, analyst and support operator. Give each a clear task and list the resources needed for that task. Test an allowed action and an action outside the role. Include service identities in your diagram, because an application performing background work also needs an explicit access design.
Before comparing computing options, record the workload: long-running service, event-triggered task or batch activity. Add expected traffic, dependencies, operational skills and tolerance for interruption. A service name is less useful than an explanation of why its behaviour fits the application.
Compare two hosting approaches in a decision note. Describe what your team must configure, maintain and observe in each approach. Include deployment and recovery tasks. A design can reduce one maintenance task while introducing another dependency, so discuss both the benefit and the new operational responsibility.
Draw a user request from name resolution to the application response. Identify entry points, routes, access restrictions and downstream services. Include the return journey. A healthy application process does not establish that the user can reach it, and an open connection does not establish that the application produced a correct response.
Investigate a hypothetical report that works internally but fails for outside users. Compare the two paths and identify the first differing dependency. Record the client, time, destination and observed error. Use the comparison to narrow the question before proposing changes to network access.
A team wants a daily sales report. Document where the source records come from, what transformations are needed and who may see the output. Check what happens when a source is late, a value is missing or a record is duplicated. Reliable analytics depends on data meaning as well as a successful processing job.
Create a five-row sample dataset with one missing value and one duplicate transaction. Define your treatment of each before calculating a total. Record which checks belong at ingestion and which belong before publication. Explain why silently replacing every unknown value with zero could mislead the report reader.
Choose a user-visible outcome such as completing a checkout, then identify the evidence that would help diagnose a failure. Logs, metrics and traces answer different questions. Start with the symptom and select the evidence that can narrow it, rather than collecting every available chart.
Write a recovery exercise for a failed deployment. State the condition that triggers rollback, who can perform it and what confirms recovery. Include a test of the user journey after restoration. Keep the exercise in a controlled environment and record the assumptions that would need review for a real workload.
| Concept | Meaning in your notes | Question to answer |
|---|---|---|
| Project | A resource ownership and organisation boundary | Who owns this workload and who should access it? |
| Role | A collection of permissions | Does this role match the task? |
| Service identity | An identity used by an application or process | What action must this process perform? |
| Region | A geographic deployment consideration | What constraints influence location? |
| Observability | Evidence about system behaviour | Which evidence explains this symptom? |
| Recovery objective | An agreed restoration target | What outcome must be restored first? |
Six weeks is an example structure. Extend a stage when you cannot yet explain or apply its concepts. The plan does not promise exam readiness.
| Stage | Focus | Practical work | Progress evidence |
|---|---|---|---|
| Week 1 | Organise projects around real responsibilities | Create a resource register with purpose, owner, environment and recovery needs. | Who owns this workload and who should access it? Answer with evidence from your exercise. |
| Week 2 | Separate identity from authorised access | Write three personas: developer, analyst and support operator. | Does this role match the task? Answer with evidence from your exercise. |
| Week 3 | Choose services by workload requirements | Compare two hosting approaches in a decision note. | What action must this process perform? Answer with evidence from your exercise. |
| Week 4 | Trace network connectivity end to end | Investigate a hypothetical report that works internally but fails for outside users. | What constraints influence location? Answer with evidence from your exercise. |
| Week 5 | Prepare data for its intended use | Create a five-row sample dataset with one missing value and one duplicate transaction. | Which evidence explains this symptom? Answer with evidence from your exercise. |
| Week 6 | Observe service behaviour and practise recovery | Write a recovery exercise for a failed deployment. | What outcome must be restored first? Answer with evidence from your exercise. |
| Observed difficulty | Useful first check | Avoid |
|---|---|---|
| Sign-in succeeds, action fails | Compare the identity, requested action and resource permission | Giving everyone broad access. |
| Service runs but users cannot connect | Trace name resolution, network path and entry points | Restarting unrelated resources repeatedly. |
| Report totals differ | Check missing records, duplicate inputs and transformation rules | Assuming successful processing means correct data. |
| Deployment causes errors | Compare the release with the baseline and rollback criteria | Changing several unrelated components together. |
| Unexpected resource usage | Identify workload, time window and owner | Removing resources without checking dependencies. |
Scenario 1: sign-in succeeds, action fails. Your starting task is to compare the identity, requested action and resource permission. Write the expected result, the evidence you would collect and the next decision if your first explanation is unsupported. The common mistake is giving everyone broad access. Explain why that shortcut could leave the underlying requirement unresolved, then compare your answer with the relevant topic notes above. These are original learning exercises, not reproduced exam questions.
Scenario 2: service runs but users cannot connect. Your starting task is to trace name resolution, network path and entry points. Write the expected result, the evidence you would collect and the next decision if your first explanation is unsupported. The common mistake is restarting unrelated resources repeatedly. Explain why that shortcut could leave the underlying requirement unresolved, then compare your answer with the relevant topic notes above. These are original learning exercises, not reproduced exam questions.
Scenario 3: report totals differ. Your starting task is to check missing records, duplicate inputs and transformation rules. Write the expected result, the evidence you would collect and the next decision if your first explanation is unsupported. The common mistake is assuming successful processing means correct data. Explain why that shortcut could leave the underlying requirement unresolved, then compare your answer with the relevant topic notes above. These are original learning exercises, not reproduced exam questions.
Scenario 4: deployment causes errors. Your starting task is to compare the release with the baseline and rollback criteria. Write the expected result, the evidence you would collect and the next decision if your first explanation is unsupported. The common mistake is changing several unrelated components together. Explain why that shortcut could leave the underlying requirement unresolved, then compare your answer with the relevant topic notes above. These are original learning exercises, not reproduced exam questions.
Scenario 5: unexpected resource usage. Your starting task is to identify workload, time window and owner. Write the expected result, the evidence you would collect and the next decision if your first explanation is unsupported. The common mistake is removing resources without checking dependencies. Explain why that shortcut could leave the underlying requirement unresolved, then compare your answer with the relevant topic notes above. These are original learning exercises, not reproduced exam questions.
For each topic, record an explanation in your own words, one practice result and the next question to investigate. Mark the topic as understood when you can apply it to a different example. Recognising a familiar phrase or remembering an answer is a useful start, but it does not establish that you can reason through a new situation.
When an exercise exposes a mistake, write the assumption, the evidence that contradicted it and the corrected principle. Create a new example using different details and repeat the reasoning. Review weaker topics before spending another session on a comfortable area. If your goal is a credential, compare the tracker with the current objectives so important gaps remain visible.
Email freelearning@ciscoforall.com with your exam name and exact code, if applicable, and the topics you need. Use “Google Cloud Free Reference PDF Request” as the subject. We will send an available older reference file free of charge. Availability varies, and a free file may not be available for every target. The original notes and exercises on this page are free to read without requesting a PDF.
Use older files for background learning and compare them with the current scope of your intended qualification or exam. Product screens, commands, terminology and objectives can change. Verify version-specific information before applying it. We share only reference resources we are permitted to distribute.
Browse Google Premium PDFs for additional preparation resources, then open the product that matches your intended target to explore its details. Compare the exam name and version carefully. Use this page to organise your foundations and identify weaker topics before choosing additional material.
Connect any Premium resource with a clear study task: review a weak topic, explain the reasoning behind a solution or repeat an unfamiliar scenario. Continue using practical activities and your error log so preparation develops understanding rather than only recognition of remembered answers.
Yes. The learning notes, tables, plan and original exercises on this page are free to read. Premium PDFs are available separately through our product pages.
Start with the learning-path comparison and choose the row closest to your goal. If the core topics are unfamiliar, build the foundations first. A more advanced label does not make a resource the best starting point for every learner.
No. These are original learning notes and activities. Confirm the current provider objectives for your exact target and use them to identify any additional topics you need to study.
Yes, you can ask. Include the exact name and code if available, plus the topics you need. Free reference files depend on availability and may be older resources.
Treat them as background material. Compare their topics and version with your intended target and verify details that have changed. Continue practising the relevant concepts.
Use it as a starting structure and adjust it to your experience and available time. Repeat any stage where you cannot explain the topic or apply it to a new example.
Use the free notes to organise your learning and identify gaps. Explore a matching Premium resource for additional review material, then connect it with practical exercises and your topic tracker.
No. Results depend on your knowledge, practical skills and preparation.
Select one learning path and complete one small exercise today. Save the evidence and the next question in your notes. For older reference material, email freelearning@ciscoforall.com with your target details. For additional preparation resources, browse Google Premium PDFs and explore the product that matches your goal.