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 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?
roles/monitoring.editor role to the compliance team.This option hardcodes metric and resource filters directly into each individual chart definition and grants the Monitoring Editor (roles/monitoring.editor) role at the project level.
roles/monitoring.editor role grants broad write permissions, including monitoring.dashboards.create, monitoring.dashboards.update, monitoring.dashboards.delete, and full administrative control over alerting policies (monitoring.alertPolicies.*). This provides excessive permissions to compliance auditors who only need read-only access to dashboard configurations.The compliance team were responsible for managing, updating, and maintaining alerting infrastructure across all environments rather than performing read-only inspection.
This option duplicates dashboard definitions across multiple static files and attempts to share dashboard views using publicly accessible, unauthenticated links.
dashboardFilters.The metrics were non-sensitive public benchmarks intended for unauthenticated external consumers on an open-source status page.
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.
dashboardFilters 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.
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.This option configures native dashboard filters but assigns the highly privileged Monitoring Editor (roles/monitoring.editor) role to auditors, attempting to restrict write actions after the fact using IAM deny rules.
roles/monitoring.editor) and relying on complex custom deny policies creates unnecessary security risk and management overhead when a purpose-built predefined role already exists.roles/monitoring.dashboardViewer role specifically to grant read-only access to dashboard structures without granting any editing or alerting privileges.Google Cloud did not offer a dedicated dashboard viewer role and required an organization-wide IAM deny policy to block specific dashboard modification API calls across all users.
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