Prepare and test your skills

Prepare and test your skills

Free sample question, answered and explained below. The Professional Data Engineer practice bank has 1,353 more like it. Try 10 free: instant score, no account.
An enterprise data analytics platform processes real-time events across several Google Cloud projects within an organization folder. The data engineering team needs to design a unified observability and alerting architecture using Google Cloud Observability to track pipeline health, custom processing latency, and resource utilization.
The solution must satisfy the following technical requirements:
Which combination of steps should the team implement?
This architecture exports logging data to Pub/Sub sinks to feed external third-party visualization platforms (such as Splunk or Datadog) and polls Google Cloud monitoring APIs with scheduled scripts.
The enterprise had a strict mandate requiring a non-GCP third-party SIEM/observability tool as their global corporate single pane of glass.
This architecture establishes a centralized observability strategy by consolidating telemetry from multiple Google Cloud projects into a designated management project metrics scope and log scope. It relies on the Ops Agent for collecting system and workload telemetry, custom dashboard definitions via configuration files, and Cloud Monitoring alerting policies paired with defined notification channels.
_Default/_AllLogs) into a default log scope allows engineers to visualize time-series telemetry and logs across all pipeline projects from a single pane of glass.workload.googleapis.com/...).gcloud monitoring dashboards create with JSON templates creates unified visualization panels for pipeline health.This approach aligns with Google Cloud architecture best practices by decoupling workload execution from centralized monitoring and governance, ensuring complete fidelity without custom log-forwarding infrastructure.
This option foregoes instance-level agents to save compute overhead and relies solely on basic compute platform hypervisor metrics, using batch BigQuery SQL queries over exported audit logs to detect issues.
You were conducting retrospective daily compliance audits on system API calls where near-real-time alerting and in-guest performance metrics are not required.
This approach configures isolated alerting and telemetry handling within each separate pipeline project and relies on custom local log parsing rather than centralized monitoring scopes.
Each project was operated by an isolated, independent organizational team requiring strict data segregation with no centralized operational oversight.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated