A healthcare company is using Amazon Bedrock to build a GenAI application to analyze patient...

AWS Glue Data Quality is the correct core service because it directly addresses the distinctive requirements that separate this question from ordinary ETL validation. AWS describes Glue Data Quality as a managed, serverless capability for measuring and monitoring dataset quality. It uses Data Quality Definition Language (DQDL) for rules, can automatically analyze datasets and recommend rules, generates a Data Quality score after rule evaluation, supports machine-learning-based anomaly detection, and integrates with Amazon CloudWatch.

Completeness can be evaluated through DQDL rules such as IsComplete . AWS rule recommendations can automatically generate completeness, uniqueness, value-domain, and column-length rules based on observed data. Anomaly detection learns historical statistics and identifies values outside predicted bounds; AWS can additionally recommend future data-quality rules based on detected anomalies.

Glue Data Quality can publish pass/fail metrics into the Glue Data Quality CloudWatch namespace, making the results usable for monitoring, alarms, and regulatory-quality dashboards.

There is one important technical issue in the wording of option B: AWS Glue Data Quality itself does not remove PII. The complete AWS Glue implementation would pair Glue Data Quality with the AWS Glue Detect PII transform. AWS documents that this transform can identify sensitive entities and then mask, redact, hash, or otherwise process identified PII. Therefore, B is clearly the intended and strongest listed answer, but a production implementation should add the Glue PII transform to fully satisfy the question ' s PII-removal requirement.

A requires extensive custom validation. C does not provide the requested automated rule recommendations and managed quality-score capabilities. D handles PII detection but lacks automated DQDL recommendations, ML anomaly detection, and native data-quality scoring.

==========