You deployed an application into a large Standard Google Kubernetes Engine (GKE) cluster. The application is stateless and multiple pods run at the same time. Your application receives inconsistent traffic. You need to ensure that the user experience remains consistent regardless of changes in traffic. and that the resource usage of the cluster is optimized.What should you do?

Configure a Horizontal Pod Autoscaler.

Configure a cron job to scale the deployment on a schedule.

Configure a Horizontal Pod Autoscaler.

Configure a Vertical Pod Autoscaler.

Configure cluster autoscaling on the node pool.

Your company operates in a highly regulated domain. Your security team requires that only trusted container images can be deployed to Google Kubernetes Engine (GKE). You need to implement a solution that meets the requirements of the security team, while minimizing management overhead. What should you do?

Configure Binary Authorization in your GKE clusters to enforce deploy-time security policies

Grant the roles/artifactregistry. writer role to the Cloud Build service account. Confirm that no employee has Artifact Registry write permission.

Use Cloud Run to write and deploy a custom validator Enable an Eventarc trigger to perform validations when new images are uploaded.

Configure Kritis to run in your GKE clusters to enforce deploy-time security policies.

Configure Binary Authorization in your GKE clusters to enforce deploy-time security policies

You need to introduce postmortems into your organization during the holiday shopping season. You are expecting your web application to receive a large volume of traffic in a short period. You need to prepare your application for potential failures during the event What should you do?Choose 2 answers

Review your increased capacity requirements and plan for the required quota management.

Ensure that relevant system metrics are being captured with Cloud Monitoring and create alerts at levels of interest.

Monitor latency of your services for average percentile latency.

Review your increased capacity requirements and plan for the required quota management.

Create alerts in Cloud Monitoring for all common failures that your application experiences.

Ensure that relevant system metrics are being captured with Cloud Monitoring and create alerts at levels of interest.

Configure Anthos Service Mesh on the application to identify issues on the topology map.

You need to introduce postmortems into your organization. You want to ensure that the postmortem process is well received. What should you do?Choose 2 answers

Ensure that writing effective postmortems is a rewarded and celebrated practice.

Encourage your senior leadership to acknowledge and participate in postmortems.

Create a designated team that is responsible for conducting all postmortems.

Encourage new employees to conduct postmortems to learn through practice.

Ensure that writing effective postmortems is a rewarded and celebrated practice.

Encourage your senior leadership to acknowledge and participate in postmortems.

Provide your organization with a forum to critique previous postmortems.

You have an application that runs on Cloud Run. You want to use live production traffic to test a new version of the application while you let the quality assurance team perform manual testing. You want to limit the potential impact of any issues while testing the new version, and you must be able to roll back to a previous version of the application if needed. How should you deploy the new version?Choose 2 answers

Deploy a new Cloud Run revision with a tag and use the ---no-traffic option.

Deploy the new application version and split traffic to the new version.

Deploy the application as a new Cloud Run service.

Deploy a new Cloud Run revision with a tag and use the ---no-traffic option.

Deploy a new Cloud Run revision without a tag and use the ---no-traffic option.

Deploy the new application version and use the ---no-traffic option Route production traffic to the revision's URL.

Deploy the new application version and split traffic to the new version.

You recently noticed that one of your services has exceeded the error budget for the current rolling window period. Your company's product team is about to launch a new feature. You want to follow Site Reliability Engineering (SRE) practices. What should you do?

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.

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.

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.

Escalate the situation and request additional error budget.

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

You are leading a DevOps project for your organization. The DevOps team is responsible for managing the service infrastructure and being on-call for incidents. The Software Development team is responsible for writing, submitting, and reviewing code. Neither team has any published SLOs. You want to design a new joint-ownership model for a service between the DevOps team and the Software Development team. Which responsibilities should be assigned to each team in the new joint-ownership model?

DevOps team responsibilities Manage the service infrastructure Be on-call for incidents Software Development team responsibilities Adopt and publish SLOs for the service Submit code to be reviewed Shared responsibilities for code reviews

DevOps team responsibilities Manage the service infrastructure Be on-call for incidents Perform code reviews Software Development team responsibilities Submit code to be reviewed by the DevOps team Publish the SLOs that the DevOps team must meet

DevOps team responsibilities Manage the service infrastructure Perform code reviews Software Development team responsibilities Submit code to be reviewed by the DevOps team Be on-call for incidents Publish the SLOs that the DevOps team must meet

DevOps team responsibilities Shared responsibilities for code reviews Software Development team responsibilities Manage the service infrastructure Be on-call for incidents on a rotation basis Adopt and publish SLOs for the service Submit code to be reviewed

DevOps team responsibilities Manage the service infrastructure Be on-call for incidents Software Development team responsibilities Adopt and publish SLOs for the service Submit code to be reviewed Shared responsibilities for code reviews

Your company uses a CI/CD pipeline with Cloud Build and Artifact Registry to deploy container images to Google Kubernetes Engine (GKE). Images are tagged with the latest commit hash and promoted to production after successful testing in the development and pre-production environments. A recent production deployment caused the application to fail due to untested integration functionality, requiring a disruptive manual rollback. During the rollback, you noticed many old and unused container images accumulating in Artifact Registry. You need to improve rollout and rollback management and clean up the old container images. What should you do?

