Free PROFESSIONAL-CLOUD-DEVOPS-ENGINEER – Google PROFESSIONAL-CLOUD-DEVOPS-ENGINEER Practice Test Question

Select an option, then click Submit answer.

• ○ Purchase Committed Use Discounts.
• ○ Migrate the instances to a Managed Instance Group.
• ○ Convert the instances to preemptible virtual machines.
• ○ Create an Unmanaged Instance Group for the instances used to run the workload.

Select an option, then click Submit answer.

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

Select an option, then click Submit answer.

• ○ ג€¢ In your application, create a metric with a metricKind set to DELTA and a valueType set to DOUBLE. ג€¢ In Stackdriver's Metrics Explorer, use a Stacked Bar graph to visualize the metric.
• ○ ג€¢ In your application, create a metric with a metricKind set to CUMULATIVE and a valueType set to DOUBLE. ג€¢ In Stackdriver's Metrics Explorer, use a Line graph to visualize the metric.
• ○ ג€¢ In your application, create a metric with a metricKind set to GAUGE and a valueType set to DISTRIBUTION. ג€¢ In Stackdriver's Metrics Explorer, use a Heatmap graph to visualize the metric.
• ○ ג€¢ In your application, create a metric with a metricKind set to METRIC_KIND_UNSPECIFIED and a valueType set to INT64. ג€¢ In Stackdriver's Metrics Explorer, use a Stacked Area graph to visualize the metric.

Select an option, then click Submit answer.

• ○ Import the Stackdriver Profiler package, and configure it to relay function timing data to Stackdriver for further analysis.
• ○ Import the Stackdriver Debugger package, and configure the application to emit debug messages with timing information.
• ○ Instrument the code using a timing library, and publish the metrics via a health check endpoint that is scraped by Stackdriver.
• ○ Install an Application Performance Monitoring (APM) tool in both locations, and configure an export to a central data storage location for analysis.

Select an option, then click Submit answer.

• ○ Use Cloud Storage to cache intermediate artifacts.
• ○ Run multiple Jenkins agents to parallelize the build.
• ○ Use multiple smaller build steps to minimize execution time.
• ○ Use larger Cloud Build virtual machines (VMs) by using the machine-type option.

Select an option, then click Submit answer.

• ○ Roll back the recent release.
• ○ Review the Stackdriver monitoring.
• ○ Upsize the virtual machines running the login services.
• ○ Deploy a new release to see whether it fixes the problem.

Select an option, then click Submit answer.

• ○ Store the encryption keys in Cloud Key Management Service (KMS) and rotate the keys frequently
• ○ Inject the secret at the time of instance creation via an encrypted configuration management system.
• ○ Integrate the application with a Single sign-on (SSO) system and do not expose secrets to the application.
• ○ Leverage a continuous build pipeline that produces multiple versions of the secret for each instance of the application.

Select an option, then click Submit answer.

• ○ Install the Stackdriver Error Reporting library for Python, and then run your code on a Compute Engine VM.
• ○ Install the Stackdriver Error Reporting library for Python, and then run your code on Google Kubernetes Engine.
• ○ Install the Stackdriver Error Reporting library for Python, and then run your code on App Engine flexible environment.
• ○ Use the Stackdriver Error Reporting API to write errors from your application to ReportedErrorEvent, and then generate log entries with properly formatted error messages in Stackdriver Logging.

Select an option, then click Submit answer.

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

Select an option, then click Submit answer.

• ○ Identify engineers responsible for the incident and escalate to the senior management.
• ○ Ensure that test cases that catch errors of this type are run successfully before new software releases.
• ○ Follow up with the employees who reviewed the changes and prescribe practices they should follow in the future.
• ○ Design a policy that will require on-call teams to immediately call engineers and management to discuss a plan of action if an incident occurs.

Select an option, then click Submit answer.

• ○ Create a single aggregated log sink at the organization level.
• ○ Create a log sink in each project.
• ○ Create two aggregated log sinks at the organization level, and filter by project ID.
• ○ Create an aggregated log sink in the Dev and Prod folders.

Select an option, then click Submit answer.

• ○ Run the kubectl rollout undo command.
• ○ Delete the new container image, and delete the running Pods.
• ○ Update the Kubernetes Service to point to the previous Kubernetes Deployment.
• ○ Scale the new Kubernetes Deployment to zero.

Select an option, then click Submit answer.

• ○ Ensure that all postmortems include what caused the incident, identify the person or team responsible for causing the incident, and how to prevent a future occurrence of the incident.
• ○ Ensure that all postmortems include what caused the incident, how the incident could have been worse, and how to prevent a future occurrence of the incident.
• ○ Ensure that all postmortems include the severity of the incident, how to prevent a future occurrence of the incident, and what caused the incident without naming internal system components.
• ○ Ensure that all postmortems include how the incident was resolved and what caused the incident without naming customer information.
• ○ Ensure that all postmortems include all incident participants in postmortem authoring and share postmortems as widely as possible.

Select an option, then click Submit answer.

