Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Associate Cloud Engineer practice bank has an additional 2,014 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
Your organization wants to monitor service-impacting health events and disruptions across its Google Cloud projects. A site reliability engineer has already been granted the Logs Viewer (roles/logging.viewer) role to view incoming log events, but they must now configure proactive notifications. Specifically, the engineer needs to:
Which set of predefined Identity and Access Management (IAM) roles should you grant to the engineer to meet these requirements using the principle of least privilege?
roles/monitoring.alertPolicyEditor), Monitoring NotificationChannel Editor (roles/monitoring.notificationChannelEditor), and Logs Configuration Writer (roles/logging.configWriter)In Google Cloud, receiving real-time proactive notifications for service disruptions and logged system events requires combining capabilities across Cloud Logging and Cloud Monitoring. Predefined Identity and Access Management (IAM) roles provide targeted sets of permissions that allow engineers to create and manage alerting pipelines while adhering to the principle of least privilege.
To establish end-to-end proactive alerting for service-impacting events, three distinct operational actions must be performed:
roles/monitoring.alertPolicyEditor) role grants the monitoring.alertPolicies.create permission, allowing the engineer to define alert conditions, thresholds, and triggers.roles/monitoring.notificationChannelEditor) role grants the monitoring.notificationChannels.create permission, enabling the creation and updating of notification endpoints such as email, SMS, PagerDuty, or Webhooks.roles/logging.configWriter) role grants the logging.notificationRules.create permission, allowing the engineer to write the necessary notification rules that intercept log entries generated during service incidents.
Granting these three specific predefined roles is the optimal strategy because it directly supplies the required permissions (monitoring.alertPolicies.create, monitoring.notificationChannels.create, and logging.notificationRules.create) without granting broad, over-privileged roles such as Project Editor or Logging Admin. This ensures that the site reliability engineer can configure alerting policies while protecting the cloud environment against unintended configuration changes.
roles/dataprocessing.admin), Monitoring NotificationChannel Viewer (roles/monitoring.notificationChannelViewer), and Monitoring AlertPolicy Viewer (roles/monitoring.alertPolicyViewer)The Data Processing Controls Resource Admin (roles/dataprocessing.admin) role administers controls within the Transparency and Control Center. The Monitoring NotificationChannel Viewer (roles/monitoring.notificationChannelViewer) and Monitoring AlertPolicy Viewer (roles/monitoring.alertPolicyViewer) roles grant read-only visibility into existing notification channels and alerting policies in Cloud Monitoring.
logging.notificationRules.create or logging.configWriter permissions necessary to connect log events to alerts.This selection would be correct if an organization required a data governance compliance officer to audit data processing settings while simultaneously auditing existing alerting policies and notification channel configurations.
When configuring proactive alerting, viewing channels is insufficient; the principal must possess editor-level roles such as Monitoring NotificationChannel Editor to configure new notification endpoints.
roles/monitoring.viewer), Logs Viewer (roles/logging.viewer), and Maintenance API Viewer (roles/maintenance.viewer)The Monitoring Viewer (roles/monitoring.viewer), Logs Viewer (roles/logging.viewer), and Maintenance API Viewer (roles/maintenance.viewer) roles are read-only predefined IAM roles. Monitoring Viewer grants permissions such as monitoring.timeSeries.list to view dashboards and metrics, Logs Viewer allows reading log records, and Maintenance API Viewer allows inspecting scheduled or ongoing infrastructure maintenance events.
monitoring.alertPolicies.create permission needed to build alerting policies.monitoring.notificationChannels.create, preventing the engineer from specifying where alerts should be sent.logging.notificationRules.create, making it impossible to match incoming service health event logs to alerting policies.This set of roles would be appropriate for an auditor or tier-1 support analyst whose sole responsibility is to view real-time system dashboards, inspect maintenance events, and review incoming logs without modifying any alerting rules.
While the Logs Viewer and Maintenance API Viewer roles are helpful for viewing health data and service disruptions, configuring proactive alerts requires editor-level privileges within Cloud Monitoring and Cloud Logging.
roles/logging.admin), Project Editor (roles/editor), and Service Usage Consumer (roles/serviceusage.serviceUsageConsumer)The Logging Admin (roles/logging.admin) role grants full control over all Cloud Logging features, including deleting log buckets, modifying log sinks, and managing access permissions. The Project Editor (roles/editor) role is a primitive role that provides broad read-write access to virtually all Google Cloud resources in the project, while Service Usage Consumer (roles/serviceusage.serviceUsageConsumer) allows accounts to consume project APIs.
This combination would be appropriate if a principal needed overarching administrative rights across the entire project infrastructure, including deploying workloads, administering all logging sinks, and managing project-wide API quotas, rather than specifically setting up alerting policies.
Google Cloud security best practices strongly advise against granting basic roles like Project Editor for operational tasks when specialized predefined roles like Monitoring AlertPolicy Editor exist.
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