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 service
Data Studio
Topic in 6 exam domains
Also called: Looker Studio
A Google Cloud reporting and visualization tool, formerly known as Looker Studio.
Where this appears on the exam
3 objectives in 1 of 5 domains
Related topics
This topicWorks alongsideBuilds on theseBuilds on theseAppliedLookerService
Data StudioService
Customer-managed encryption keysFeatureVPC Service ControlsServiceBigQuery Storage Read APIFeatureBI Engine reservationsFeatureCloud MonitoringServiceApigeeServiceBackup and DRServiceData Studio BigQuery connectorFeatureCloud LoggingServiceGoogle Cloud StorageServiceData Studio ProServiceExploreConceptCompute EngineServiceBigQueryServiceGoogle SecOpsServiceCloud SQLServiceBigQuery BI EngineServicePoints to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
- BigQuery works with Data Studio From the official documentation: “Select the BigQuery [connector](/data-studio/connector).”
- BigQuery Storage Read API works with Data Studio From the official documentation: “Data Studio automatically uses the Storage Read API when doing so improves query runtimes.”
- Apigee works with Data Studio From the official documentation: “A Data Studio data source can connect to a single Apigee organization.”
- Backup and DR works with Data Studio From the official documentation: “This page explains how to view Backup and DR prebuilt reports in Data Studio for vaulted backups.”
- BI Engine reservations works with Data Studio From the official documentation: “[BI Engine reservations](/bigquery/docs/bi-engine-intro) can improve the performance of Data Studio dashboards.”
- BigQuery BI Engine works with Data Studio From the official documentation: “BI Engine integrates with Data Studio to accelerate data exploration and analysis.”
- Cloud SQL works with Data Studio From the official documentation: “Data Studio supports both public and private IP connections to PostgreSQL on Cloud SQL.”
- Data Studio works with Explore From the official documentation: “View Looker Explore data in Data Studio”
- Data Studio works with Google Cloud Storage From the official documentation: “All the data you upload via Data Studio is stored in Google Cloud Storage.”
- Data Studio works with Looker From the official documentation: “See the [Connecting to Data Studio](/looker/docs/looker-studio-connector) documentation page to learn more about connecting Looker and Data Studio.”
- Data Studio is an alternative to Looker From the official documentation: “You can also [export these recommendations to BigQuery](/recommender/docs/bq-export/export-recommendations-to-bq) and then examine them using [Data Studio](/bigquery/docs/visualize-looker-studio) or [Looker](/bigquery/docs/looker).”
- Data Studio BigQuery connector is part of Data Studio From the official documentation: “The Data Studio BigQuery connector lets you access and visualize data from your BigQuery tables, views, and custom SQL queries directly within Data Studio.”
- Data Studio Pro is part of Data Studio From the official documentation: “Data Studio offers a premium version, Data Studio Pro, which includes enhanced enterprise capabilities, including permissions management with Identity and Access Management, team workspaces for collaboration, a mobile app, and technical support.”
- BigQuery works with Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
- BigQuery works with Cloud SQL From the official documentation: “Add credentials to connect BigQuery to Cloud SQL.”
- VPC Service Controls secures BigQuery From the official documentation: “BigQuery data is protected with VPC Service Controls”
- BigQuery works with Looker From the official documentation: “Connect Looker to the BigQuery project.”
- Cloud Logging works with Customer-managed encryption keys From the official documentation: “To use Cloud Logging with Customer-managed encryption keys (CMEK), you must complete the steps in the [Enable CMEK for an organization](/logging/docs/routing/managed-encryption#enable) page in the Cloud Logging documentation.”
- BigQuery works with Cloud Monitoring From the official documentation: “You can use Monitoring to export your metrics to BigQuery.”
- Cloud SQL works with Compute Engine From the official documentation: “Create a Compute Engine VM Instance to host a sample web app that connects to Cloud SQL.”
- Google Cloud Storage works with Google SecOps From the official documentation: “Google SecOps uses a unique service account to read data from your GCS bucket.”
- BigQuery is an alternative to Google Cloud Storage From the official documentation: “The training data can be either a CSV file in Cloud Storage or a table in BigQuery.”
- BigQuery works with Google Cloud Storage From the official documentation: “Load Cloud Storage data into BigQuery”
- Cloud Monitoring works with Cloud SQL From the official documentation: “You can also get more details by viewing the Cloud Monitoring logs for your Cloud SQL destination instance.”
- Cloud Logging works with Cloud SQL From the official documentation: “Cloud SQL uses Cloud Logging.”
- Cloud SQL depends on Compute Engine From the official documentation: “Cloud SQL uses Compute Engine virtual machines (VMs) with persistent storage disks.”
- Customer-managed encryption keys secures BigQuery From the official documentation: “You can either create CMEKs manually to protect your BigQuery resources or use Cloud KMS Autokey.”
- Customer-managed encryption keys secures Cloud SQL From the official documentation: “Enable CMEK for Cloud SQL Databases”
- Cloud SQL works with Looker From the official documentation: “To get started, see [Use Looker with Cloud SQL](/sql/docs/sqlserver/looker).”
- Apigee works with Customer-managed encryption keys From the official documentation: “This page describes using CMEK with Apigee.”
- 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 depends on Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
- BigQuery works with Google SecOps From the official documentation: “Google SecOps exports the following categories of data to your BigQuery project:”
- Cloud Logging works with Compute Engine From the official documentation: “Compute Engine sends you Cloud Logging events for scheduled, started, or completed maintenance.”
- Cloud SQL works with Google Cloud Storage From the official documentation: “Imports data into a Cloud SQL instance from a SQL dump or CSV file in Cloud Storage.”
- Compute Engine works with Google Cloud Storage From the official documentation: “The usage export bucket is a Google Cloud Storage bucket where Compute Engine usage reports are stored.”
- VPC Service Controls secures Cloud SQL From the official documentation: “VPC Service Controls perimeters protect the Cloud SQL Admin API.”
- Apigee works with Compute Engine From the official documentation: “| [Compute Engine](https://console.cloud.google.com/apis/library/compute.googleapis.com) | `compute.googleapis.com` | Used for managing your Apigee runtime. |”
- Backup and DR works with Cloud SQL From the official documentation: “Enable the Backup and DR API where the Cloud SQL instances are located.”
- 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.”
- BigQuery works with BigQuery BI Engine From the official documentation: “BigQuery BI Engine lets you perform fast, low-latency analysis services and interactive analytics with reports and dashboards backed by BigQuery.”
- BigQuery BI Engine is part of BigQuery From the official documentation: “BI Engine acceleration is part of BigQuery job processing.”
- Cloud Logging works with Cloud Monitoring From the official documentation: “If a log entry matches the filter of the alerting policy, then Cloud Logging extracts labels and forwards the data to Cloud Monitoring.”
- Cloud Logging is an alternative to Google Cloud Storage From the official documentation: “When you specify your own service account for builds, you must store your build logs in a Cloud Logging bucket, in a user-created Cloud Storage bucket, or in a Google Cloud-created and user-owned Cloud Storage bucket.”
- Cloud Logging works with Google SecOps From the official documentation: “This document explains how to integrate Cloud Logging with Google Security Operations.”
- 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.”
- Customer-managed encryption keys secures Cloud Logging From the official documentation: “Cloud Logging supports encrypting Log storage with CMEK keys.”
- Customer-managed encryption keys secures Compute Engine From the official documentation: “In IL5, CMEK is enabled by default for Compute Engine, Google Kubernetes Engine (GKE), Cloud Storage, and Cloud SQL.”
- Explore is part of Looker From the official documentation: “Ex = [Explore](/looker/docs/creating-and-editing-explores)”
- Google SecOps depends on Google Cloud Storage From the official documentation: “This document explains how to ingest Desynova Contido logs to Google Security Operations using Google Cloud Storage V2.”
- VPC Service Controls secures Backup and DR From the official documentation: “Enclose backup operations within VPC Service Controls security perimeters to help secure your backup workflows.”
- VPC Service Controls secures Compute Engine From the official documentation: “To further protect your Compute Engine resources, you can protect them using [VPC Service Controls](/vpc-service-controls/docs/overview).”
- VPC Service Controls secures Google Cloud Storage From the official documentation: “Storage Transfer Service supports on-premises transfers to Cloud Storage buckets protected by VPC Service Controls, under the following conditions:”
- Apigee works with BigQuery From the official documentation: “You can use the Apigee API to export all analytics data for an entire day from Apigee to your own data repository, such as Google Cloud Storage or BigQuery.”
- Apigee works with Cloud Logging From the official documentation: “This page describes how to find and use [Cloud Logging](/logging/docs) to query and view maintenance logs for an Apigee instance.”
- Apigee works with Cloud Monitoring From the official documentation: “If you are behind a corporate proxy or firewall, Apigee may not be able to send metrics to Cloud Monitoring with its default settings.”
- Apigee works with Google Cloud Storage From the official documentation: “You can use the Apigee API to export all analytics data for an entire day from Apigee to your own data repository, such as Google Cloud Storage or BigQuery.”
- Apigee works with Google SecOps From the official documentation: “This document explains how to integrate Apigee with [Google Security Operations](/chronicle/docs/secops/secops-overview) (Google SecOps).”
- Apigee works with VPC Service Controls From the official documentation: “Apigee integrations with VPC Service Controls have the following limitations:”
How learners score on this topic
Last updated