Control who receives information and which details are needed.
Practise restricted recipients, optional public fields, recovery answers and support forms. Two scenarios supply fictional policies; no employer policy is invented.
Four original scenarios each count one correct answer. Your count out of four describes this edition only; it is not a security certification, percentile, or prediction that an account is safe.
Read audience and sensitivity together
This group asks who is allowed to receive a file, whether a public field is necessary, whether a recovery answer is already public and what a support form excludes. The payroll and support scenarios explicitly supply their rules. The correct answer follows those supplied constraints; it is not a claim that every organization uses the same policy.
A name does not set access permissions
Imagine a file named private-notes that is visible to anyone with its link. Renaming it does not restrict access. If a task says only two named accounts may receive it, select a sharing configuration that limits access to those authorized accounts. Before any real sharing, use the actual organization’s rules and the service’s documented permission controls.
What a missed item may reveal
A wrong choice might overlook the audience, confuse a label with a control, treat a public biography fact as a secret, or assume an expiring code is harmless. Identify that one assumption in the worked answer. A four-item count does not measure how much sensitive information you have disclosed in real life or determine whether any legal duty applies.
Rehearse with invented data
For a fictional support request, write a short error description while excluding passwords and sign-in codes. For an invented public profile, mark fields as required or optional and identify the audience. Then explain why each detail needs to be included. This exercise needs no real credentials, identity documents or payroll file.
A rule-following practice, not a policy service
Public FTC guidance supplies background on protecting personal information and authentication secrets. The explicit fictional policies make context-dependent answers testable. This page cannot review a real permission configuration or substitute for an organization’s security and privacy instructions. All four revision guides remain readable even when a section count is zero.