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
Key Visualizer
Topic in 1 exam domain
Also called: Key Visualizer tool, Spanner Key Visualizer
A diagnostic tool that generates heatmaps to visualize database read and write patterns and identify hotspotting issues.
Where this appears on the exam
1 objective in 1 of 5 domains
Domain 3
Storing the data~20% of exam
Related topics
FoundationsBuilding blocksBuilding blocksThis topicApplication Default CredentialsFeaturecustomer-managed encryption keysFeatureIdentity and Access ManagementServiceBigtableServiceFirestoreServiceSpannerServiceBigQueryServiceDataflowServiceCloud MonitoringService
Key VisualizerFeature
Points to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
- Key Visualizer is part of Bigtable From the official documentation: “This page provides an overview of the Key Visualizer diagnostic tool for Bigtable.”
- Key Visualizer is part of Firestore From the official documentation: “This page provides an overview of the Key Visualizer diagnostic tool for Firestore.”
- Key Visualizer is part of Spanner From the official documentation: “Key Visualizer is enabled in Spanner by default.”
- Firestore depends on Application Default Credentials From the official documentation: “To authenticate to Firestore, set up Application Default Credentials.”
- Application Default Credentials secures BigQuery From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
- BigQuery depends on Application Default Credentials From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
- Dataflow depends on Application Default Credentials From the official documentation: “To authenticate to Dataflow, set up Application Default Credentials.”
- Application Default Credentials works with Firestore From the official documentation: “To authenticate to Firestore, set up Application Default Credentials.”
- Application Default Credentials works with BigQuery From the official documentation: “Create a BigQuery client using application default credentials.”
- Application Default Credentials works with Bigtable From the official documentation: “To authenticate to Bigtable, set up Application Default Credentials.”
- Application Default Credentials secures Bigtable From the official documentation: “To authenticate to Bigtable, set up Application Default Credentials.”
- BigQuery works with Dataflow From the official documentation: “Read from BigQuery to Dataflow”
- Application Default Credentials works with Dataflow From the official documentation: “To authenticate to Dataflow, set up Application Default Credentials.”
- Bigtable depends on Application Default Credentials From the official documentation: “To authenticate to Bigtable, set up Application Default Credentials.”
- Application Default Credentials secures Spanner From the official documentation: “To authenticate to Spanner, set up Application Default Credentials.”
- Application Default Credentials works with Spanner From the official documentation: “To authenticate to Spanner, set up Application Default Credentials.”
- Spanner depends on Application Default Credentials From the official documentation: “To authenticate to Spanner, set up Application Default Credentials.”
- BigQuery works with Bigtable From the official documentation: “External BigQuery data source backed by Bigtable”
- BigQuery works with Cloud Monitoring From the official documentation: “You can use Monitoring to export your metrics to BigQuery.”
- BigQuery works with Spanner From the official documentation: “Reverse ETL (BigQuery to Spanner)”
- Cloud Monitoring depends on Application Default Credentials From the official documentation: “To authenticate to Monitoring, set up Application Default Credentials.”
- Dataflow works with Spanner From the official documentation: “Use Dataflow to load data into Spanner.”
- 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.”
- Identity and Access Management secures Firestore From the official documentation: “This page describes the IAM permissions and roles for Firestore.”
- Application Default Credentials secures Dataflow From the official documentation: “To authenticate to Dataflow, 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.”
- Cloud Monitoring works with Dataflow From the official documentation: “Dataflow is fully integrated with Cloud Monitoring.”
- Cloud Monitoring works with Spanner From the official documentation: “Monitor Spanner metrics using Cloud Monitoring.”
- Identity and Access Management secures BigQuery From the official documentation: “Access to BigQuery data from AlloyDB is managed through IAM.”
- BigQuery works with Identity and Access Management From the official documentation: “BigQuery uses Identity and Access Management (IAM) for authorization.”
- customer-managed encryption keys secures Bigtable From the official documentation: “In a CMEK-protected instance, Bigtable uses your CMEK key to protect your data at rest.”
- customer-managed encryption keys works with Spanner From the official documentation: “This page describes how to use manually-created customer-managed encryption keys (CMEK) for Spanner.”
- Identity and Access Management secures Bigtable From the official documentation: “Bigtable uses Identity and Access Management (IAM) for authorization.”
- Identity and Access Management secures Spanner From the official documentation: “Spanner uses Identity and Access Management (IAM) for authorization.”
- Application Default Credentials secures Cloud Monitoring From the official documentation: “To authenticate to Monitoring, set up Application Default Credentials.”
- Application Default Credentials secures Firestore From the official documentation: “To authenticate to Firestore, set up Application Default Credentials.”
- BigQuery works with Firestore From the official documentation: “You can load data from a Firestore with MongoDB compatibility export into BigQuery, but only if you specified a `collection-ids` filter.”
- Bigtable works with Dataflow From the official documentation: “The Dataflow job then writes the transformed data to your Bigtable table.”
- Bigtable works with Identity and Access Management From the official documentation: “Bigtable uses [Identity and Access Management (IAM)](/iam) for access control.”
- Identity and Access Management depends on Application Default Credentials From the official documentation: “To authenticate to IAM, set up Application Default Credentials.”
- Application Default Credentials configures BigQuery From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
- Application Default Credentials works with Cloud Monitoring From the official documentation: “To authenticate to Monitoring, set up Application Default Credentials.”
- BigQuery is an alternative to Dataflow From the official documentation: “To automate the EDA process, use BigQuery or a managed data processing service like Dataflow.”
- Bigtable works with Cloud Monitoring From the official documentation: “The following Bigtable metrics are provided to Cloud Monitoring.”
- Bigtable works with customer-managed encryption keys From the official documentation: “If you want to control your encryption keys, then you can use customer-managed encryption keys (CMEKs) in [Cloud KMS](/kms/docs) with CMEK-integrated services including Bigtable.”
- Cloud Monitoring works with Firestore From the official documentation: “This page describes how to use Cloud Monitoring metrics for Firestore with MongoDB compatibility to monitor your database.”
- Cloud Monitoring depends on Identity and Access Management From the official documentation: “To use Monitoring, you must have the appropriate [Identity and Access Management](/iam/docs/overview) (IAM) permissions.”
- customer-managed encryption keys works with Dataflow From the official documentation: “This sample shows how to use encryption keys managed by the customer, with a Dataflow pipeline.”
- customer-managed encryption keys secures Dataflow From the official documentation: “You can either create CMEKs manually to protect your Dataflow resources or use Cloud KMS Autokey.”
- customer-managed encryption keys secures Firestore From the official documentation: “To specify encryption compliance requirements for Firestore with MongoDB compatibility databases in your organization, use a [CMEK organization policy constraint](https://cloud.google.com/kms/docs/cmek-org-policy).”
- customer-managed encryption keys secures Spanner From the official documentation: “To learn how to use manually-created CMEKs to protect your Spanner resources, see [Secure a database with CMEK](/spanner/docs/use-cmek).”
- Dataflow works with Firestore From the official documentation: “Running a Firestore workload in Dataflow incurs costs for Firestore usage and Dataflow usage.”
- Dataflow depends on Identity and Access Management From the official documentation: “Dataflow uses Identity and Access Management (IAM) for authorization.”
- Identity and Access Management secures Dataflow From the official documentation: “To control access to Dataflow resources for users, groups, and service accounts in a project or organization, use Identity and Access Management (IAM).”
- Spanner depends on Identity and Access Management From the official documentation: “Spanner relies on IAM for identity management rather than managing user credentials within the database.”
How learners score on this topic
Last updated