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
Cloud Functions
Topic in 4 exam domains
Also called: Cloud Function (2nd gen), Cloud Functions for Firebase, Google Cloud Functions, HTTP Cloud Functions
A serverless execution environment used to run ingestion scripts for Armis Vulnerabilities logs.
Where this appears on the exam
4 subdomains in 3 of 5 domains
Related topics
FoundationsBuilding blocksBuilding blocksThis topicWorks alongsideAppliedApplication Default CredentialsFeatureIdentity and Access ManagementServiceVPC Service ControlsServicePub/SubServiceCloud StorageServiceIAMServiceDataflowServiceFirestoreServiceBigQueryServiceCloud RunService
Cloud FunctionsService
ApigeeServiceCloud Audit LogsFeatureCloud LoggingServiceCloud SchedulerServiceWorkflowsServiceCloud SQLServiceSecret ManagerServiceenvironment variablesConceptPoints to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
- Cloud Functions works with Pub/Sub From the official documentation: “Demonstrates how to interact with Pub/Sub from Cloud Functions.”
- Application Default Credentials configures Cloud Functions From the official documentation: “To authenticate to Cloud Run functions, set up Application Default Credentials.”
- Application Default Credentials secures Cloud Functions From the official documentation: “To authenticate to Cloud Run functions, set up Application Default Credentials.”
- Cloud Functions depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Run functions, set up Application Default Credentials.”
- Cloud Functions works with Cloud Storage From the official documentation: “You can use Cloud Run functions to launch Workflows in response to Pub/Sub events or file changes in Cloud Storage.”
- Cloud Functions works with Firestore From the official documentation: “With Cloud Functions, you can deploy Node.js code to handle events triggered by changes in your Firestore database.”
- Apigee works with Cloud Functions From the official documentation: “Apigee supports using [Google OAuth tokens](https://developers.google.com/identity/protocols/oauth2) or [OpenID Connect tokens](https://developers.google.com/identity/protocols/oauth2/openid-connect) to authenticate with Google services such as [Cloud…”
- Cloud Audit Logs works with Cloud Functions From the official documentation: “This sample demonstrates how to process Cloud Audit Logs using Cloud Functions.”
- Cloud Functions works with Cloud Logging From the official documentation: “Code running in Google Cloud Functions itself writes log entries to // Cloud Logging.”
- Cloud Functions depends on Cloud Run From the official documentation: “Cloud Run functions represent the next evolution of Cloud Functions, offering an event-driven programming model with enhanced control and scalability, leveraging the Cloud Run serverless platform.”
- Cloud Functions works with Cloud Scheduler From the official documentation: “You can use Cloud Run functions with Cloud Scheduler for workflows that require the calculation of time-based parameters.”
- Cloud Functions works with Workflows From the official documentation: “Learn how to use Workflows to link two public HTTP services (using Cloud Functions), an external REST API, and a private Cloud Run service together.”
- environment variables is part of Cloud Functions From the official documentation: “Demonstrates how to use environment variables within a Cloud Function.”
- IAM secures Cloud Functions From the official documentation: “Use IAM to Secure and Control Access Learn how to configure security for your functions.”
- Identity and Access Management secures Cloud Functions From the official documentation: “You use [Identity and Access Management (IAM)](/iam) to authorize identities to perform administrative actions on functions created using the [Cloud Functions v2 API](/functions/docs/apis)—for example, using `gcloud functions`, the REST API, or Terraform.”
- 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 Storage From the official documentation: “Sample to load Avro data from Cloud Storage into a new BigQuery table”
- Application Default Credentials secures BigQuery From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
- BigQuery works with Cloud SQL From the official documentation: “Add credentials to connect BigQuery to Cloud SQL.”
- BigQuery works with Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
- Cloud SQL works with Cloud Storage From the official documentation: “Exports data from a Cloud SQL instance to a Cloud Storage bucket as a SQL dump or CSV file.”
- Cloud Run depends on Pub/Sub From the official documentation: “Cloud Run function triggered by Pub/Sub to fetch HYPR MFA logs and write to GCS.”
- Application Default Credentials works with Pub/Sub From the official documentation: “To authenticate to Pub/Sub, set up Application Default Credentials.”
- Dataflow works with Pub/Sub From the official documentation: “Pub/Sub notifies Dataflow about the upload.”
- Application Default Credentials works with Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
- Application Default Credentials secures Pub/Sub 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”
- Cloud Run works with Cloud Scheduler From the official documentation: “Create a Cloud Scheduler job that triggers the Cloud Run service daily.”
- Application Default Credentials works with BigQuery From the official documentation: “Create a BigQuery client using application default credentials.”
- Cloud Storage works with Dataflow From the official documentation: “Write from Dataflow to Cloud Storage”
- Pub/Sub depends on Application Default Credentials From the official documentation: “To authenticate to Pub/Sub, 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.”
- Application Default Credentials works with Firestore From the official documentation: “To authenticate to Firestore, set up Application Default Credentials.”
- BigQuery depends on Application Default Credentials From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
- Cloud Run works with Cloud SQL From the official documentation: “Connecting from Cloud Run (fully managed) to Cloud SQL”
- Cloud Scheduler works with Pub/Sub From the official documentation: “Create a Pub/Sub topic to set up as your Cloud Scheduler job target.”
- Firestore depends on Application Default Credentials From the official documentation: “To authenticate to Firestore, set up Application Default Credentials.”
- Application Default Credentials secures Dataflow From the official documentation: “To authenticate to Dataflow, set up Application Default Credentials.”
- BigQuery works with Pub/Sub From the official documentation: “createBigQuerySubscription creates a Pub/Sub subscription that exports messages to BigQuery.”
- 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 Scheduler works with Workflows From the official documentation: “[Schedule a workflow using Cloud Scheduler](/workflows/docs/schedule-workflow)”
- Cloud Storage 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.”
- Pub/Sub works with Secret Manager From the official documentation: “Receive notifications via Pub/Sub when Secret Manager resources change.”
- Application Default Credentials works with Dataflow From the official documentation: “To authenticate to Dataflow, set up Application Default Credentials.”
- Application Default Credentials works with Secret Manager From the official documentation: “To authenticate to Secret Manager, set up Application Default Credentials.”
- Cloud Audit Logs works with Cloud Storage From the official documentation: “This page provides supplemental information for using [Cloud Audit Logs](/logging/docs/audit) with Cloud Storage.”
- Cloud Audit Logs works with VPC Service Controls From the official documentation: “VPC Service Controls integrate with Cloud Audit Logs to monitor access to the control plane.”
- Cloud Logging works with Cloud SQL From the official documentation: “Database Migration Service and Cloud SQL use Cloud Logging.”
- 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 Storage works with Pub/Sub From the official documentation: “| **Google Cloud** | Cloud Storage | Pub/Sub |”
- Dataflow depends on Application Default Credentials From the official documentation: “To authenticate to Dataflow, 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.”
- Application Default Credentials configures BigQuery From the official documentation: “To authenticate to BigQuery, 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 Firestore From the official documentation: “To authenticate to Firestore, set up Application Default Credentials.”
- Application Default Credentials secures IAM From the official documentation: “To authenticate to IAM, set up Application Default Credentials.”
- Application Default Credentials works with Workflows From the official documentation: “To authenticate to Workflows, set up Application Default Credentials.”
- BigQuery works with Cloud Audit Logs From the official documentation: “Cloud Audit Logs maintain a record of Google Cloud events, including BigQuery events.”
- 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.”
How learners score on this topic
Last updated