• ○ Select a latency metric for a request-based method of evaluation.
• ○ Select a latency metric for a window-based method of evaluation.
• ○ Select an availability metric for a request-based method of evaluation.
• ○ Select an availability metric for a window-based method of evaluation.

Select an option, then click Submit answer.

• ○ Encourage new employees to conduct postmortems to team through practice.
• ○ Create a designated team that is responsible for conducting all postmortems.
• ○ Encourage your senior leadership to acknowledge and participate in postmortems.
• ○ Ensure that writing effective postmortems is a rewarded and celebrated practice.
• ○ Provide your organization with a forum to critique previous postmortems.

Select an option, then click Submit answer.

• ○ Use A/B testing with blue/green deployment.
• ○ Use canary testing with continuous deployment.
• ○ Use canary testing with rolling updates deployment.
• ○ Use shadow testing with continuous deployment.

Select an option, then click Submit answer.

• ○ Apply the conditional role binding resource.name.extract("locations/global/buckets/{bucket}/") == "_Default" to the _Default bucket.
• ○ Apply a jsonPayload.user_email restricted field to the _Default bucket. Grant the Log Field Accessor role to the security team members.
• ○ Apply a jsonPayload.user_email exclusion filter to the _Default bucket.
• ○ Modify the application to toggle inclusion of user_email when the LOG_USER_EMAIL environment variable is set to true. Restrict the engineering team members who can change the production environment variable by using the CODEOWNERS file.

Select an option, then click Submit answer.

• ○ Automate CI pipelines by using Cloud Build for container image creation and Kubernetes manifest updates from main branch merge requests. Integrate with Config Sync to test new im-ages in dynamically created namespaces on the Dev GKE cluster with autoscaling enabled. Im-plement a post-test namespace cleanup routine.
• ○ Automate CI pipelines by using Cloud Build to create container images and update Kuber-netes manifests for each commit. Use Cloud Deploy for progressive delivery to Dev, Staging, and Prod GKE clusters. Enable Config Sync for consistent Kubernetes configurations across en-vironments.
• ○ Use Cloud Build to automate CI pipelines and update Kubernetes manifest files from feature branch commits. Integrate with Config Sync to test new images in dynamically created namespaces on the Dev GKE cluster with autoscaling enabled. Implement a post-test namespace cleanup routine.
• ○ Use Cloud Build to automate CI pipelines and update Kubernetes manifest files from feature branch commits. Integrate with Config Sync to test new images in dynamically created GKE Dev clusters for each feature branch, which are deleted upon merge request.

Select an option, then click Submit answer.

• ○ Configure Artifact Registry to automatically scan new images and periodically re-scan all images. Use Cloud Audit Logs to track image uploads and identify the user who pushed each image.
• ○ Configure Artifact Registry to send vulnerability scan results to a Cloud Storage bucket. Use a separate script to parse results and notify a security team.
• ○ Configure Artifact Registry to automatically re-scan images daily. Enable Cloud Audit Logs to track these scans, and use Logs Explorer to identify vulnerabilities.
• ○ Configure Artifact Registry to automatically trigger vulnerability scans for new image tags, and view scan results. Use Cloud Audit Logs to track image tag creation events.

Select an option, then click Submit answer.

• ○ Delay the deployment of the feature until the error budget is replenished.
• ○ Re-run the unit tests, and start the deployment of the feature if the tests pass.
• ○ Start the deployment of the feature immediately.
• ○ Deploy the feature to a subset of users, and gradually roll out to all users if there are no errors reported.

Select an option, then click Submit answer.

• ○ Create a separate VPC for each department, and connect the VPCs with VPC Network Peering.
• ○ Create a separate VPC for each department. Use Private Service Connect to connect the VPCs.
• ○ Create a separate VPC for each application. Use Private Service Connect to connect the VPCs.
• ○ Create a separate VPC for each department, and connect the VPCs with Cloud VPN.

Select an option, then click Submit answer.

• ○ Implement a sidecar OpenTelemetry Collector alongside each Pod in all Kubernetes clusters (on-premises and GKE). Configure these collectors to export Prometheus-formatted metrics. Use dedicated Prometheus instances in each Kubernetes cluster and Thanos in a central GKE cluster. Install Grafana on a GKE cluster, and use Grafana to monitor the applications.
• ○ Create a scoping project and add all the Google Cloud projects to it. Use Bindplane to streamline OpenTelemetry metric collection for the on-premises Kubernetes clusters into Cloud Monitoring.
• ○ Create a new Google Cloud project to use as a scoping project and add all the other Google Cloud projects to it. Instrument the applications running on-premises to export the metrics to Cloud Monitoring as user-defined metrics. Use Cloud Monitoring to monitor the applications.
• ○ Enable Google Cloud Managed Service for Prometheus collections by using the OpenTelemetry Collector on the Google Kubernetes Engine (GKE) clusters, and enable non-managed Prometheus for the on-premises Kubernetes clusters. Install Grafana on a GKE cluster, and use Grafana to monitor the applications.