Explore 18 guided topic projects and three capstones in the Learning Hub. Each project includes starter material, deliverables, a worked outline, review checks and a downloadable brief.
AI & data: AI, Data Science, Python, Databases, and Data Engineering & ETL.
Cloud & infrastructure: AWS, Azure, Cloud Engineering, Linux, Storage, and Networking & DNS.
Delivery & operations: DevOps, Docker, Kubernetes, Git & GitHub, Cloud Security & IAM, Monitoring & Troubleshooting, and Cloud Cost Management.
Open the Learning Hub, then choose Projects →
The briefs use fictional scenarios and can be completed with plain language, a spreadsheet or a diagram. No coding or cloud deployment is required.
An interactive training demonstration for exploring retail performance and inventory exceptions. Inspect revenue, margin, potential shortages and price exceptions, then review the source records supporting each result.
The demonstration brings together sales summaries, an inventory snapshot, confirmed inbound deliveries and current price policies.
Change a store or exception filter, inspect a product and compare the summary with its source records. The figures are synthetic examples for learning, not live business results.
Google Sheets: organize and review the source data.
Data Studio: present metrics, exceptions and source links.
Vertex AI Studio: inspect selected evidence with Gemini and check its explanation.
The no-code learning workflow uses a manual handoff to Vertex AI. The dashboard demonstration is not connected to a Google Cloud account.
Share a completed project for review and agree permission and attribution before it is featured here. The examples currently available are trainer demonstrations and guided project briefs.
Trainer demonstration: Inspect the retail decision dashboard, built with synthetic data, and trace the records behind a finding.
Guided project briefs: Explore 18 topic projects and three capstones covering analysis, cloud architecture and AI workflows in the Learning Hub.
Explore project briefs → · Inspect the trainer demonstration →
Share a project link, the problem addressed, tools used, your own contribution and your preferred name or credit. Include permission to publish the material and agree the final attribution before publication.
Discuss a learner submission →
Use these concise design notes and conceptual diagrams to connect technical choices with evidence, access requirements and recovery goals. The practice activities can be completed as a written review or architecture sketch.
Begin with a question that needs source evidence. Prepare approved documents in traceable chunks, create embeddings and retrieve relevant passages for the query. Supply those passages with the question to the model, then review its answer against the cited material.
Design review: Keep ingestion and question answering separate so source updates, retrieval quality and response evaluation can be reviewed independently. Check source versions, relevant passages and unsupported claims.
Practice: Ask a policy question, inspect the retrieved evidence and record whether each answer claim is supported.
Reference: Google Cloud RAG architecture
Start with recovery requirements: which data must be recoverable, how much loss is acceptable and how quickly a restore is needed. Amazon S3 Versioning retains multiple versions of objects and can help recover from accidental deletion or overwrite.
Design review: Consider retained versions, access permissions and the restore procedure together. Define how the recovered object will be checked against the required version and business need.
Practice: Write a restore checklist with the object, required version, authorised operator and evidence that the recovered data is correct.
Reference: Amazon S3 Versioning
Separate authentication from authorisation. A workload establishes an identity, then receives the permissions needed for the target resource. Supported Azure services can use managed identities to authenticate without application-managed passwords or access keys.
Design review: Identify human and workload access separately, choose the required actions and scope, and review role assignments and identity lifecycle. Managed identity handles authentication; access still needs suitable authorisation.
Practice: Sketch a training portal that can read an agreed Blob container. Define the required role and scope and the evidence you would review when checking access.
Reference: Azure managed identities · Azure identity and access guidance
Discuss a practical learning session for your team: praisedcreator@gmail.com