How to Build a PHI-Redacted Audit Trail for FM Prompts
A healthcare company is developing an application that processes sensitive patient data and gen-erates treatment summaries by using a foundation model (FM). The application must maintain an audit trail of all prompts and completions. The application must securely handle protected health information (PHI) data throughout the processing lifecycle. The company must track all prompt-completion pairs with original patient data, but the company must redact any PHI from stored records. The company must enforce healthcare-specific data retention policies. Which solution will meet these requirements?
Community Insight
You must satisfy auditability, PHI redaction of stored records, and healthcare retention simultaneously; the trap is assuming a Bedrock-native guardrail/flow pipeline covers storage-side redaction and retention obligations.
This AIP-C01 scenario tests how a healthcare app can keep a complete, immutable audit trail of foundation-model prompt-completion pairs while never persisting protected health information. The winning design pairs S3 Object Lock in compliance mode with tag-based lifecycle retention and a Lambda redaction step, which is why option C is correct.
Learners most often pick B, believing Amazon Bedrock Flows and Guardrails sensitive-information filters detect PHI and enforce retention. Guardrails masks PII during model interaction but does not redact already-stored logs, does not provide an immutable audit store, and does not implement healthcare retention policies.
Community Discussion (1 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Option C is the only choice that satisfies every clause of the requirement set at once. S3 Object Lock in compliance mode creates write-once-read-many storage, so the prompt-completion audit trail cannot be altered or purged early, which is exactly what an audit trail of all prompts and completions demands. Tag-based S3 Lifecycle policies give the company an enforcement point for healthcare-specific retention periods applied to PHI-tagged objects, and the Lambda function redacts patient information after processing so that stored records carry no PHI. Because redaction happens as part of processing rather than at the end of a retention window, the company still tracks each prompt-completion pair while keeping persistent records clean.Why the Other Options Are Wrong
Option A leaves PHI intact in S3 until a retention period expires and then deletes it, which violates the explicit requirement to redact any PHI from stored records, and default server-side encryption is a transport-at-rest control rather than a redaction or retention mechanism. Option B leans on Amazon Bedrock Prompt Management and Flows to detect PHI, but those services orchestrate prompts and pipelines rather than perform clinical PHI detection, and Guardrails sensitive-information filters operate on model interactions instead of guaranteeing redacted stored logs plus enforced healthcare retention. Option D puts patient data into an Amazon Bedrock knowledge base, which is a retrieval corpus for RAG rather than an immutable prompt-completion audit log, and a retention Lambda without Object Lock cannot prevent records from being modified. None of A, B, or D delivers compliance-mode immutability alongside redaction and lifecycle-based retention.Community Comment Notes
A single commenter, TNT87, argued for option B, repeating the option wording that the team should "Use Amazon Bedrock Prompt Management and Amazon Bedrock Flows to detect PHI" and closing with "Ans B." That reasoning addresses masking during inference but never establishes an immutable audit trail or a healthcare retention mechanism, which are explicit requirements in the stem. The comment also assumes Guardrails can enforce retention on S3 logs, when the option only offers generic S3 retention settings. On the exam, weight the words compliance mode, redact, and retention policies, since those three together point to option C.Official Reference
Exam Strategy
Scan the stem for three obligations — immutable audit trail, redaction of stored PHI, and enforced retention — then eliminate any option that satisfies only one or two. Bedrock-native wording (Flows, Guardrails, knowledge base) is often a distractor when the requirement is about storage governance.
Frequently Asked Questions
Why isn't Amazon Bedrock Guardrails enough to redact PHI for this audit trail?
Guardrails sensitive-information filters act on model interactions, but they do not redact records already written to storage, do not make logs immutable, and do not enforce healthcare retention periods.
Why does the audit trail need S3 Object Lock in compliance mode?
Compliance mode is write-once-read-many and blocks deletion or overwrite even by administrators, guaranteeing the prompt-completion record stays intact for the full retention window.
Related Analysis
Practice All AIP-C01 Questions
Access 110 questions with complete answers and detailed explanations.
View Full AIP-C01 Practice Test →