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
AI-assisted troubleshooting
Topic in 1 exam domain
Also called: troubleshooting with AI assistance
A preview capability providing performance anomaly detection, root cause and situation analysis, and fix recommendations.
Where this appears on the exam
1 objective in 1 of 5 domains
Related topics
FoundationsBuilding blocksBuilding blocksBuilding blocksThis topicAlloyDB for PostgreSQLServiceIdentity and Access ManagementServiceCloud LoggingServiceGemini Cloud AssistServiceCloud RunServiceCloud StorageServiceCloud SQLServiceBigQueryServiceCloud SQL Enterprise Plus editionFeature
AI-assisted troubleshootingFeature
Query insightsFeaturePoints to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
- AI-assisted troubleshooting is part of Cloud SQL From the official documentation: “The following limitations apply to AI-assisted troubleshooting in Cloud SQL:”
- AI-assisted troubleshooting is part of AlloyDB for PostgreSQL From the official documentation: “The following limitations apply to AI-assisted troubleshooting in AlloyDB:”
- AI-assisted troubleshooting is part of Cloud SQL Enterprise Plus edition From the official documentation: “Cloud SQL Enterprise Plus edition provides the following observability enhancements: - **Query insights**: advanced query performance diagnostics and filtering with up to 30-day metric retention, up to 1 MB query length limit, and a 200 query plan sample maximum. - **Enhanced…”
- AI-assisted troubleshooting depends on Gemini Cloud Assist From the official documentation: “For Cloud SQL Enterprise edition instances, troubleshooting with AI assistance is only available if you enable Gemini Cloud Assist.”
- AI-assisted troubleshooting works with Gemini Cloud Assist From the official documentation: “You can use the AI-assisted troubleshooting tools of AlloyDB and [Gemini Cloud Assist](/cloud-assist/overview) to [troubleshoot slow queries](#troubleshoot-slow-queries) and [troubleshoot high database load](#troubleshoot-high-database-load).”
- BigQuery is an alternative to Cloud Storage From the official documentation: “The `import_result_sink` must be a Cloud Storage path or a BigQuery table.”
- BigQuery works with Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
- BigQuery works with Cloud Storage From the official documentation: “External BigQuery data source backed by Cloud Storage”
- BigQuery works with Cloud SQL From the official documentation: “Add credentials to connect BigQuery to Cloud SQL.”
- Cloud Run works with Cloud SQL From the official documentation: “Learn how to connect to Cloud SQL from Cloud Run”
- Cloud SQL works with Cloud Storage From the official documentation: “When ingesting data from Cloud SQL, data is first staged to a Cloud Storage bucket.”
- Cloud SQL Enterprise Plus edition is part of Cloud SQL From the official documentation: “For Cloud SQL Enterprise Plus edition instances:”
- Cloud Run works with Cloud Storage From the official documentation: “Route Cloud Storage events to Cloud Run”
- Cloud SQL works with Identity and Access Management From the official documentation: “This page describes how Cloud SQL is integrated with IAM .”
- Cloud Logging works with Cloud SQL From the official documentation: “Cloud SQL uses Cloud Logging.”
- Cloud Storage works with Identity and Access Management From the official documentation: “To learn how to use IAM with Cloud Storage, see [Using IAM Permissions](/storage/docs/access-control/using-iam-permissions).”
- Query insights is part of Cloud SQL From the official documentation: “To disable query insights for a Cloud SQL instance by using the Google Cloud console, follow these steps:”
- Cloud Logging works with Cloud Storage From the official documentation: “Cloud Storage writes various log entries to Cloud Logging in the Google Cloud console.”
- Cloud SQL works with Gemini Cloud Assist From the official documentation: “To use Gemini Cloud Assist with Cloud SQL, do the following:”
- Identity and Access Management secures BigQuery From the official documentation: “Access to BigQuery data from AlloyDB is managed through IAM.”
- Identity and Access Management secures Cloud Storage From the official documentation: “Cloud Storage uses Identity and Access Management (IAM) for authorization.”
- AlloyDB for PostgreSQL works with BigQuery From the official documentation: “BigQuery AlloyDB federation lets BigQuery query data residing in AlloyDB in real time without copying or moving the data.”
- AlloyDB for PostgreSQL works with Cloud Storage From the official documentation: “AlloyDB supports importing and exporting compressed `.gz` files from Cloud Storage.”
- 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.”
- Query insights is part of AlloyDB for PostgreSQL From the official documentation: “To help you analyze and improve query performance of the databases,<br>AlloyDB for PostgreSQL provides a Query Insights tool.”
- AlloyDB for PostgreSQL works with Cloud Run From the official documentation: “The Cloud Run service can connect to the AlloyDB instance.”
- AlloyDB for PostgreSQL is an alternative to Cloud SQL From the official documentation: “The sample code uses Cloud SQL as the vector database, whereas this reference architecture uses AlloyDB for PostgreSQL.”
- AlloyDB for PostgreSQL works with Gemini Cloud Assist From the official documentation: “You can use Gemini Cloud Assist to help you monitor and troubleshoot your AlloyDB resources.”
- BigQuery works with Cloud Run From the official documentation: “You can then use Cloud Run to transcode data present in the bucket and move it to BigQuery.”
- BigQuery works with Gemini Cloud Assist From the official documentation: “To use Gemini Cloud Assist to help you [troubleshoot a query failure or performance issue](/bigquery/docs/use-cloud-assist#analyze_jobs), do the following: 1. In the Google Cloud console, go to the **BigQuery** page.”
- Cloud Logging works with Cloud Run From the official documentation: “Cloud Logging captures, stores, and analyzes Cloud Run logs.”
- Cloud Run works with Identity and Access Management From the official documentation: “Cloud Run also offers the ability to control access to a service with Identity and Access Management (IAM).”
- AlloyDB for PostgreSQL works with Cloud Logging From the official documentation: “AlloyDB processes user-generated audit logs asynchronously before securely forwarding them to Cloud Logging.”
- AlloyDB for PostgreSQL works with Identity and Access Management From the official documentation: “This page explains the process of logging into an AlloyDB for PostgreSQL instance using an account prepared with Identity and Access Management (IAM).”
- BigQuery depends on Cloud Storage From the official documentation: “BigQuery relies on Cloud Storage for staging file data and supports reading from and writing to several other sources and Google Cloud services.”
- Cloud Logging is an alternative to Cloud Storage From the official documentation: “When you specify your own service account for builds, you must store your build logs either in Cloud Logging or in a user-created Cloud Storage bucket.”
- Cloud Logging works with Gemini Cloud Assist From the official documentation: “Cloud Logging sends the text of the log entry to Gemini Cloud Assist with a prompt to summarize the contents of the log entry.”
- Cloud Run works with Gemini Cloud Assist From the official documentation: “The following table provide some example prompts for using Gemini Cloud Assist with Cloud Run.”
- Cloud SQL depends on Cloud Storage From the official documentation: “When ingesting data from Cloud SQL, data is first staged to a Cloud Storage bucket.”
- Cloud SQL Enterprise Plus edition works with Cloud Storage From the official documentation: “If your Cloud SQL Enterprise edition instance stores transaction logs for PITR on disk, then starting the upgrade process to Cloud SQL Enterprise Plus edition switches the storage location of these logs to Cloud Storage.”
- Cloud Storage works with Gemini Cloud Assist From the official documentation: “When you use Gemini Cloud Assist, you can enter prompts about how Cloud Storage works in general, and when you enable a Storage Intelligence subscription, you can enter prompts about specific buckets and objects.”
- Gemini Cloud Assist depends on Identity and Access Management From the official documentation: “To support questions and requests about your Google Cloud resources, Gemini Cloud Assist needs the appropriate Identity and Access Management (IAM) permissions for those resources.”
- Identity and Access Management secures Cloud Run From the official documentation: “Cloud Run services are secured by IAM.”
- Query insights is part of Cloud SQL Enterprise Plus edition From the official documentation: “Cloud SQL Enterprise Plus edition provides the following observability enhancements: - **Query insights**: advanced query performance diagnostics and filtering with up to 30-day metric retention, up to 1 MB query length limit, and a 200 query plan sample maximum.”
How learners score on this topic
Last updated