Which Amazon Comprehend filtering design meets privacy and latency requirements?
A company is developing a customer communication platform that uses an AI assistant powered by an Amazon Bedrock foundation model (FM). The AI assistant summarizes customer messages and generates initial response drafts. The company wants to use Amazon Comprehend to implement layered content filtering. The layered content filtering must prevent sharing of offensive content, protect customer privacy, and detect potential inappropriate advice solicitation. Inappropriate advice solicitation includes requests for unethical practices, harmful activities, or manipulative behaviors. The solution must maintain acceptable overall response times, so all pre-processing filters must finish before the content reaches the FM. Which solution will meet these requirements?
Community Insight
The question tests Amazon Comprehend's layered moderation capabilities and latency trade-off; the trap is choosing parallel latency in option A while ignoring that PII detection without redaction does not protect customer privacy.
Amazon Comprehend layered content filtering for a Bedrock-powered assistant requires toxicity detection, prompt safety classification, and PII redaction to run before inference. This page establishes why option D satisfies all three checks with parallel pre-processing while option A leaves PII unredacted.
The most common wrong answer is A: it runs the Comprehend filters in parallel, but PII detection without redaction still lets sensitive customer data reach the Bedrock FM, so the privacy requirement is not met.
Community Discussion (7 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Option D is the only choice that combines the three Amazon Comprehend capabilities the scenario requires: toxicity detection for offensive content, prompt safety classification for inappropriate advice solicitation, and PII detection with entity redaction for customer privacy. Running the independent checks in parallel is the right latency pattern because the requirement says every pre-processing filter must finish before the draft request reaches the Bedrock FM. Redaction is essential: merely detecting PII does not stop sensitive data from being included in the FM prompt. The 0.5 toxicity threshold is a tuning detail, not a disqualifier in a question that does not specify per-category thresholds, and CloudWatch alarms add useful visibility into filter behavior.Why the Other Options Are Wrong
Option A has the right parallel latency idea and covers toxicity and prompt safety, but its PII detection is without redaction, so customer data can still reach the FM and the privacy requirement fails. Option B misuses Comprehend custom classification as if it could build an FM and gates PII detection behind the custom classifier, so not every message receives the privacy filter and the design is not a clean layered pre-processing pipeline. Option C is the serial version: prompt safety, then toxicity, then PII in streaming mode adds cumulative latency and EventBridge human review without clearly redacting PII before inference. Option D's fixed 0.5 threshold is less flexible than a tuned threshold, but it still supplies all three filters plus redaction and parallel execution.Community Comment Notes
The comments show the main split in the thread. Naaser supports A for "Lowest Latency" and complete coverage, but OlaFemi points out the fatal gap: "a redaction is needed" for PII, which A omits. Chibuzo1 backs D because it pairs toxicity, prompt safety, and PII with redaction and parallel execution, while mosun and jyrajan69 object to D's fixed 0.5 threshold; that is a tuning concern, not a failure of the privacy requirement. dbcert87 argues that "layered filtering which rules our parellel processing" favors C, but the latency requirement and the need to finish all filters before the Bedrock FM make the parallel design more defensible. The comments are useful for spotting the redaction trap, but the exam's decisive criterion is complete pre-processing with PII protection.Official Reference
Exam Strategy
Read the privacy requirement as a binary control: detecting PII is not the same as preventing it from reaching the Bedrock FM. When the question says all filters must finish before inference, prefer parallel independent checks that include redaction, and treat fixed thresholds as secondary tuning details.
Frequently Asked Questions
Why is PII detection without redaction insufficient in option A?
Detecting PII only flags it; unless the message is blocked or entities are redacted, sensitive customer data can still reach the Bedrock FM, failing the privacy requirement.
Does layered content filtering require sequential Comprehend calls?
No. Toxicity detection, prompt safety classification, and PII redaction can run in parallel as long as every filter finishes before the Bedrock FM receives the draft request.
Related Analysis
Practice All AIP-C01 Questions
Access 110 questions with complete answers and detailed explanations.
View Full AIP-C01 Practice Test →