Cloud service models and shared responsibility
Classify three fictional services and list provider and customer responsibilities.
By the end of this lesson
- Explain cloud service models and shared responsibility and when it matters
- Perform a bounded practice or evidence-based scenario
- Verify the result and communicate limitations
Your environment: Use an unprivileged account and a disposable Linux lab. Examples are illustrative; verify syntax and behaviour against the installed software documentation. Where a command could affect a live service, complete the supplied scenario offline. Setup help
Core concepts
Infrastructure as a Service exposes configurable compute, storage and networking; Platform as a Service abstracts more runtime operations; Software as a Service delivers a managed application. Responsibility is shared and shifts by service. A provider securing facilities does not automatically secure customer identities, data or configuration.
Operational decisions should be grounded in scope, observable evidence and a clear success condition. Record the system, version, time window and assumptions. Distinguish what you observed from what you inferred, and avoid exposing credentials or personal data in notes.
A safe working method
Classify three fictional services and list provider and customer responsibilities.
Begin with read-only inspection, change one variable at a time when practical, and preserve a recovery option before consequential work. If the environment differs from the scenario, stop and consult the relevant vendor or distribution documentation rather than guessing.
Interpret the outcome
The answer separates infrastructure controls from customer configuration and data governance.
A command or check provides limited evidence. Validate the result at the level that matters to the task, note any remaining uncertainty and communicate next steps clearly.
See it in context
Worked example
Illustrative checklist for a disposable lab or offline case study.
# Record context before acting
printf '%s\n' 'scope: disposable lab' 'goal: Cloud service models and shared responsibility' 'result: pending' > practice-notes.txt
cat practice-notes.txtThis example creates a local note only. Replace the placeholder with evidence from your own authorised lab; do not include secrets.
Your turn
Practical lab
Build a responsibility matrix for a VM, managed database and hosted email service.
Run commands in your own lab. This website displays instructions; the practice terminal below helps you rehearse the syntax.
1. Prepare your workspace
mkdir -p "$HOME/training4linux/extended-labs" && cd "$HOME/training4linux/extended-labs"
printf '%s\n' 'Practice case: Cloud service models and shared responsibility' > case-notes.txt2. Complete the task
- Classify three fictional services and list provider and customer responsibilities.
- Record the evidence you used and distinguish it from assumptions.
- Write a verification step, a stop condition and a safe cleanup or recovery note.
3. Check your result
- The answer separates infrastructure controls from customer configuration and data governance.
- The exercise stays within the disposable workspace or offline scenario.
- The report names at least one limitation or uncertainty.
Need a hint?
Identify the scope, inspect the relevant evidence and choose the smallest check that distinguishes possible explanations.
Reveal a worked solution
Compare this with your approach after trying the task. More than one valid solution may exist.
Use the expected outcomes as a rubric. Explain why each check supports the conclusion; more than one safe method may be valid.After the lab: No production changes are required. Remove only files created in the disposable practice directory if desired.
Common mistakes to avoid
- Do not run unfamiliar commands with elevated privileges or against production systems.
- Do not treat a successful command exit as proof of the full service outcome.
Check your understanding
Knowledge check
Answer all 3 questions correctly to pass. Retry as often as you need; your best score is kept.
Your lesson progress
Not started · Best score: 0% · Attempts: 0
Practical completion is self-reported. Progress is linked to a private cookie in this browser and stored on the site. Clearing that cookie loses access to it. Manage or erase progress.