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
Gemini Enterprise
Topic in 1 exam domain
- Gemini Enterprise · Service
- Gemini Enterprise · Feature
Also called: Discovery Engine, discoveryengine, Gemini Enterprise Standard edition, Gemini Enterprise web app, Google Cloud Gemini Enterprise, Google Gemini Enterprise
An enterprise search and AI platform that connects to various data sources to provide federated search across connected repositories.
Where this appears on the exam
1 objective in 1 of 5 domains
Related topics
FoundationsThis topicWorks alongsideAppliedVPC Service ControlsServiceIdentity and Access ManagementServiceApplication Default CredentialsFeatureCloud MonitoringServiceCompute EngineServiceCloud RunServiceBigQueryService
Gemini EnterpriseService
Cloud StorageServiceSensitive Data ProtectionServiceCloud Run functionsServiceDataflowServiceKnowledge CatalogServiceGKEServiceCloud LoggingServicePrivate Service ConnectFeatureAccess TransparencyServiceAlloyDB for PostgreSQLServiceCloud SQLServicePoints to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
- Application Default Credentials secures Gemini Enterprise From the official documentation: “To authenticate to Gemini Enterprise, set up Application Default Credentials.”
- BigQuery works with Gemini Enterprise From the official documentation: “The following table compares the two ways that you can import BigQuery data into Gemini Enterprise data stores.”
- Gemini Enterprise depends on Application Default Credentials From the official documentation: “To authenticate to Gemini Enterprise, set up Application Default Credentials.”
- VPC Service Controls secures Gemini Enterprise From the official documentation: “The API for Gemini Enterprise can be protected by VPC Service Controls and the product can be used normally inside service perimeters.”
- Gemini Enterprise works with Private Service Connect From the official documentation: “To configure private connectivity to Gemini Enterprise, you must route Google Cloud API traffic through a Private Service Connect (PSC) endpoint.”
- Identity and Access Management secures Gemini Enterprise From the official documentation: “Gemini Enterprise uses Identity and Access Management (IAM) for authorization.”
- Access Transparency works with Gemini Enterprise From the official documentation: “This page provides an overview of the support that [Access Transparency](/assured-workloads/access-transparency/docs/overview) provides for Gemini Enterprise.”
- AlloyDB for PostgreSQL works with Gemini Enterprise From the official documentation: “You can connect your AlloyDB instance to Gemini Enterprise, enabling live access to your data.”
- Cloud Logging works with Gemini Enterprise From the official documentation: “By default, Gemini Enterprise sends Cloud Logging data to the `_Default` bucket.”
- Cloud Monitoring works with Gemini Enterprise From the official documentation: “Metrics generated by your Gemini Enterprise app are stored in Cloud Monitoring in your Google Cloud project, and their retention is governed by Cloud Monitoring.”
- Cloud Storage works with Gemini Enterprise From the official documentation: “Discovery Engine service uploads documents and user events from Cloud Storage and BigQuery, reports results to the customer Cloud Storage bucket, writes logs to customer projects using Cloud Logging, and writes and reads metrics for customer using Cloud Monitoring.”
- Compute Engine works with Gemini Enterprise From the official documentation: “This page describes how to create a data store and connect Compute Engine to Gemini Enterprise.”
- Gemini Enterprise works with Sensitive Data Protection From the official documentation: “Optional: In the **Sensitive Data Protection policy** section, attach an existing [Sensitive Data Protection](https://cloud.google.com/sensitive-data-protection/docs/sensitive-data-protection-overview) policy to inspect and de-identify data that Gemini Enterprise retrieves…”
- Application Default Credentials works with Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
- Sensitive Data Protection depends on Application Default Credentials From the official documentation: “To authenticate to Sensitive Data Protection, 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.”
- BigQuery works with Sensitive Data Protection From the official documentation: “Uses the Data Loss Prevention API to analyze BigQuery data.”
- Dataflow depends on Application Default Credentials From the official documentation: “To authenticate to Dataflow, set up Application Default Credentials.”
- 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”
- Application Default Credentials works with BigQuery From the official documentation: “Create a BigQuery client using application default credentials.”
- Application Default Credentials secures Sensitive Data Protection From the official documentation: “To authenticate to Sensitive Data Protection, set up Application Default Credentials.”
- BigQuery works with Dataflow From the official documentation: “Read from BigQuery to Dataflow”
- 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”
- Application Default Credentials works with Dataflow From the official documentation: “To authenticate to Dataflow, set up Application Default Credentials.”
- Application Default Credentials works with Compute Engine From the official documentation: “To authenticate to Compute Engine, set up Application Default Credentials.”
- VPC Service Controls secures BigQuery From the official documentation: “BigQuery data is protected with VPC Service Controls”
- Application Default Credentials secures Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
- Knowledge Catalog depends on Application Default Credentials From the official documentation: “To authenticate to Knowledge Catalog, set up Application Default Credentials.”
- Cloud Storage depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
- BigQuery works with Knowledge Catalog From the official documentation: “Some Knowledge Catalog functionalities trigger job execution using BigQuery.”
- 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 works with Private Service Connect From the official documentation: “You can use Private Service Connect to connect to a Cloud SQL instance from multiple VPC networks.”
- 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.”
- Cloud Run works with Cloud Storage From the official documentation: “Route Cloud Storage events to Cloud Run”
- Application Default Credentials works with Cloud Run functions From the official documentation: “To authenticate to Cloud Run functions, set up Application Default Credentials.”
- Cloud Run functions depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Run functions, 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.”
- Application Default Credentials works with Sensitive Data Protection From the official documentation: “To authenticate to Sensitive Data Protection, set up Application Default Credentials.”
- Cloud Logging works with GKE From the official documentation: “Enable Cloud Logging on GKE Clusters”
- Cloud Run functions works with Cloud Storage From the official documentation: “Set up functions in response to events in Cloud Storage:”
- Compute Engine is an alternative to GKE From the official documentation: “To use TPU7x, you can use Google Kubernetes Engine (GKE) or Compute Engine.”
- BigQuery works with Cloud Run functions From the official documentation: “BigQuery supports external function calls through Cloud Run functions.”
- Cloud Monitoring depends on Application Default Credentials From the official documentation: “To authenticate to Monitoring, set up Application Default Credentials.”
- 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 Monitoring works with GKE From the official documentation: “Enable Cloud Monitoring on GKE Clusters”
- Cloud SQL works with Identity and Access Management From the official documentation: “This page describes how Cloud SQL is integrated with IAM .”
- Cloud SQL works with Knowledge Catalog From the official documentation: “You can use Knowledge Catalog to organize and enrich the metadata of Cloud SQL resources.”
- Cloud Storage works with Dataflow From the official documentation: “Write from Dataflow to Cloud Storage”
- Cloud Storage works with Sensitive Data Protection From the official documentation: “Uses the Data Loss Prevention API to analyze a file on GCS.”
- Cloud Logging works with Cloud SQL From the official documentation: “Cloud SQL uses Cloud Logging.”
- Cloud Run depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
- Cloud Run is an alternative to GKE From the official documentation: “The app uses Cloud SQL, Vertex AI, and either Google Kubernetes Engine (GKE) or Cloud Run.”
- Cloud SQL depends on Compute Engine From the official documentation: “Cloud SQL uses Compute Engine virtual machines (VMs) with persistent storage disks.”
- Application Default Credentials secures Dataflow From the official documentation: “To authenticate to Dataflow, set up Application Default Credentials.”
- Application Default Credentials secures Knowledge Catalog From the official documentation: “To authenticate to Knowledge Catalog, set up Application Default Credentials.”
How learners score on this topic
Last updated