Explanation:
Explanation:
Option A is the correct solution because it comprehensively addresses all requirements:
End-to-end data lineage: AWS Glue Data Catalog is specifically designed for data cataloging and lineage tracking across various data sources, providing metadata management and lineage capabilities.
Real-time PII filtering: Amazon Bedrock Guardrails includes built-in PII filters that can detect and filter sensitive information in real-time during inference calls.
Audit trails: AWS CloudTrail provides comprehensive logging of all API calls, including Amazon Bedrock operations, creating a complete audit trail.
Automated compliance reporting: Amazon Macie scans stored data for sensitive information, publishes findings to CloudWatch Logs, and CloudWatch dashboards can visualize these findings and generate automated reports.
Why other options are incorrect:
Option B: AWS Config tracks configuration changes, not data lineage. AWS WAF is for web application firewall protection, not real-time PII filtering in Bedrock. Amazon Comprehend Medical is for medical text analysis, not real-time PII filtering.
Option C: AWS DataSync is for data transfer, not lineage tracking. Session Manager logs user sessions, not comprehensive audit trails. Textract is for document text extraction, not real-time PII filtering.
Option D: Amazon Athena is for querying data, not tracking lineage. CloudWatch metrics and X-Ray are for monitoring and tracing, not comprehensive audit trails. Rekognition Custom Labels is for image/video analysis, not real-time PII filtering in text data.
Ultimate access to all questions.
No comments yet.
A medical company is creating a generative AI (GenAI) system by using Amazon Bedrock. The system processes data from various sources and must maintain end-to-end data lineage. The system must also use real-time personally identifiable information (PII) filtering and audit trails to automatically report compliance.
Which solution will meet these requirements?
A
Use AWS Glue Data Catalog to register all data sources and track lineage. Use Amazon Bedrock Guardrails PII filters. Enable AWS CloudTrail logging for all Amazon Bedrock API calls with Amazon S3 integration. Use Amazon Macie to scan stored data for sensitive information and publish findings to Amazon CloudWatch Logs. Create CloudWatch dashboards to visualize the findings and generate automated compliance reports.
B
Use AWS Config to track data source configurations and changes. Use AWS WAF with custom rules to filter PII at the application layer before Amazon Bedrock processes the data. Configure Amazon EventBridge to capture and route audit events to Amazon S3. Use Amazon Comprehend Medical with scheduled AWS Lambda functions to analyze stored outputs for compliance violations.
C
Use AWS DataSync to replicate data sources to track lineage. Configure Amazon Macie to scan Amazon Bedrock outputs for sensitive information. Use AWS Systems Manager Session Manager to log user interactions. Deploy Amazon Textract with AWS Step Functions workflows to identify and redact PII from generated reports.
D
Configure Amazon Athena to query data sources to analyze and report on data lineage. Use Amazon CloudWatch custom metrics to monitor PII exposure in Amazon Bedrock responses and establish AWS X-Ray tracing to generate an audit trail. Use an Amazon Rekognition Custom Labels model to detect sensitive information in the data that Amazon Bedrock processes.