Module 5: Integrating with Cloud Databases
Looking for ‘Developing Applications with Cloud Run Functions on Google Cloud Module 5 Answers’?
In this post, I provide complete, accurate, and detailed explanations for the answers to Module 5: Integrating with Cloud Databases 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 4
Graded Assignment
1. Which three statements about using environment variables with Cloud Run functions are correct? Environment variables:
- Are provided during function deployment.
- Can be shared and used by multiple functions.
- Can be stored in a YAML file, whose filename can be provided during function deployment.
- Are key-value pairs that are accessed by the function code at runtime.
- Cannot be added, updated, or removed.
Explanation:
- Environment variables allow configuration without modifying code.
- They are set during deployment and accessed as key-value pairs.
- Cloud Run supports loading environment variables from a YAML file.
2. Which statements about triggering Cloud Run functions from Firestore database events are correct? Select two.
- A function cannot be triggered when a Firestore document is deleted.
- A function can be triggered when a Firestore document is created, updated, or deleted.
- A function can be triggered when a specific field in a Firestore document is changed.
- To trigger a function, you must specify an event type and the document path.
- A function can only be triggered on changes to an individual Firestore document.
Explanation:
- Firestore supports event-driven triggers for document changes (create, update, delete).
- Event types and document paths must be explicitly defined for the function to listen for changes.
3. What are two methods of making a secret available to a cloud function?
- Provide the secret name and value as query parameters to the function.
- Provide the secret as an environment variable when deploying the function.
- Mount the secret as a volume so that the function can access the secret from a file.
- Secrets cannot be accessed from Cloud Run functions.
Explanation:
Cloud Run integrates with Secret Manager, allowing secrets to be:
- Injected as environment variables.
- Mounted as a volume, where the function reads from a file.
Related contents:
Module 2: Introduction to Cloud Run Functions
Module 3: Calling and Connecting Cloud Run Functions
Module 4: Securing Cloud Run Functions
Module 6: Best Practices for Functions
You might also like:
Course 3:
