Welcome to ExamTopics
ExamTopics Logo
- Expert Verified, Online, Free.
exam questions

Exam Professional Cloud DevOps Engineer All Questions

View all questions & answers for the Professional Cloud DevOps Engineer exam

Exam Professional Cloud DevOps Engineer topic 1 question 137 discussion

Actual exam question from Google's Professional Cloud DevOps Engineer
Question #: 137
Topic #: 1
[All Professional Cloud DevOps Engineer Questions]

You are developing reusable infrastructure as code modules. Each module contains integration tests that launch the module in a test project. You are using GitHub for source control. You need to continuously test your feature branch and ensure that all code is tested before changes are accepted. You need to implement a solution to automate the integration tests. What should you do?

  • A. Use a Jenkins server for CI/CD pipelines. Periodically run all tests in the feature branch.
  • B. Ask the pull request reviewers to run the integration tests before approving the code.
  • C. Use Cloud Build to run the tests. Trigger all tests to run after a pull request is merged.
  • D. Use Cloud Build to run tests in a specific folder. Trigger Cloud Build for every GitHub pull request.
Show Suggested Answer Hide Answer
Suggested Answer: D 🗳️

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
6a8c7ad
3 months, 2 weeks ago
Selected Answer: C
D mentions folder. Huh? I’ll take C
upvoted 1 times
...
xhilmi
11 months, 3 weeks ago
Selected Answer: D
Choose option D Use Cloud Build to run tests in a specific folder and trigger Cloud Build for every GitHub pull request. By configuring Cloud Build to run tests in a specific folder, you can focus on the relevant tests for the modified code in the feature branch. Triggering Cloud Build for every GitHub pull request ensures that tests are automatically executed whenever changes are proposed, providing continuous integration. This approach allows for automated testing of each pull request, providing early feedback to developers and ensuring that changes are thoroughly tested before being merged, contributing to a more reliable and efficient development process.
upvoted 1 times
...
pharao89
1 year ago
Selected Answer: D
D is what I do at work for this scenario and it works well.
upvoted 2 times
...
mshafa
1 year ago
Selected Answer: D
This approach automates the testing process, integrates well with your existing tools (GitHub and GCP), and ensures that code is tested in the most relevant part of the development lifecycle - before merging into the main branch.
upvoted 2 times
...
lelele2023
1 year ago
Selected Answer: D
shouldn't be C since it makes the test to happen after merge. Answer is D - as soon as a PR gets created then it runs tests.
upvoted 1 times
...
koo_kai
1 year ago
Selected Answer: D
all code is tested before changes are accepted
upvoted 2 times
...
Jason_Cloud_at
1 year, 1 month ago
Selected Answer: C
I would go with C
upvoted 2 times
...
Jay09812
1 year, 1 month ago
Wouldnt it be D considering you would want to run the tests when the PR is created and not after the code is already merged
upvoted 3 times
...
activist
1 year, 1 month ago
Answer C is correct. https://cloud.google.com/build/docs/automating-builds/create-manage-triggers
upvoted 2 times
Jason_Cloud_at
1 year, 1 month ago
Agreed
upvoted 1 times
...
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
Loading ...