Module 3: Calling and Connecting Cloud Run Functions

Looking for ‘Developing Applications with Cloud Run Functions on Google Cloud Module 3 Answers’?

In this post, I provide complete, accurate, and detailed explanations for the answers to Module 3: Calling and Connecting Cloud Run Functions of Course 5: Developing Applications with Cloud Run Functions on Google Cloud – Preparing for Google Cloud Certification: Cloud Developer Professional Certificate

Whether you’re preparing for quizzes or brushing up on your knowledge, these insights will help you master the concepts effectively. Let’s dive into the correct answers and detailed explanations for each question!

Quiz 2

Graded Assignment

1. Which of these statements about Cloud Run functions triggers are correct? Select three.

  • Triggers are specified during function deployment. ✅
  • Multiple functions can be triggered by the same trigger settings. ✅
  • A function can be bound to multiple triggers at the same time.
  • An event trigger reacts to cloud events. ✅

Explanation:

  • Triggers are specified during deployment → You define triggers while deploying a function.
  • Multiple functions can share the same trigger → The same event can trigger multiple functions.
  • Event triggers react to cloud events → Event-driven functions listen to changes in cloud services.

2. Which of these statements about Workflows are correct? Select three.

  • Workflows is serverless. ✅
  • In a workflow, data cannot be shared between steps.
  • Workflows can combine services or functions hosted on Cloud Run. ✅
  • A workflow step can be defined to make an HTTP call to a URL. ✅

Explanation:

  • Workflows is fully managed & serverless → No infrastructure management required.
  • Can orchestrate Cloud Run services → Workflows integrate various services, including Cloud Run.
  • Can make HTTP calls → Workflows can call APIs, retrieve data, and process responses.

3. What are two reasons for using Serverless VPC Access?

  • To enable Cloud Run functions to access external HTTP endpoints.
  • To connect Cloud Run functions to internal resources in a VPC network. ✅
  • To expose requests and responses to and from a VPC network to the internet.
  • To send requests and receive responses using internal DNS and IP addresses. ✅

Explanation:

  • Allows Cloud Run to access internal VPC resources securely.
  • Supports internal DNS & IP resolution within the VPC.

4. An HTTP trigger: (Select two)

  • Enables a function to respond to events from cloud infrastructure.
  • Does not support the DELETE HTTP request method.
  • Generates a URL when it is assigned to a function.  ✅
  • Enables a function to respond to HTTP requests.  ✅

Explanation:

  • Each HTTP function gets a unique URL for direct invocation.
  • HTTP triggers handle HTTP(S) requests, making them ideal for APIs & webhooks.

Related contents:

Module 2: Introduction to Cloud Run Functions
Module 4: Securing Cloud Run Functions
Module 5: Integrating with Cloud Databases
Module 6: Best Practices for Functions

You might also like:

Course 3:

Leave a Reply