An application log's data, including customer identifiers such as email addresses, needs to be redacted. However, these logs also include the email addresses of internal developers from company.com…

Question

Options

• ACreate a regular custom dictionary detector that lists a subset of the developers' email addresses.
• BCreate a regular expression (regex) custom infoType detector to match on @company.com.
• CCreate a regular custom dictionary detector to match all email addresses listed in Cloud Identity.
• DCreate a custom infoType called COMPANY_EMAIL to match @company.com.

• A
  4% (2)
• B
  77% (41)
• C
  13% (7)
• D
  6% (3)

Explanation

The requirement has two parts: redact external customer email addresses AND exclude internal @company.com email addresses from redaction. A regular expression (regex) custom infoType can match the pattern '@company.com' to identify internal emails. This custom infoType is then configured as an exclusion rule within a DLP inspection job, telling DLP to skip redacting any email that matches the internal domain pattern. Option A (custom dictionary listing specific email addresses) is not scalable - it would need to list every internal employee. Option C (matching all emails from Cloud Identity) would flag internal emails as PII to redact, opposite of the goal. Option D creates a custom infoType to match the domain, which is similar to B but less precise - B specifically uses regex which is the standard mechanism for pattern-based exclusion.

No community discussion yet for this question.