Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud DevOps Engineer practice bank has 1,455 more like it. Try 10 free: instant score, no account.
Your enterprise operates dozens of microservices deployed across multiple Google Cloud projects segregated by environment and department. You need to establish a centralized observability strategy with the following requirements:
Which architecture should you implement to satisfy these requirements?
This approach maintains decentralized monitoring by configuring separate dashboards and alerting policies independently within each production project's local workspace.
roles/monitoring.editor across every single production project, increasing the administrative blast radius rather than centralizing access in a designated monitoring project.Each individual project was owned by an autonomous team that required strictly isolated monitoring, local alerting boundaries, and zero cross-project visibility.
This approach proposes using Pub/Sub messaging pipelines to publish metric metadata and descriptors to a central project, while granting organization-wide administrative privileges.
roles/monitoring.admin at the organization level provides excessive permissions across all organizational resources rather than scoped access to a central monitoring interface.roles/monitoring.admin at the organization level grants full administrative control over monitoring configurations across all development, staging, and sensitive production projects.You needed to export real-time custom telemetry payloads to a third-party SIEM or external monitoring tool outside of Google Cloud.
A scoping project hosts a metrics scope, which is a Cloud Monitoring construct that defines the set of monitored Google Cloud projects whose time-series data is visible to the scoping project. By linking multiple monitored projects to a single scoping project, Cloud Monitoring allows engineers to chart, query, and alert on multi-project metrics within a unified console interface.
roles/monitoring.editor) role on the scoping project to build dashboards and define alerting policies. They can view and alert on time-series telemetry across all scoped projects without needing elevated administrative permissions on individual workload projects.This solution uses Google Cloud's native multi-project monitoring model. It centralizes alert configurations and dashboard definitions while respecting IAM boundaries, avoiding the operational overhead of log routing sinks, custom metric pipelines, or duplicate dashboard creation in each project.
This approach uses an aggregated log sink in Cloud Logging to route audit and application logs across the organization into a centralized BigQuery dataset, then leverages SQL-based alerting and Looker Studio for analytics and visualization.
The requirement was to perform long-term compliance auditing, security log analytics, or historical security trend analysis across organization-wide log sinks.
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