Free Access to Google.Professional-Cloud-DevOps-Engineer.v2024-08-12.q133 with Valid Practice Test (Page 4)

Question 11

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 Cl/CD pipelines. Periodically run all tests in the feature branch.
B.Use Cloud Build to run the tests. Trigger all tests to run after a pull request is merged.
C.Ask the pull request reviewers to run the integration tests before approving the code.
D.Use Cloud Build to run tests in a specific folder. Trigger Cloud Build for every GitHub pull request.

Correct Answer: D

Explanation
Cloud Build is a service that executes your builds on Google Cloud Platform infrastructure. Cloud Build can import source code from Google Cloud Storage, Cloud Source Repositories, GitHub, or Bitbucket, execute a build to your specifications, and produce artifacts such as Docker containers or Java archives1. Cloud Build can also run integration tests as part of your build steps2.
You can use Cloud Build to run tests in a specific folder by specifying the path to the folder in the dir field of your build step3. For example, if you have a folder named tests that contains your integration tests, you can use the following build step to run them:
steps:
- name: 'gcr.io/cloud-builders/go'
args: ['test', '-v']
dir: 'tests'
Copy
You can use Cloud Build to trigger builds for every GitHub pull request by using the Cloud Build GitHub app. The app allows you to automatically build on Git pushes and pull requests and view your build results on GitHub and Google Cloud console4. You can configure the app to run builds on specific branches, tags, or paths5. For example, if you want to run builds on pull requests that target the master branch, you can use the following trigger configuration:
includedFiles:
- '**'
name: 'pull-request-trigger'
github:
name: 'my-repo'
owner: 'my-org'
pullRequest:
branch: '^master$'
Using Cloud Build to run tests in a specific folder and trigger builds for every GitHub pull request is a good way to continuously test your feature branch and ensure that all code is tested before changes are accepted.
This way, you can catch any errors or bugs early and prevent them from affecting the main branch.
Using a Jenkins server for CI/CD pipelines is not a bad option, but it would require more setup and maintenance than using Cloud Build, which is fully managed by Google Cloud. Periodically running all tests in the feature branch is not as efficient as running tests for every pull request, as it may delay the feedback loop and increase the risk of conflicts or failures.
Using Cloud Build to run the tests after a pull request is merged is not a good practice, as it may introduce errors or bugs into the main branch that could have been prevented by testing before merging.
Asking the pull request reviewers to run the integration tests before approving the code is not a reliable way of ensuring code quality, as it depends on human intervention and may be prone to errors or oversights.
References:
1: Overview | Cloud Build Documentation | Google Cloud
2: Running integration tests | Cloud Build Documentation | Google Cloud
3: Build configuration overview | Cloud Build Documentation | Google Cloud
4: Building repositories from GitHub | Cloud Build Documentation | Google Cloud
5: Creating GitHub app triggers | Cloud Build Documentation | Google Cloud

Question 12

You are responsible for the reliability of a high-volume enterprise application. A large number of users report that an important subset of the application's functionality - a data intensive reporting feature - is consistently failing with an HTTP 500 error. When you investigate your application's dashboards, you notice a strong correlation between the failures and a metric that represents the size of an internal queue used for generating reports. You trace the failures to a reporting backend that is experiencing high I/O wait times. You quickly fix the issue by resizing the backend's persistent disk (PD). How you need to create an availability Service Level Indicator (SLI) for the report generation feature. How would you define it?

A.As the I/O wait times aggregated across all report generation backends
B.As the proportion of report generation requests that result in a successful response
C.As the application's report generation queue size compared to a known-good threshold
D.As the reporting backend PD throughout capacity compared to a known-good threshold

Question 13

Your organization wants to increase the availability target of an application from 99 9% to 99 99% for an investment of $2 000 The application's current revenue is S1,000,000 You need to determine whether the increase in availability is worth the investment for a single year of usage What should you do?

A.Calculate the value of improved availability to be $900, and determine that the increase in availability is not worth the investment
B.Calculate the value of improved availability to be $1 000 and determine that the increase in availability is not worth the investment
C.Calculate the value of improved availability to be $1 000 and determine that the increase in availability is worth the investment
D.Calculate the value of improved availability to be $9,000. and determine that the increase in availability is worth the investment

Question 14

Your company follows Site Reliability Engineering practices. You are the person in charge of Communications for a large, ongoing incident affecting your customer-facing applications. There is still no estimated time for a resolution of the outage. You are receiving emails from internal stakeholders who want updates on the outage, as well as emails from customers who want to know what is happening. You want to efficiently provide updates to everyone affected by the outage. What should you do?

A.Focus on responding to internal stakeholders at least every 30 minutes. Commit to "next update" times.
B.Provide periodic updates to all stakeholders in a timely manner. Commit to a "next update" time in all communications.
C.Delegate the responding to internal stakeholder emails to another member of the Incident Response Team. Focus on providing responses directly to customers.
D.Provide all internal stakeholder emails to the Incident Commander, and allow them to manage internal communications. Focus on providing responses directly to customers.

Question 15

You need to deploy a new service to production. The service needs to automatically scale using a Managed Instance Group (MIG) and should be deployed over multiple regions. The service needs a large number of resources for each instance and you need to plan for capacity. What should you do?

A.Validate that the resource requirements are within the available quota limits of each region.
B.Use the n1-highcpu-96 machine type in the configuration of the MIG.
C.Monitor results of Stackdriver Trace to determine the required amount of resources.
D.Deploy the service in one region and use a global load balancer to route traffic to this region.

Question 11

Question 12

Question 13

Question 14

Question 15

Download PDF File