Professional-Cloud-DevOps-Engineer Practice Questions

A.  

Deploy Falco or Twistlock on GKE to monitor for vulnerabilities on your running Pods

B.  

Configure Identity and Access Management (1AM) policies to create a least privilege model on your GKE clusters

C.  

Use Binary Authorization to attest images during your CI CD pipeline

D.  

Enable Container Analysis in Artifact Registry, and check for common vulnerabilities and exposures (CVEs) in your container images

A.  

Compare the canary with a new deployment of the current production version.

B.  

Compare the canary with a new deployment of the previous production version.

C.  

Compare the canary with the existing deployment of the current production version.

D.  

Compare the canary with the average performance of a sliding window of previous production versions.

A.  

Notify the team that their error budget is used up. Negotiate with the team for a launch freeze or tolerate a slightly worse user experience.

B.  

Look through other metrics related to the product and find SLOs with remaining error budget. Reallocate the error budgets and allow the feature launch.

C.  

Escalate the situation and request additional error budget.

D.  

Notify the team about the lack of error budget and ensure that all their tests are successful so the launch will not further risk the error budget.

A.  

Run the gcloud container clusters update --logging—SYSTEM command for the development cluster.

B.  

Run the gcloud container clusters update logging=WORKLOAD command for the development cluster.

C.  

Run the gcloud logging sinks update _Defau1t --disabled command in the project associated with the development environment.

D.  

Add the severity >= DEBUG resource. type "k83 container" exclusion filter to the Default logging sink in the project associated with the development environment.

A.  

Store public and private charts in OCI format by using Artifact Registry

B.  

Store public and private charts by using GitHub Enterprise with Google Workspace as the identity provider

C.  

Store public and private charts by using Git repository Configure Cloud Build to synchronize contents of the repository into a Cloud Storage bucket Connect Helm to the bucket by using https: // [bucket] .srorage.googleapis.com/ [holnchart] as the Helm repository

D.  

Configure a Helm chart repository server to run in Google Kubernetes Engine (GKE) with Cloud Storage bucket as the storage backend

A.  

Add logic to each Cloud Build step to HTTP POST the build information to a webhook.

B.  

Add a new step at the end of the pipeline in Cloud Build to HTTP POST the build information to a webhook.

C.  

Use Stackdriver Logging to create a logs-based metric from the Cloud Buitd logs. Create an Alert with a Webhook notification type.

D.  

Create a Cloud Pub/Sub push subscription to the Cloud Build cloud-builds PubSub topic to HTTP POST the build information to a webhook.

A.  

Enable Personalized Service Health annotations on the dashboard.

B.  

Create an alerting policy for the system error metrics.

C.  

Create a log-based metric to track cloud service errors, and display the metric on the dashboard.

D.  

Create a logs widget to display system errors from Cloud Logging on the dashboard.

A.  

Notify the team about the lack of error budget and ensure that all their tests are successful so the launch will not further risk the error budget.

B.  

Notify the team that their error budget is used up. Negotiate with the team for a launch freeze or tolerate a slightly worse user experience.

C.  

Escalate the situation and request additional error budget.

D.  

Look through other metrics related to the product and find SLOs with remaining error budget. Reallocate the error budgets and allow the feature launch.

A.  

Grant relevant team members read access to all GCP production projects. Create Stackdriver workspaces inside each project.

B.  

Grant relevant team members the Project Viewer IAM role on all GCP production projects. Create Slackdriver workspaces inside each project.

C.  

Choose an existing GCP production project to host the monitoring workspace. Attach the production projects to this workspace. Grant relevant team members read access to the Stackdriver Workspace.

D.  

Create a new GCP monitoring project, and create a Stackdriver Workspace inside it. Attach the production projects to this workspace. Grant relevant team members read access to the Stackdriver Workspace.

A.  

Enable the default service account key. and download the key

B.  

Remove the iam.disableServiceAccountKeyCreation policy at the organization level, and create a key.

C.  

Disable the service account key creation policy at the project's folder, and download the default key

D.  

Add a rule to set the iam.disableServiceAccountKeyCreation policy to off in your project and create a key.