Google PROFESSIONAL-CLOUD-DEVELOPER Exam Dumps

Your team manages a Google Kubernetes Engine (GKE) cluster where an application is running. A different team is planning to integrate with this application. Before they start the integration, you need to ensure that the other team cannot make changes to your application, but they can deploy the integration on GKE. What should you do?

A. Using Identity and Access Management (IAM), grant the Viewer IAM role on the cluster project to the other team.

B. Create a new GKE cluster. Using Identity and Access Management (IAM), grant the Editor role on the cluster project to the other team.

C. Create a new namespace in the existing cluster. Using Identity and Access Management (IAM), grant the Editor role on the cluster project to the other team.

D. Create a new namespace in the existing cluster. Using Kubernetes role-based access control (RBAC), grant the Admin role on the new namespace to the other team.

Your application is deployed in a Google Kubernetes Engine (GKE) cluster. You want to expose this application publicly behind a Cloud Load Balancing HTTP(S) load balancer. What should you do?

A. Configure a GKE Ingress resource.

B. Configure a GKE Service resource.

C. Configure a GKE Ingress resource with type: LoadBalancer.

D. Configure a GKE Service resource with type: LoadBalancer.

You need to deploy an internet-facing microservices application to Google Kubernetes Engine (GKE). You want to validate new features using the A/B testing method. You have the following requirements for deploying new container image releases

?There is no downtime when new container images are deployed.

?New production releases are tested and verified using a subset of production users.

What should you do?

A. 1 Configure your Cl/CD pipeline to update the Deployment manifest file by replacing the container version with the latest version. 2 Recreate the Pods in your cluster by applying the Deployment manifest file. 3 Validate the application's performance by comparing its functionality with the previous release version and roll back if an issue arises.

B. 1 install the Anthos Service Mesh on your GKE cluster. 2 Create two Deployments on the GKE cluster and label them with different version names. 3 Create a VirtualService with a routing rule to send a small percentage of traffic to the Deployment that references the new version of the application.

C. 1 Create a second namespace on GKE for the new release version. 2 Create a Deployment configuration for the second namespace with the desired number of Pods. 3 Deploy new container versions in the second namespace. 4 Update the ingress configuration to route traffic to the namespace with the new container versions.

D. 1. Implement a rolling update pattern by replacing the Pods gradually with the new release versify. 2 Validate the application's performance for the new subset of users during the rollout and roll back if an issue arises.