Adopt Cloud Deploy for managing deployments, and implement an Artifact Registry cleanup policy.

Adopt Cloud Deploy for managing deployments, and schedule a Cloud Build job for container image cleanup.

Deploy Cloud Service Mesh across the GKE clusters, and manually clean up Artifact Registry images.

Adopt Cloud Deploy for managing deployments, and implement an Artifact Registry cleanup policy.

Set up a rollback pipeline in Cloud Build, and implement an Artifact Registry cleanup policy.

Your application's performance in Google Cloud has degraded since the last release. You suspect that downstream dependencies might be causing some requests to take longer to complete. You need to investigate the issue with your application to determine the cause. What should you do?

Configure Cloud Trace in your application.

Configure Error Reporting in your application.

Configure Cloud Profiler in your application.

Configure Google Cloud Managed Service for Prometheus in your application.

You work for a company that manages highly sensitive user data. You are designing the Google Kubernetes Engine (GKE) infrastructure for your company, including several applications that will be deployed in development and production environments. Your design must protect data from unauthorized access from other applications while minimizing the amount of management overhead required. What should you do?

Create one cluster for each environment (development and production) with each application in its own namespace within each cluster.

Create one cluster for the organization with separate namespaces for each application and environment combination.

Create one cluster for each environment (development and production) with each application in its own namespace within each cluster.

Create one cluster for the organization with separate namespaces for each application.

Create one cluster for each application with separate namespaces for production and development environments.

Your company runs services on Google Cloud. Each team runs their applications in a dedicated project. New teams and projects are created regularly. Your security team requires that all logs are processed by a security information and event management (SIEM) system. The SIEM ingests logs by using Pub/Sub. You must ensure that all existing and future logs are scanned by the SIEM. What should you do?

Create an organization-level aggregated sink with a SIEM Pub/Sub topic as the destination. Set an inclusion filter to include all logs.

Create a project-level logging sink with a SIEM Pub/Sub topic as the destination. Set an inclusion filter to include all logs. Repeat for each project.

Create an organization-level aggregated sink with a SIEM log bucket as the destination. Set an inclusion filter to include all logs.

Create a folder-level aggregated sink with a SIEM Pub/Sub topic as the destination. Set an inclusion filter to include all logs. Repeat for each folder.

Your company is creating a new cloud-native Google Cloud organization. You expect this Google Cloud organization to first be used by a small number of departments and then expand to be used by a large number of departments. Each department has a large number of applications varying in size. You need to design the VPC network architecture. Your solution must minimize the amount of management required while remaining flexible enough for development teams to quickly adapt to their evolving needs. What should you do?

Create a separate VPC for each department and connect the VPCs with VPC Network Peering.

Create a separate VPC for each department and use Private Service Connect to connect the VPCs.

Create a separate VPC for each application and use Private Service Connect to connect the VPCs.

Create a separate VPC for each department and connect the VPCs with Cloud VPN.

You are using Jenkins to orchestrate your CI/CD pipelines deploying your applications to GKE and on-premises VMs. After expanding your on-premises infrastructure, all resource utilization is normal, but you notice that initiating on-premises deployments is taking longer than expected. You need to accelerate the initiation of on-premises deployments. What should you do?

Configure Jenkins to use an artifact repository in your on-premises environment.

Implement a blue-green deployment strategy for your on-premises VMs.

Upgrade your on-premises VMs to have faster CPUs and more memory.

Increase the number of Jenkins executor threads.

Configure Jenkins to use an artifact repository in your on-premises environment.

You use Google Cloud Managed Service for Prometheus with managed collection to gather metrics from your service running on Google Kubernetes Engine (GKE). After deploying the service, there is no metric data appearing in Cloud Monitoring, and you have not encountered any error messages. You need to troubleshoot this issue. What should you do?

Verify that your PodMonitoring configuration references a valid port.

Determine if your service has exceeded its quota for writes to the Cloud Monitoring API.

Check if the Grafana service is installed on your GKE cluster.

Confirm that your service has the monitoring.servicesViewer IAM role.

Verify that your PodMonitoring configuration references a valid port.

Your team is preparing to launch a new API in Cloud Run. The API uses an OpenTelemetry agent to send distributed tracing data to Cloud Trace to monitor the time each request takes. The team has noticed inconsistent trace collection. You need to resolve the issue. What should you do?

Configure CPU to be always-allocated.

Increase the CPU limit in Cloud Run from 2 to 4.

Configure CPU to be allocated only during request processing.

Configure CPU to be always-allocated.

Google Professional Cloud DevOps Engineer Practice Test 5

You are analyzing Java applications in production. All applications have Cloud Profiler and Cloud Trace installed and configured by default. You want to determine which applications need performance tuning. What should you do?

Choose 2 answers

Become a Premium Member for full access

Unlock Premium Member

Google Professional Cloud DevOps Engineer Practice Test 5

Question

Google Professional Cloud DevOps Engineer Practice Tests

Practice Tests