nerdexam
Amazon

DEA-C01 · Question #181

A company analyzes data in a data lake every quarter to perform inventory assessments. A data engineer uses AWS Glue DataBrew to detect any personally identifiable formation (PII) about customers…

The correct answer is B. Implement custom data quality rules in DataBrew. Apply the custom rules across datasets. AWS Glue DataBrew allows users to create custom data quality rules, including rules for detecting non-standard PII categories. By implementing custom rules, the data engineer can automate the detection of PII (including the custom categories) across multiple datasets without…

Data Security and Governance

Question

A company analyzes data in a data lake every quarter to perform inventory assessments. A data engineer uses AWS Glue DataBrew to detect any personally identifiable formation (PII) about customers within the data. The company's privacy policy considers some custom categories of information to be PII. However, the categories are not included in standard DataBrew data quality rules. The data engineer needs to modify the current process to scan for the custom PII categories across multiple datasets within the data lake. Which solution will meet these requirements with the LEAST operational overhead?

Options

  • AManually review the data for custom PII categories.
  • BImplement custom data quality rules in DataBrew. Apply the custom rules across datasets.
  • CDevelop custom Python scripts to detect the custom PII categories. Call the scripts from
  • DImplement regex patterns to extract PII information from fields during extract transform, and load

How the community answered

(34 responses)
  • A
    9% (3)
  • B
    82% (28)
  • C
    6% (2)
  • D
    3% (1)

Explanation

AWS Glue DataBrew allows users to create custom data quality rules, including rules for detecting non-standard PII categories. By implementing custom rules, the data engineer can automate the detection of PII (including the custom categories) across multiple datasets without needing to manually review or develop custom scripts. This provides a solution with the least operational overhead, as it leverages the existing DataBrew framework and automation Manually reviewing the data is highly labor-intensive, error-prone, and not scalable, especially across multiple datasets. While possible, writing custom Python scripts adds operational overhead, as it requires developing, maintaining, and integrating scripts with DataBrew. This increases complexity compared to implementing custom rules directly within DataBrew. While regex can be useful, incorporating it directly into ETL processes adds operational complexity and doesn't leverage the capabilities of DataBrew, which is already designed for data cleaning and quality validation.

Topics

#AWS Glue DataBrew#Data Quality#PII Detection#Operational Overhead

Community Discussion

No community discussion yet for this question.

Full DEA-C01 Practice