Professional-Cloud-DevOps-Engineer 무료 덤프문제 온라인 액세스

Your company is using HTTPS requests to trigger a public Cloud Run-hosted service accessible at the
https://booking-engine-abcdef .a.run.app URL You need to give developers the ability to test the latest revisions of the service before the service is exposed to customers What should you do?

• A.Grant the roles/run. invoker role to the developers testing the booking-engine service Use the https:
  //booking-engine-abcdef. private. run. app URL for testing
• B.Runthegcioud run services update-traffic booking-engine -to-revisions LATEST*! command Use the ht tps: //booking-engine-abcdef. a. run. ape URL for testing
• C.Pass the curl -K "Authorization: Hearer S(gclcud auth print-identity-token)" auth token Use the https: /
  /booking-engine-abcdef. a. run. app URL to test privately
• D.Runthegcioud run deploy booking-engine -no-traffic --ag dev command Use the https://dev---- booking-engine-abcdef. a. run. app URL for testing

You use Spinnaker to deploy your application and have created a canary deployment stage in the pipeline.
Your application has an in-memory cache that loads objects at start time. You want to automate the comparison of the canary version against the production version. How should you configure the canary analysis?

• A.Compare the canary with the existing deployment of the current production version.
• B.Compare the canary with a new deployment of the previous production version.
• C.Compare the canary with a new deployment of the current production version.
• D.Compare the canary with the average performance of a sliding window of previous production versions.

You support a large service with a well-defined Service Level Objective (SLO). The development team deploys new releases of the service multiple times a week. If a major incident causes the service to miss its SLO, you want the development team to shift its focus from working on features to improving service reliability. What should you do before a major incident occurs?

• A.Negotiate with the development team to reduce the release frequency to no more than once a week.
• B.Add a plugin to your Jenkins pipeline that prevents new releases whenever your service is out of SLO.
• C.Negotiate with the product team to always prioritize service reliability over releasing new features.
• D.Develop an appropriate error budget policy in cooperation with all service stakeholders.

You need to define Service Level Objectives (SLOs) for a high-traffic multi-region web application.
Customers expect the application to always be available and have fast response times. Customers are currently happy with the application performance and availability. Based on current measurement, you observe that the
90th percentile of latency is 120ms and the 95th percentile of latency is 275ms over a 28-day window. What latency SLO would you recommend to the team to publish?

• A.90th percentile - 250ms95th percentile - 400ms
• B.90th percentile - 120ms95th percentile - 275ms
• C.90th percentile - 100ms95th percentile - 250ms
• D.90th percentile - 150ms95th percentile - 300ms

You are the Operations Lead for an ongoing incident with one of your services. The service usually runs at around 70% capacity. You notice that one node is returning 5xx errors for all requests. There has also been a noticeable increase in support cases from customers. You need to remove the offending node from the load balancer pool so that you can isolate and investigate the node. You want to follow Google-recommended practices to manage the incident and reduce the impact on users. What should you do?

• A.1. Communicate your intent to the incident team.2. Add a new node to the pool, and wait for the new node to report as healthy.3. When traffic is being served on the new node, drain traffic from the unhealthy node, and remove the old node from service.
• B.1. Communicate your intent to the incident team.2. Perform a load analysis to determine if the remaining nodes can handle the increase in traffic offloaded from the removed node, and scale appropriately.3. When any new nodes report healthy, drain traffic from the unhealthy node, and remove the unhealthy node from service.
• C.1 . Drain traffic from the unhealthy node and remove the old node from service.2. Add a new node to the pool, wait for the new node to report as healthy, and then serve traffic to the new node.3. Monitor traffic to ensure that the pool is healthy and is handling traffic appropriately.4. Communicate your actions to the incident team.
• D.1 . Drain traffic from the unhealthy node and remove the node from service.2. Monitor traffic to ensure that the error is resolved and that the other nodes in the pool are handling the traffic appropriately.3.
  Scale the pool as necessary to handle the new load.4. Communicate your actions to the incident team.