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
Google Cloud Marketplace
Topic in 2 exam domains
Google Cloud's online store where partners publish and customers discover and deploy integrated cloud products and services.
Where this appears on the exam
1 objective in 1 of 5 domains
~15% of exam
Related topics
This topicWorks alongsideBuilds on theseBuilds on theseApplied
Google Cloud MarketplaceService
Deployment ManagerServiceApplication Default CredentialsFeatureBigQuery sharingFeatureCloud MonitoringServiceIdentity and Access ManagementServiceCloud LoggingServiceCompute EngineServicePub/SubServiceBigQueryServiceGKEServiceDataflowServiceCloud RunServicePoints to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
- BigQuery sharing works with Google Cloud Marketplace From the official documentation: “You can discover Cloud Marketplace-integrated commercial listings on both BigQuery sharing and Cloud Marketplace.”
- Compute Engine works with Google Cloud Marketplace From the official documentation: “*Google Cloud Marketplace* lets you click to install MySQL onto a Compute Engine instance.”
- Cloud Monitoring works with Google Cloud Marketplace From the official documentation: “Some virtual machine (VM) products from Cloud Marketplace might include Cloud Monitoring, which collects metrics, events, and metadata from your deployment.”
- Deployment Manager works with Google Cloud Marketplace From the official documentation: “The advantage of Google Cloud Marketplace is that it handles configuration and template creation for you and you just deploy the solution through a button in the Google Cloud console. This greatly simplifies creating deployments on Deployment Manager.”
- GKE works with Google Cloud Marketplace From the official documentation: “You can select and deploy container-based applications from Google Cloud Marketplace to your Google Kubernetes Engine cluster.”
- Google Cloud Marketplace works with Pub/Sub From the official documentation: “Integrate with Pub/Sub to receive notifications from Cloud Marketplace, such as when a user signs up for your product.”
- 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 Pub/Sub From the official documentation: “To authenticate to Pub/Sub, 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.”
- Application Default Credentials secures Pub/Sub From the official documentation: “To authenticate to Pub/Sub, set up Application Default Credentials.”
- Pub/Sub depends on Application Default Credentials From the official documentation: “To authenticate to Pub/Sub, 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.”
- Application Default Credentials works with Compute Engine From the official documentation: “To authenticate to Compute Engine, 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 Run works with Pub/Sub From the official documentation: “Route Cloud Pub/Sub events to Cloud Run”
- Dataflow works with Pub/Sub From the official documentation: “Pub/Sub notifies Dataflow about the upload.”
- 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 Pub/Sub From the official documentation: “To keep audit logs for a longer period of time or to use more powerful search capabilities, you can route copies of your audit logs to Cloud Storage, BigQuery, or Pub/Sub.”
- Cloud Logging works with GKE From the official documentation: “Enable Cloud Logging on GKE Clusters”
- Compute Engine is an alternative to GKE From the official documentation: “To use TPU7x, you can use Google Kubernetes Engine (GKE) or Compute Engine.”
- Cloud Monitoring depends on Application Default Credentials From the official documentation: “To authenticate to Monitoring, set up Application Default Credentials.”
- Cloud Monitoring works with GKE From the official documentation: “Enable Cloud Monitoring on GKE Clusters”
- Cloud Run depends on Pub/Sub From the official documentation: “Create a Pub/Sub topic that Cloud Scheduler will publish to and the Cloud Run function will subscribe to.”
- BigQuery works with Pub/Sub From the official documentation: “createBigQuerySubscription creates a Pub/Sub subscription that exports messages to BigQuery.”
- 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.”
- Application Default Credentials secures Dataflow From the official documentation: “To authenticate to Dataflow, 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 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 Logging works with Pub/Sub From the official documentation: “Pub/Sub writes various log entries to Cloud Logging in the Google Cloud console.”
- Cloud Monitoring works with Dataflow From the official documentation: “Dataflow is fully integrated with Cloud Monitoring.”
- Identity and Access Management secures BigQuery From the official documentation: “Access to BigQuery data from AlloyDB is managed through IAM.”
- 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.”
- Cloud Logging works with Compute Engine From the official documentation: “Compute Engine sends you Cloud Logging events for scheduled, started, or completed maintenance.”
- Cloud Monitoring works with Pub/Sub From the official documentation: “Use Cloud Monitoring and Pub/Sub to set up custom monitoring and alerting policies for exported logs.”
- GKE depends on Compute Engine From the official documentation: “For example, GKE deploys clusters on Compute Engine VMs.”
- GKE works with Pub/Sub From the official documentation: “Route Cloud Pub/Sub events to GKE”
- Application Default Credentials secures Cloud Monitoring From the official documentation: “To authenticate to Monitoring, set up Application Default Credentials.”
- Application Default Credentials works with GKE From the official documentation: “To authenticate to GKE, set up Application Default Credentials.”
- 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.”
- 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 works with Cloud Run From the official documentation: “Cloud Logging captures, stores, and analyzes Cloud Run logs.”
- Cloud Logging works with Dataflow From the official documentation: “Information stored in [Cloud Logging](/logging/docs/region-support) is primarily generated by the code in your Dataflow program.”
- Cloud Monitoring works with Cloud Run From the official documentation: “Cloud Monitoring records metrics regarding the execution of Cloud Run.”
- Cloud Monitoring works with Compute Engine From the official documentation: “Many Google services like Compute Engine send telemetry to Cloud Monitoring.”
- Cloud Run works with GKE From the official documentation: “Leverage Google Kubernetes Engine (GKE) and Cloud Run to deploy applications to the Google Cloud, optimizing costs, performance, and management overhead.”
- 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).”
- Dataflow depends on Compute Engine From the official documentation: “When you run your pipeline on the Dataflow service, Dataflow creates Compute Engine instances to run your pipeline code.”
- Deployment Manager configures Compute Engine From the official documentation: “This guide has you use the Cloud Deployment Manager templates that are provided by Google Cloud to deploy the Compute Engine virtual machines (VMs), which ensures that the VMs meet SAP supportability requirements and conform to current best practices.”
- Identity and Access Management depends on Application Default Credentials From the official documentation: “To authenticate to IAM, set up Application Default Credentials.”
- Identity and Access Management secures Compute Engine From the official documentation: “Compute Engine uses Identity and Access Management (IAM) for authorization.”
- Identity and Access Management secures Pub/Sub From the official documentation: “Pub/Sub uses Identity and Access Management (IAM) for authorization.”
- Application Default Credentials configures BigQuery From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
- Application Default Credentials works with Cloud Logging From the official documentation: “To authenticate to Logging, set up Application Default Credentials.”
How learners score on this topic
Last updated