01. Understand IaaS, PaaS and SaaS
Professional objective : Comparison table and justified choice.
Fictional case study
A fictional library plans a public catalogue and private staff space, without using a real cloud account.
Method to understand
This lesson turns a workplace decision into observable evidence. All data is fictional, and no live service change is required. First separate known facts from assumptions. Work offline or in a dedicated sandbox; then record the rationale and non-sensitive evidence for review.
Guided demonstration
- Prepare the case: read the scenario, identify the output, record assumptions.
- Perform the chapter task: Match three catalogue needs to cloud service models and remaining customer duties.
- Check the result against this criterion: Cloud hosting does not transfer all responsibility.
- Archive output, date and limitations; request human approval for sensitive choices.
Independent practice
Repeat the task with a changed fictional constraint (smaller team or shorter deadline) without using live systems. Match three catalogue needs to cloud service models and remaining customer duties.
Reference answer and verification
Comparison table and justified choice. An acceptable submission includes the deliverable, reasons for choices, and evidence of checking. An inadequate submission only claims success without evidence or discussion of limits.
Limits and safety
Cloud hosting does not transfer all responsibility.
Expected output : Comparison table and justified choice.
Next chapter: reuse this output as the starting point for the next activity.
02. Draw a simple architecture
Professional objective : Annotated architecture with trust boundaries.
Fictional case study
A fictional library plans a public catalogue and private staff space, without using a real cloud account.
Method to understand
This lesson turns a workplace decision into observable evidence. All data is fictional, and no live service change is required. First separate known facts from assumptions. Work offline or in a dedicated sandbox; then record the rationale and non-sensitive evidence for review.
Guided demonstration
- Prepare the case: read the scenario, identify the output, record assumptions.
- Perform the chapter task: Draw browsers, web service, private storage, backup and permitted flows for the case.
- Check the result against this criterion: Separate public, internal and backup components.
- Archive output, date and limitations; request human approval for sensitive choices.
Independent practice
Repeat the task with a changed fictional constraint (smaller team or shorter deadline) without using live systems. Draw browsers, web service, private storage, backup and permitted flows for the case.
Reference answer and verification
Annotated architecture with trust boundaries. An acceptable submission includes the deliverable, reasons for choices, and evidence of checking. An inadequate submission only claims success without evidence or discussion of limits.
Limits and safety
Separate public, internal and backup components.
Expected output : Annotated architecture with trust boundaries.
Next chapter: reuse this output as the starting point for the next activity.
03. Cloud accounts and IAM
Professional objective : Access matrix and revocation workflow.
Fictional case study
A fictional library plans a public catalogue and private staff space, without using a real cloud account.
Method to understand
This lesson turns a workplace decision into observable evidence. All data is fictional, and no live service change is required. First separate known facts from assumptions. Work offline or in a dedicated sandbox; then record the rationale and non-sensitive evidence for review.
Guided demonstration
- Prepare the case: read the scenario, identify the output, record assumptions.
- Perform the chapter task: Build an IAM matrix for administration, catalogue editing and viewing.
- Check the result against this criterion: Avoid shared accounts and over-broad roles.
- Archive output, date and limitations; request human approval for sensitive choices.
Independent practice
Repeat the task with a changed fictional constraint (smaller team or shorter deadline) without using live systems. Build an IAM matrix for administration, catalogue editing and viewing.
Reference answer and verification
Access matrix and revocation workflow. An acceptable submission includes the deliverable, reasons for choices, and evidence of checking. An inadequate submission only claims success without evidence or discussion of limits.
Limits and safety
Avoid shared accounts and over-broad roles.
Expected output : Access matrix and revocation workflow.
Next chapter: reuse this output as the starting point for the next activity.
04. Virtual networks and segmentation
Professional objective : Network plan with stated flow rules.
Fictional case study
A fictional library plans a public catalogue and private staff space, without using a real cloud account.
Method to understand
This lesson turns a workplace decision into observable evidence. All data is fictional, and no live service change is required. First separate known facts from assumptions. Work offline or in a dedicated sandbox; then record the rationale and non-sensitive evidence for review.
Guided demonstration
- Prepare the case: read the scenario, identify the output, record assumptions.
- Perform the chapter task: Separate public front end, internal service and non-public storage in a network diagram.
- Check the result against this criterion: Default-deny unnecessary flows; do not modify a real network.
- Archive output, date and limitations; request human approval for sensitive choices.
Independent practice
Repeat the task with a changed fictional constraint (smaller team or shorter deadline) without using live systems. Separate public front end, internal service and non-public storage in a network diagram.
Reference answer and verification
Network plan with stated flow rules. An acceptable submission includes the deliverable, reasons for choices, and evidence of checking. An inadequate submission only claims success without evidence or discussion of limits.
Limits and safety
Default-deny unnecessary flows; do not modify a real network.
Expected output : Network plan with stated flow rules.
Next chapter: reuse this output as the starting point for the next activity.
05. Storage, encryption and keys
Professional objective : Storage selection table.
Fictional case study
A fictional library plans a public catalogue and private staff space, without using a real cloud account.
Method to understand
This lesson turns a workplace decision into observable evidence. All data is fictional, and no live service change is required. First separate known facts from assumptions. Work offline or in a dedicated sandbox; then record the rationale and non-sensitive evidence for review.
Guided demonstration
- Prepare the case: read the scenario, identify the output, record assumptions.
- Perform the chapter task: Compare object and file storage; document privacy, retention, key ownership and backup.
- Check the result against this criterion: Never place a real secret key into course materials.
- Archive output, date and limitations; request human approval for sensitive choices.
Independent practice
Repeat the task with a changed fictional constraint (smaller team or shorter deadline) without using live systems. Compare object and file storage; document privacy, retention, key ownership and backup.
Reference answer and verification
Storage selection table. An acceptable submission includes the deliverable, reasons for choices, and evidence of checking. An inadequate submission only claims success without evidence or discussion of limits.
Limits and safety
Never place a real secret key into course materials.
Expected output : Storage selection table.
Next chapter: reuse this output as the starting point for the next activity.
06. High availability and recovery
Professional objective : Fictional recovery objectives and timeline.
Fictional case study
A fictional library plans a public catalogue and private staff space, without using a real cloud account.
Method to understand
This lesson turns a workplace decision into observable evidence. All data is fictional, and no live service change is required. First separate known facts from assumptions. Work offline or in a dedicated sandbox; then record the rationale and non-sensitive evidence for review.
Guided demonstration
- Prepare the case: read the scenario, identify the output, record assumptions.
- Perform the chapter task: Compare zone outage with data loss and draft two fictional recovery procedures.
- Check the result against this criterion: RTO/RPO are design targets, not supplier guarantees.
- Archive output, date and limitations; request human approval for sensitive choices.
Independent practice
Repeat the task with a changed fictional constraint (smaller team or shorter deadline) without using live systems. Compare zone outage with data loss and draft two fictional recovery procedures.
Reference answer and verification
Fictional recovery objectives and timeline. An acceptable submission includes the deliverable, reasons for choices, and evidence of checking. An inadequate submission only claims success without evidence or discussion of limits.
Limits and safety
RTO/RPO are design targets, not supplier guarantees.
Expected output : Fictional recovery objectives and timeline.
Next chapter: reuse this output as the starting point for the next activity.
07. Observability and logging
Professional objective : Monitoring sheet with explained thresholds.
Fictional case study
A fictional library plans a public catalogue and private staff space, without using a real cloud account.
Method to understand
This lesson turns a workplace decision into observable evidence. All data is fictional, and no live service change is required. First separate known facts from assumptions. Work offline or in a dedicated sandbox; then record the rationale and non-sensitive evidence for review.
Guided demonstration
- Prepare the case: read the scenario, identify the output, record assumptions.
- Perform the chapter task: Use synthetic latency, error and availability metrics to design cautious alerts.
- Check the result against this criterion: Never portray fabricated metrics as live service data.
- Archive output, date and limitations; request human approval for sensitive choices.
Independent practice
Repeat the task with a changed fictional constraint (smaller team or shorter deadline) without using live systems. Use synthetic latency, error and availability metrics to design cautious alerts.
Reference answer and verification
Monitoring sheet with explained thresholds. An acceptable submission includes the deliverable, reasons for choices, and evidence of checking. An inadequate submission only claims success without evidence or discussion of limits.
Limits and safety
Never portray fabricated metrics as live service data.
Expected output : Monitoring sheet with explained thresholds.
Next chapter: reuse this output as the starting point for the next activity.
08. Infrastructure as Code: safe review
Professional objective : Review of a non-executable infrastructure manifest.
Fictional case study
A fictional library plans a public catalogue and private staff space, without using a real cloud account.
Method to understand
This lesson turns a workplace decision into observable evidence. All data is fictional, and no live service change is required. First separate known facts from assumptions. Work offline or in a dedicated sandbox; then record the rationale and non-sensitive evidence for review.
Guided demonstration
- Prepare the case: read the scenario, identify the output, record assumptions.
- Perform the chapter task: Review fictional descriptive YAML; flag public networking, secrets and approval-sensitive changes.
- Check the result against this criterion: No automatic deployment or real cloud account.
- Archive output, date and limitations; request human approval for sensitive choices.
Independent practice
Repeat the task with a changed fictional constraint (smaller team or shorter deadline) without using live systems. Review fictional descriptive YAML; flag public networking, secrets and approval-sensitive changes.
Reference answer and verification
Review of a non-executable infrastructure manifest. An acceptable submission includes the deliverable, reasons for choices, and evidence of checking. An inadequate submission only claims success without evidence or discussion of limits.
Limits and safety
No automatic deployment or real cloud account.
Expected output : Review of a non-executable infrastructure manifest.
Next chapter: reuse this output as the starting point for the next activity.
09. Cloud budgets and costs
Professional objective : Cost worksheet with explicit assumptions.
Fictional case study
A fictional library plans a public catalogue and private staff space, without using a real cloud account.
Method to understand
This lesson turns a workplace decision into observable evidence. All data is fictional, and no live service change is required. First separate known facts from assumptions. Work offline or in a dedicated sandbox; then record the rationale and non-sensitive evidence for review.
Guided demonstration
- Prepare the case: read the scenario, identify the output, record assumptions.
- Perform the chapter task: Compare three fictional cost proposals separating compute, storage, transfer and contingency.
- Check the result against this criterion: Do not present unsourced vendor pricing as current.
- Archive output, date and limitations; request human approval for sensitive choices.
Independent practice
Repeat the task with a changed fictional constraint (smaller team or shorter deadline) without using live systems. Compare three fictional cost proposals separating compute, storage, transfer and contingency.
Reference answer and verification
Cost worksheet with explicit assumptions. An acceptable submission includes the deliverable, reasons for choices, and evidence of checking. An inadequate submission only claims success without evidence or discussion of limits.
Limits and safety
Do not present unsourced vendor pricing as current.
Expected output : Cost worksheet with explicit assumptions.
Next chapter: reuse this output as the starting point for the next activity.
10. Configuration and shared responsibility
Professional objective : Ten-control responsibility matrix.
Fictional case study
A fictional library plans a public catalogue and private staff space, without using a real cloud account.
Method to understand
This lesson turns a workplace decision into observable evidence. All data is fictional, and no live service change is required. First separate known facts from assumptions. Work offline or in a dedicated sandbox; then record the rationale and non-sensitive evidence for review.
Guided demonstration
- Prepare the case: read the scenario, identify the output, record assumptions.
- Perform the chapter task: Review ten fictional-service controls and assign duties to provider versus customer.
- Check the result against this criterion: Responsibilities depend on service and contract.
- Archive output, date and limitations; request human approval for sensitive choices.
Independent practice
Repeat the task with a changed fictional constraint (smaller team or shorter deadline) without using live systems. Review ten fictional-service controls and assign duties to provider versus customer.
Reference answer and verification
Ten-control responsibility matrix. An acceptable submission includes the deliverable, reasons for choices, and evidence of checking. An inadequate submission only claims success without evidence or discussion of limits.
Limits and safety
Responsibilities depend on service and contract.
Expected output : Ten-control responsibility matrix.
Next chapter: reuse this output as the starting point for the next activity.
11. Migration and exit planning
Professional objective : Migration plan and exit checklist.
Fictional case study
A fictional library plans a public catalogue and private staff space, without using a real cloud account.
Method to understand
This lesson turns a workplace decision into observable evidence. All data is fictional, and no live service change is required. First separate known facts from assumptions. Work offline or in a dedicated sandbox; then record the rationale and non-sensitive evidence for review.
Guided demonstration
- Prepare the case: read the scenario, identify the output, record assumptions.
- Perform the chapter task: Plan a fictional migration covering export, compatibility, acceptance and rollback.
- Check the result against this criterion: Do not shut down or delete actual services in exercises.
- Archive output, date and limitations; request human approval for sensitive choices.
Independent practice
Repeat the task with a changed fictional constraint (smaller team or shorter deadline) without using live systems. Plan a fictional migration covering export, compatibility, acceptance and rollback.
Reference answer and verification
Migration plan and exit checklist. An acceptable submission includes the deliverable, reasons for choices, and evidence of checking. An inadequate submission only claims success without evidence or discussion of limits.
Limits and safety
Do not shut down or delete actual services in exercises.
Expected output : Migration plan and exit checklist.
Next chapter: reuse this output as the starting point for the next activity.
12. Final project: library architecture
Professional objective : Architecture dossier and validation plan.
Fictional case study
A fictional library plans a public catalogue and private staff space, without using a real cloud account.
Method to understand
This lesson turns a workplace decision into observable evidence. All data is fictional, and no live service change is required. First separate known facts from assumptions. Work offline or in a dedicated sandbox; then record the rationale and non-sensitive evidence for review.
Guided demonstration
- Prepare the case: read the scenario, identify the output, record assumptions.
- Perform the chapter task: Build an architecture dossier with diagram, IAM, storage, recovery, monitoring, costs and risks.
- Check the result against this criterion: Review architecture choices before real implementation.
- Archive output, date and limitations; request human approval for sensitive choices.
Independent practice
Repeat the task with a changed fictional constraint (smaller team or shorter deadline) without using live systems. Build an architecture dossier with diagram, IAM, storage, recovery, monitoring, costs and risks.
Reference answer and verification
Architecture dossier and validation plan. An acceptable submission includes the deliverable, reasons for choices, and evidence of checking. An inadequate submission only claims success without evidence or discussion of limits.
Limits and safety
Review architecture choices before real implementation.
Expected output : Architecture dossier and validation plan.
Next chapter: reuse this output as the starting point for the next activity.
