Professional Cloud DevOps Engineer
Prepare and test your skills
Prepare and test your skills
Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.
Keep the momentum going with these hand-picked practice scenarios
Want more questions like this?
Get a free certification question every week.
Last updated
Your organization operates a multi-tier microservices application across multiple Google Cloud projects and environments (e.g., production, staging). As a DevOps engineer, you need to design a centralized Cloud Monitoring dashboard that enables team members to troubleshoot across environments efficiently while maintaining strict security controls.
The dashboard design must meet the following requirements:
Which configuration and IAM role assignment should you implement?
Configure dashboardFilters at the dashboard level targeting resource and environment labels, and assign the roles/monitoring.dashboardViewer role to the compliance team.
Configure dashboardFilters at the dashboard level targeting resource labels, and assign the roles/monitoring.editor role with a custom IAM deny policy to the compliance team.
Configure individual static query filters inside each chart tile, and assign the roles/monitoring.editor role to the compliance team.
Create separate duplicated dashboard files for each environment, and share dashboards using unauthenticated public links.
Configure dashboardFilters at the dashboard level targeting resource and environment labels, and assign the roles/monitoring.dashboardViewer role to the compliance team.
This solution implements top-level dashboardFilters within the Cloud Monitoring dashboard definition and grants the predefined Monitoring Dashboard Configuration Viewer (roles/monitoring.dashboardViewer) role to the compliance auditors.
StudyCerts
StudyCertsdashboardFilters allows users to dynamically filter all charts and widgets across the dashboard using template variables and label matching (such as resource.label.environment or resource.label.zone). This eliminates the need to create separate static dashboard definitions for each environment.roles/monitoring.dashboardViewer role provides read-only permissions specifically for dashboard metadata and configuration (monitoring.dashboards.get and monitoring.dashboards.list). It deliberately restricts users from creating, updating, or deleting dashboards, alerting policies, or notification channels.Using native dashboardFilters and roles/monitoring.dashboardViewer strictly satisfies both operational agility and security governance according to Google Cloud best practices.
Configure dashboardFilters at the dashboard level targeting resource labels, and assign the roles/monitoring.editor role with a custom IAM deny policy to the compliance team.
Configure individual static query filters inside each chart tile, and assign the roles/monitoring.editor role to the compliance team.
Create separate duplicated dashboard files for each environment, and share dashboards using unauthenticated public links.