Build and operate the data processing systems behind analytics and ML on Google Cloud, including BigQuery, Dataflow, and Pub/Sub, and track your readiness for the Professional Data Engineer exam.
Advanced
Prepare and test your skills
Advanced
Prepare and test your skills
Google Cloud feature
dashboards
Topic in 3 exam domains
- dashboards · Feature
- Dashboards · Feature
- dashboards · Concept
Also called: custom Looker dashboards, dashboard, Dashboards engine, Dashboards framework, Google Security Operations Dashboards, Google Security Operations Dashboards engine, Google Security Operations SIEM dashboards, Looker dashboards, nativeDashboards, SIEM dashboards
Visual displays in Cloud Monitoring that present charts and telemetry data collected from instances and services.
Where this appears on the exam
3 subdomains in 2 of 5 domains
Practice questions on this topic
1 question
Monitoring the data lake
Related topics
FoundationsBuilding blocksBuilding blocksBuilding blocksBuilding blocksBuilding blocksBuilding blocksThis topicGoogle SecOpsServiceservice accountConceptApplication Default CredentialsFeatureIdentity and Access ManagementServiceCloud MonitoringServiceCloud LoggingServiceBackup and DRServiceBigQueryServicelog-based metricsFeatureCompute EngineServiceOps AgentService
dashboardsFeature
Points to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
- dashboards is part of Google SecOps From the official documentation: “The Dashboards feature of Google Security Operations is built from charts populated using YARA-L 2.0 properties.”
- Identity and Access Management secures dashboards From the official documentation: “The following permissions are required to access dashboards:”
- dashboards is part of Cloud Monitoring From the official documentation: “In the Monitoring navigation panel, click **Dashboards**.”
- dashboards works with log-based metrics From the official documentation: “This section describes how to create [log-based metrics](/logging/docs/logs-based-metrics) used for setting up monitoring dashboards and alerts.”
- dashboards depends on Ops Agent From the official documentation: “Any dashboards are automatically installed after you configure the integration and the Ops Agent has begun collecting metric data.”
- Application Default Credentials secures BigQuery From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
- BigQuery works with Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
- Compute Engine works with Ops Agent From the official documentation: “In Compute Engine VMs, the Ops Agent can collect logs and most metrics.”
- BigQuery works with Cloud Monitoring From the official documentation: “You can use Monitoring to export your metrics to BigQuery.”
- Application Default Credentials works with BigQuery From the official documentation: “Create a BigQuery client using application default credentials.”
- Application Default Credentials works with Compute Engine From the official documentation: “To authenticate to Compute Engine, set up Application Default Credentials.”
- Cloud Logging works with Ops Agent From the official documentation: “Is the agent sending logs to Cloud Logging?”
- Compute Engine works with service account From the official documentation: “A common method is to attach a service account to a resource like a Compute Engine instance.”
- BigQuery depends on Application Default Credentials From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
- Cloud Monitoring depends on Application Default Credentials From the official documentation: “To authenticate to Monitoring, set up Application Default Credentials.”
- Application Default Credentials secures Compute Engine From the official documentation: “To authenticate to Compute Engine, set up Application Default Credentials.”
- Cloud Monitoring works with Ops Agent From the official documentation: “Is the agent sending metrics to Cloud Monitoring?”
- Application Default Credentials configures BigQuery From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
- Backup and DR works with Compute Engine From the official documentation: “This page details how to use Backup and DR to back up the disks of a Compute Engine instance.”
- BigQuery works with Google SecOps From the official documentation: “Google SecOps can export detailed `ingestion_metrics` tables to your BigQuery dataset.”
- Cloud Logging works with Cloud Monitoring From the official documentation: “You can store and view query-response activity logs in Cloud Logging and set up logs-based monitoring by using Cloud Monitoring.”
- Cloud Logging works with Compute Engine From the official documentation: “Compute Engine sends you Cloud Logging events for scheduled, started, or completed maintenance.”
- service account is part of Identity and Access Management From the official documentation: “Service accounts function as both principals and resources within IAM.”
- Application Default Credentials secures Cloud Monitoring From the official documentation: “To authenticate to Monitoring, set up Application Default Credentials.”
- Application Default Credentials works with Identity and Access Management From the official documentation: “To authenticate to IAM, set up Application Default Credentials.”
- Application Default Credentials works with service account From the official documentation: “You can authenticate the service account using Application Default Credentials (ADC) or a service account key.”
- Backup and DR works with Cloud Monitoring From the official documentation: “Cloud Monitoring: Provides visibility into the usage, performance, and overall health of Backup and DR resources.”
- BigQuery depends on Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
- BigQuery works with Identity and Access Management From the official documentation: “BigQuery uses Identity and Access Management (IAM) for authorization.”
- Cloud Logging depends on Application Default Credentials From the official documentation: “To authenticate to Logging, set up Application Default Credentials.”
- Identity and Access Management secures Compute Engine From the official documentation: “Compute Engine uses Identity and Access Management (IAM) for authorization.”
- log-based metrics is part of Cloud Logging From the official documentation: “To derive metrics from log entries, create [log-based metrics](/logging/docs/logs-based-metrics) in Cloud Logging instead.”
- Ops Agent depends on Compute Engine From the official documentation: “The agents run only on Compute Engine VMs; these procedures apply only to that platform.”
- Application Default Credentials works with Cloud Logging From the official documentation: “To authenticate to Logging, set up Application Default Credentials.”
- Application Default Credentials configures Compute Engine From the official documentation: “To authenticate to Compute Engine, set up Application Default Credentials.”
- Application Default Credentials depends on service account From the official documentation: “If your `BidiProcessOrder` client runs in a secure environment that can be configured with service account credentials (such as Compute Engine, Google Kubernetes Engine, or your on-premise servers), it can use [Application Default Credentials…”
- Application Default Credentials is an alternative to service account From the official documentation: “There are two ways to obtain credentials for the agent to use: - Let the agent use a service account with private-key authentication - Let the agent use application default credentials (ADC).”
- Backup and DR works with BigQuery From the official documentation: “Backup and DR integrates with Cloud Monitoring, Cloud Logging, and BigQuery services and provides the following benefits:”
- Backup and DR works with Cloud Logging From the official documentation: “You can view Backup and DR event logs in **Cloud Logging** by using the Google Cloud console and the Google Cloud CLI.”
- Backup and DR secures Compute Engine From the official documentation: “Backup and DR ensures that the chosen Compute Engine instances get backed up per the frequency set in the backup policy.”
- Backup and DR works with Google SecOps From the official documentation: “This guide describes the integration between Security Command Center, Google Security Operations (Google SecOps), and Backup and DR.”
- Backup and DR depends on Identity and Access Management From the official documentation: “To access Backup and DR, each user needs a Google Account that has been added to a Google Cloud project, folder, or organization as a principal with an Identity and Access Management role that allows access to the Google Cloud console.”
- Backup and DR works with Identity and Access Management From the official documentation: “The Google Cloud-native Backup and DR Service integrates with the Google Cloud ecosystem, including simplified sign-on via SSO, seamless integration with Identity and Access Management (IAM), Cloud Logging, Cloud Monitoring, Key Management, and more.”
- BigQuery works with Compute Engine From the official documentation: “Compute Engine integrates with Google Cloud technologies such as Cloud Storage, Google Kubernetes Engine, and BigQuery, to extend beyond the basic computational capability to create more complex and sophisticated applications.”
- BigQuery works with service account From the official documentation: “The service account can be used by services, such as Cloud Run, to read and modify data in the BigQuery dataset.”
- Cloud Logging is an alternative to Cloud Monitoring From the official documentation: “To see the status of your invalidation request or find a definitive list of recently submitted requests, you can use Cloud Logging or Cloud Monitoring.”
- Cloud Monitoring works with Compute Engine From the official documentation: “Many Google services like Compute Engine send telemetry to Cloud Monitoring.”
- Cloud Monitoring works with Google SecOps From the official documentation: “Google SecOps uses Cloud Monitoring to send the ingestion notifications.”
- Cloud Monitoring works with log-based metrics From the official documentation: “You can display log-based metrics in Cloud Monitoring charts, and alerting policies can monitor these metrics.”
- Compute Engine depends on service account From the official documentation: “The Service Account is used by Compute Engine to access other Google APIs.”
- Identity and Access Management depends on Application Default Credentials From the official documentation: “To authenticate to IAM, set up Application Default Credentials.”
- Identity and Access Management secures BigQuery From the official documentation: “Security in BigQuery is intrinsically linked to [Identity and Access Management (IAM)](/iam/docs/overview) in Google Cloud.”
- Identity and Access Management secures Google SecOps From the official documentation: “You create IAM policies that define which users and groups have access to Google SecOps features.”
- Ops Agent depends on Application Default Credentials From the official documentation: “Google Cloud authorizes the Ops Agent on a Bare Metal Solution server by using ADC.”
- Ops Agent is part of Cloud Monitoring From the official documentation: “Cloud Monitoring offers a [Ops Agent](/monitoring/agent) that collects additional disk, CPU, network, and process metrics from your VM instances.”
- Ops Agent depends on service account From the official documentation: “Use the Compute Engine **VM instances** page of the Google Cloud console to verify that your Compute Engine VM instance has adequate credential for the Ops Agent. The credentials are typically added in the default service account of all new Compute Engine VM instances, but it…”
- service account depends on BigQuery From the official documentation: “Each feature view uses a service account to access the source data in BigQuery during sync.”
- service account is part of Google SecOps From the official documentation: “Each Google SecOps instance has a unique service account.”
How learners score on this topic
Last updated