Google Professional Cloud DevOps Engineer Question 210
Select 3Google Cloud PlatformYou are deploying a new version of an application using a CI/CD pipeline in Google Cloud. To ensure the new version does not introduce errors, you decide to test it in a staging environment before promoting it to production. Which steps should you include in your pipeline to validate the new version effectively?
- A
Execute unit and integration tests as part of the build process.
- B
Deploy the new version to the staging environment and run automated end-to-end tests.
- C
Skip testing in the staging environment and promote the new version directly to production.
- D
Run load testing in the staging environment to evaluate performance under stress.
- E
Manually verify the staging environment after automated tests pass.
Show answer and explanation
Correct answers: A, B, D
Explanation
Validating a new application version in a CI/CD pipeline involves multiple layers of testing. Unit and integration tests ensure basic functionality, while end-to-end and load testing in a staging environment validate the application's behavior under more realistic conditions. Skipping these steps or relying solely on manual testing increases the risk of defects and reduces the reliability of the deployment process.
- A. Correct.
Executing unit and integration tests as part of the build process helps catch issues early in the pipeline, ensuring that the new version is functionally correct before deployment.
- B. Correct.
Deploying to a staging environment and running automated end-to-end tests is critical for validating the application in an environment that mimics production.
- C. Incorrect.
Skipping testing and directly promoting to production increases the risk of introducing defects or breaking functionality, which is not a recommended practice.
- D. Correct.
Running load testing in staging helps evaluate how the application performs under stress and ensures it can handle expected traffic levels before being promoted to production.
- E. Incorrect.
While manual verification can be useful, it is not a substitute for automated testing and is typically less efficient. Automation should be prioritized.