Map Data Flows across a Trust Boundary
Identify the receiver and applicable protection at each stated data-flow step.
About 22 minutes, plus any extended practice
Supplied materials
- Paper and pencil; answers may also be spoken or typed.
- All cases, labels, numbers and rules are supplied on this page. No real account, private information or purchase is needed.
Learn the idea
A data-flow map shows where information moves and which systems or people receive it. Crossing a trust boundary can change exposure or control. A diagram should include local storage, server storage and external recipients, not only the visible screen. The lesson’s systems are fictional and no actual data is transmitted.
Identify the receiver and applicable protection at each stated data-flow step. A public-looking interface does not reveal every downstream recipient.
Use this supplied case: Answers remain only in the described browser. Which destination or boundary is described? The task is to connect the given information to the computing idea. Write a short evidence trail so another learner can reproduce your choice. The simplified case describes the stated model, not every real system.
- Represent the supplied worked case with a labeled drawing, table or short trace.
- Identify the receiver and applicable protection at each stated data-flow step.
- Explain why the worked answer fits and why one alternative does not.
- Try the new check and practice cases; revisit the stated rule if your evidence does not match.
See the method in action
Answers remain only in the described browser. Which destination or boundary is described? The supported answer is Local device storage. Identify the receiver and applicable protection at each stated data-flow step. A public-looking interface does not reveal every downstream recipient. A data-flow map shows where information moves and which systems or people receive it.
Check your reasoning
Your answer is temporary and is not saved to an account. Download your current answer before leaving or reloading. Written work on paper or in another app stays in your own file.
Helpful tips
- Identify the receiver and applicable protection at each stated data-flow step.
- A public-looking interface does not reveal every downstream recipient.
See the answer and explanation
Service server
The supplied case states: Save request writes to the platform service. Which destination or boundary is described? Under the stated distinction, this identifies Service server. A data-flow map shows where information moves and which systems or people receive it. Crossing a trust boundary can change exposure or control. A diagram should include local storage, server storage and external recipients, not only the visible screen. The lesson’s systems are fictional and no actual data is transmitted. Identify the receiver and applicable protection at each stated data-flow step.
Take it further
A local draft is sent to an external provider. Expected: document that data flow, recipient, purpose and controls; the visible screen alone does not explain downstream use.
Nothing here is saved to an account or sent to a teacher. The answer download includes your current choice and any checked feedback. It does not include choices from the separate More practice section. Download that section separately.
More practice: try new cases
Choose an answer for each problem. Explain your method on paper, then use the feedback to decide what to revisit.
Your choices are temporary. Feedback appears after you check all the answers.
Nothing here is saved to an account or sent to a teacher. Keep your own notes or download them before leaving. The score describes these questions; it does not certify subject mastery.
Check the subject sources
These LifeStarter passages, scenarios and exercises are authored for this Academy with AI assistance and review. External resources keep their publishers’ terms. A grade label suggests a starting level; it does not establish alignment with your school’s complete requirements.