Google Professional-Cloud-Security-Engineer Exam With Confidence Using Practice Dumps

To comply with FIPS 140-2 for the messaging app, you need to ensure that both data at rest and data in transit are encrypted according to the standard. Using customer-managed encryption keys (CMEK) ensures that you have control over the encryption keys, and BoringSSL is a library that meets FIPS 140-2 standards for encrypting data in transit.

Steps:

Encrypt Local SSDs: Modify the instance template for the Managed Instance Group (MIG) to use customer-managed encryption keys (CMEK) for encrypting Local SSDs.

Enable BoringSSL: Update the application to use the BoringSSL library for all instance-to-instance communication to ensure that all data in transit is encrypted according to FIPS 140-2 standards.

The standard and most efficient way to stream logs from Google Cloud (including Workspace logs that are shared with Google Cloud) to an external SIEM is via Cloud Logging Sinks pointing to Pub/Sub.5

According to Google Cloud Documentation (Architecture for exporting Cloud Logging logs):

"To stream logs to a third-party SIEM in real-time, you should create a log sink in Cloud Logging. The sink filters for specific logs (e.g., resource.type="audited_resource" and methodName:"login") and exports them to a Pub/Sub topic. The SIEM can then subscribe to this topic to pull events immediately as they are generated."

Why other options are incorrect:

A is incorrect: Exporting to Cloud Storage is for long-term archiving/compliance and is not real-time (it usually involves batched files every few hours).

C is incorrect: Polling via CLI is not scalable, introduces latency, and is prone to failure in production environments.

D is incorrect: Google Workspace does not have a native "direct push" feature for SIEM endpoints; it typically requires an intermediate step like Pub/Sub or BigQuery.

For "automatic discovery, redaction, or pseudonymization" of sensitive data, the specific product is Sensitive Data Protection (formerly known as Cloud Data Loss Prevention - DLP).10

According to Google Cloud Documentation (Sensitive Data Protection Overview):

"Sensitive Data Protection provides visibility into where PII exists in your organization. It allows you to automatically discover and classify data using over 150 predefined infoTypes (like SSN, Credit Card, etc.). Beyond discovery, it can redact (remove), mask (cover), or pseudonymize (replace with a token) the data so that it can be used for analysis without exposing the raw PII."

Why other options are incorrect:

A is incorrect: Cloud Armor is a WAF; it doesn't scan data contents inside a database for PII.

C is incorrect: Encryption (KMS) protects the data from unauthorized disk access, but once an authorized user opens the database, the PII is still visible. It doesn't perform "redaction" or "pseudonymization."

D is incorrect: While the DLP API is mentioned, this option focuses on Cloud Storage and alerts rather than the "redaction/pseudonymization" for analysis requested in the prompt. Option B is the comprehensive managed service approach.