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?

Question

Accepted Answer

B. Use a Fluentd filter plugin with the Stackdriver Agent to remove log entries containing userinfo, The Cloud Logging agent on Compute Engine utilizes Fluentd for log collection. By configuring a Fluentd filter plugin on the VM, log entries containing 'userinfo' can be intercepted and removed or redirected directly on the instance, preventing them from ever being sent to Stackdriver Logging.

Answer

A. Create a basic log filter matching userinfo, and then configure a log export in the Stackdriver 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.

Answer

C. Create an advanced log filter matching userinfo, configure a log export in the Stackdriver console 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.

Answer

D. Use a Fluentd filter plugin with the Stackdriver Agent to remove log entries containing userinfo, 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.

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…

Question

Options

How the community answered

Why each option

Topics

Community Discussion