Module 7: Deploying Applications

Looking for ‘Developing Applications with Google Cloud: Foundations Module 7 Answers’?

In this post, I provide complete, accurate, and detailed explanations for the answers to Module 7: Deploying Applications of Course 3: Developing Applications with Google Cloud: Foundations – 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!

Deploying Applications

Graded Assignment

1. Which of the following statements about continuous integration and delivery are accurate? Select two.

  • Continuous integration is a developer workflow in which developers frequently pull from the master and commit their changes into a feature branch in a source code repository. ✅
  • To benefit from continuous integration and delivery developers must use GitHub.
  • Continuous delivery is a workflow that is triggered when changes are pushed to the main branch in the repository. ✅
  • If all tests pass, builds generated from continuous integration in a feature branch can be released on a production environment.
  • Any continuous integration and delivery pipeline built on Google Cloud will automatically provide best security practices.

Explanation:

  • Continuous Integration (CI): Developers frequently pull the latest code from the main/master branch and commit their changes into feature branches. This ensures frequent testing and integration of code changes.
  • Continuous Delivery (CD): Involves automatically building, testing, and deploying changes when they are merged into the main branch. The goal is to ensure that code is always in a deployable state.

2. How can Cloud Build and Container Registry help you build a continuous integration and delivery pipeline? Select two.

  • You can install Cloud Build on Google Kubernetes Engine. GKE will autoscale depending on the number of builds.
  • With Cloud Build, the artifacts produced by each build step are persisted in the /workspace folder and can be used by the following build step. ✅
  • Each build step in a Cloud Build configuration specifies how to build an application container image.
  • When you commit code to a repository, you must start a build manually using a gcloud CLI command.
  • By using Container Registry and Cloud Build, you can create build pipelines that are automatically triggered when you commit code to a repository. ✅

Explanation:

  • Cloud Build creates isolated build steps, and artifacts are stored in /workspace to be shared between steps.
  • You can set up automatic triggers in Cloud Build so that when code is committed to a repository (e.g., GitHub, GitLab, Cloud Source Repositories), a build process is automatically initiated.

Related contents:

Module 2: Best Practices for Cloud Application Development
Module 3: Getting Started with Google Cloud Development
Module 4: Data Storage Options
Module 5: Handling Authentication and Authorization
Module 6: Adding Intelligence to Your Application
Module 8: Compute Options for Your Application
Module 9: Monitoring and Performance Tuning

You might also like:

Course 3:

Leave a Reply