PROFESSIONAL-CLOUD-DEVOPS-ENGINEER Question #179: Real Exam Question with Answer & Explanation

Question

You are running an application on Compute Engine and collecting logs through Stackdriver. You discover that some personally identifiable information (PII) is leaking into certain log entry fields. All PII entries begin with the text userinfo. You want to capture these log entries in a secure location for later review and prevent them from leaking to Stackdriver Logging. What should you do?

Options

• ACreate a basic log filter matching userinfo, and then configure a log export in the Stackdriver
• BUse a Fluentd filter plugin with the Stackdriver Agent to remove log entries containing userinfo,
• CCreate an advanced log filter matching userinfo, configure a log export in the Stackdriver console
• DUse a Fluentd filter plugin with the Stackdriver Agent to remove log entries containing userinfo,

Explanation

To prevent PII from leaking into Stackdriver Logging, log entries containing sensitive information must be processed and filtered at the source before ingestion into the logging service.

Common mistakes.

• A. Creating a basic log filter in Stackdriver (Cloud Logging) operates on logs after they have already been ingested into the service, failing to prevent the PII from initially leaking.
• C. An advanced log filter in Stackdriver (Cloud Logging) also processes logs only after their ingestion, meaning the PII has already been recorded in the logging service before the filter can act.
• D. Assuming the truncated option D is identical to B, it would technically achieve the same outcome, but since B is specified as the correct answer, B is the intended solution.

Concept tested. Log preprocessing and filtering at source agent

Reference. https://cloud.google.com/logging/docs/agent/logging/configuration

No community discussion yet for this question.