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
Firestore
Topic in 6 exam domains
Also called: Firebase database, Firestore (Native Mode), Firestore database, Firestore in Native Mode, Firestore with MongoDB compatibility, Google Cloud Firestore
A Google Cloud database service whose database resources and configurations can be governed using policies and constraints.
Where this appears on the exam
4 objectives in 3 of 5 domains
~22% of exam
~25% of exam
Domain 3
Storing the data~20% of exam
Related topics
FoundationsThis topicWorks alongsideAppliedAccess ApprovalServiceAccess TransparencyServiceCloud Key Management ServiceServiceVPC Service ControlsServiceIdentity and Access ManagementServiceApplication Default CredentialsFeature
FirestoreService
Cloud RunServiceEventarcServiceCloud LoggingServiceBigQueryServiceCloud MonitoringServiceSpannerServiceCompute EngineServiceGoogle SecOpsServiceWorkflowsServiceGoogle Cloud StorageServiceCloud Run functionsServiceCloud SQLServicePoints to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
- Firestore depends on Application Default Credentials From the official documentation: “To authenticate to Firestore, set up Application Default Credentials.”
- Application Default Credentials works with Firestore From the official documentation: “To authenticate to Firestore, set up Application Default Credentials.”
- Identity and Access Management secures Firestore From the official documentation: “This page describes the IAM permissions and roles for Firestore.”
- Cloud Run works with Firestore From the official documentation: “The Cloud Run app stores the result in Firestore.”
- Cloud Run functions works with Firestore From the official documentation: “The Cloud Run function stores the result in Firestore.”
- Access Approval secures Firestore From the official documentation: “Secure Firestore with centralized Google Cloud governance encompassing Identity and Access Management,VPC Service Controls (VPC-SC), Access Transparency,<br>Access Approval, Cloud Monitoring, and Cloud Logging.”
- Access Transparency secures Firestore From the official documentation: “Secure Firestore with centralized Google Cloud governance encompassing Identity and Access Management,VPC Service Controls (VPC-SC), Access Transparency,<br>Access Approval, Cloud Monitoring, and Cloud Logging.”
- 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.”
- Cloud SQL is an alternative to Firestore From the official documentation: “Check your application code for reliance on local filesystems, and replace it with file storage on [Cloud Storage](/storage) or data storage such as [Firestore](/firestore) or [Cloud SQL](/sql).”
- Firestore works with VPC Service Controls From the official documentation: “Because Firestore with MongoDB compatibility is compliant with VPC Service Controls, you can use this domain in VPC Service Controls scenarios.”
- Cloud Key Management Service secures Firestore From the official documentation: “Instead of Google managing the encryption keys that protect your data, your Firestore with MongoDB compatibility database is protected using a key that you control and manage in [Cloud Key Management Service (Cloud KMS)](https://cloud.google.com/kms).”
- Cloud Logging works with Firestore From the official documentation: “Secure Firestore with centralized Google Cloud governance encompassing Identity and Access Management (IAM),VPC Service Controls (VPC-SC), Access Transparency,<br>Access Approval, Cloud Monitoring, and Cloud Logging.”
- 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 Run functions depends on Firestore From the official documentation: “Grant the Compute Engine service account (`your-project-number-developer.gserviceaccount.com`) the **Cloud Datastore User** role, so the newly deployed Cloud Run functions can access Firestore.”
- Eventarc works with Firestore From the official documentation: “Create event-driven architectures with Eventarc and Firestore”
- Firestore works with Workflows From the official documentation: “Workflows supports a connector for Firestore. Use the connector to integrate Firestore into your workflows:”
- VPC Service Controls secures Firestore From the official documentation: “Secure Firestore with centralized Google Cloud governance encompassing Identity and Access Management,VPC Service Controls (VPC-SC), Access Transparency,<br>Access Approval, Cloud Monitoring, and Cloud Logging.”
- 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 Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
- Application Default Credentials works with BigQuery From the official documentation: “Create a BigQuery client using application default credentials.”
- 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 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 Spanner From the official documentation: “To authenticate to Spanner, set up Application Default Credentials.”
- Application Default Credentials works with Google Cloud Storage From the official documentation: “To authenticate to Cloud Storage, 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 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 Eventarc From the official documentation: “Route Eventarc events to Cloud Run”
- 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.”
- 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.”
- 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 Cloud Run functions From the official documentation: “BigQuery supports external function calls through Cloud Run functions.”
- BigQuery works with Google Cloud Storage From the official documentation: “Load Cloud Storage data into 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.”
- 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 SQL works with Identity and Access Management From the official documentation: “This page describes how Cloud SQL is integrated with IAM .”
- Eventarc works with Workflows From the official documentation: “Route Eventarc events to Workflows”
- Application Default Credentials works with Workflows From the official documentation: “To authenticate to Workflows, set up Application Default Credentials.”
- 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 works with Workflows From the official documentation: “Route Workflows events to 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 works with Cloud Key Management Service From the official documentation: “To authenticate to Cloud KMS, set up Application Default Credentials.”
- Application Default Credentials works with Cloud Run From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
- Application Default Credentials secures Cloud Run functions From the official documentation: “To authenticate to Cloud Run functions, 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 Logging depends on Application Default Credentials From the official documentation: “To authenticate to Logging, set up Application Default Credentials.”
- Cloud Monitoring works with Spanner From the official documentation: “Monitor Spanner metrics using Cloud Monitoring.”
- Cloud Run is an alternative to Cloud Run functions From the official documentation: “To create remote functions, you must [grant required roles](/bigquery/docs/remote-functions#grant_permission_on_function) to Cloud Run functions or Cloud Run.”
- Cloud Run functions works with Workflows From the official documentation: “Use Workflows with Cloud Run and Cloud Run functions tutorial”
- Eventarc depends on Application Default Credentials From the official documentation: “To authenticate to Eventarc, set up Application Default Credentials.”
- Identity and Access Management secures BigQuery From the official documentation: “Access to BigQuery data from AlloyDB is managed through IAM.”
How learners score on this topic
Last updated