A housing authority refuses sending raw citizen PII from S3 access logs to an external generative model. What AI workflow control is that?
Select an answer to reveal the explanation.
Short Explanation
Do not FedEx the citizen PII to an external model just to summarize S3 access logs—minimize first. Bedrock Guardrails, VPC endpoints, and Augmented AI review are useful, but they won't stop raw citizen PII from reaching an external model. Keep PII out.
Full Explanation
Applying data minimization so AI-assisted AWS security workflows do not exfiltrate civic PII to external models keeps housing-authority citizen data out of prompts and training-adjacent paths when summarizing or analyzing S3 access logs. Minimization means stripping or tokenizing identifiers, limiting fields sent to models, and preferring private or VPC-isolated model endpoints when AI assist is used at all. Refusing to send raw citizen PII from access logs to external generative models is a deliberate privacy control aligned with municipal data-protection duties. Applying Bedrock Guardrails filtering so AI-assisted AWS security workflows do not include civic PII in external outputs fails because it filters PII from model outputs but does not prevent raw citizen PII from being sent in prompts to external generative models. Using VPC endpoints so AI-assisted AWS security workflows do not send civic PII traffic outside agency boundaries fails because network path isolation does not remove PII from the model input; the external model can still receive and process citizen identifiers. Adding Augmented AI review so AI-assisted AWS security workflows do not release civic PII findings for use fails because human validation serves oversight of results, not AI data minimization, and does not stop raw PII from leaving for external model processing. Exam caveat: Data minimization for AI-assisted AWS security focuses on keeping civic PII out of external models—not Bedrock Guardrails filtering for civic PII in external outputs, VPC endpoints for keeping civic PII traffic inside agency boundaries, or Augmented AI review for holding civic PII findings from release. Operational check for a housing authority: classify fields in S3 access-log pipelines, build a redaction step that removes citizen identifiers before any model call, verify with packet or API logging that raw PII never leaves the municipal boundary, and use Augmented AI review to avoid releasing civic PII findings for use rather than as a substitute for blocking raw PII from external models.
Prefer to study offline? Printable PDF study book + test engine ($7.50, unofficial). These questions stay free here.