Your application is deployed in a Google Kubernetes Engine (GKE) cluster. When a new version of your application is released, your CI/CD tool updates the spec.template.spec.containers[0].image value to reference the Docker image of your new application version. When the Deployment object applies the change, you want to deploy at least 1 replica of the new version and maintain the previous replicas until the new replica is healthy.
Which change should you make to the GKE Deployment object shown below?

• A.Set the Deployment strategy to Recreate with maxSurge set to 1, maxUnavailable set to 0.
• B.Set the Deployment strategy to RollingUpdate with maxSurge set to 0, maxUnavailable set to 1.
• C.Set the Deployment strategy to RollingUpdate with maxSurge set to 1, maxUnavailable set to 0.
• D.Set the Deployment strategy to Recreate with maxSurge set to 0, maxUnavailable set to 1.

Comment: *

Name: *

Email: *

Verification: *

You are a developer working with the CI/CD team to troubleshoot a new feature that your team introduced. The CI/CD team used HashiCorp Packer to create a new Compute Engine image from your development branch. The image was successfully built, but is not booting up. You need to investigate the issue with the CI/CD team. What should you do?

• A.Create a new feature branch, and ask the build team to rebuild the image.
• B.Shut down the deployed virtual machine, export the disk, and then mount the disk locally to access the boot logs.
• C.Install Packer locally, build the Compute Engine image locally, and then run it in your personal Google Cloud project.
• D.Check Compute Engine OS logs using the serial port, and check the Cloud Logging logs to confirm access to the serial port.

Comment: *

Name: *

Email: *

Verification: *

You are developing an ecommerce web application that uses App Engine standard environment and Memorystore for Redis. When a user logs into the app, the application caches the user's information (e.g., session, name, address, preferences), which is stored for quick retrieval during checkout.
While testing your application in a browser, you get a 502 Bad Gateway error. You have determined that the application is not connecting to Memorystore. What is the reason for this error?

• A.Your Memorystore for Redis instance was deployed without a public IP address.
• B.You configured your application to use a Serverless VPC Access connector on a different subnet in a different availability zone than your App Engine instance.
• C.You configured your Serverless VPC Access connector in a different region than your App Engine instance.
• D.The firewall rule allowing a connection between App Engine and Memorystore was removed during an infrastructure update by the DevOps team.

Comment: *

Name: *

Email: *

Verification: *

Your data is stored in Cloud Storage buckets. Fellow developers have reported that data downloaded from Cloud Storage is resulting in slow API performance. You want to research the issue to provide details to the GCP support team. Which command should you run?

• A.gsutil test -o output.json gs://my-bucket
• B.gsutil perfdiag -o output.json gs://my-bucket
• C.gcloud compute scp example-instance:~/test-data -o output.json gs://my-bucket
• D.gcloud services test -o output.json gs://my-bucket

Comment: *

Name: *

Email: *

Verification: *

You are developing a web application that will be accessible over both HTTP and HTTPS and will run on Compute Engine instances. On occasion, you will need to SSH from your remote laptop into one of the Compute Engine instances to conduct maintenance on the app. How should you configure the instances while following Google-recommended best practices?

• A.Set up a backend with Compute Engine web server instances with a private IP address behind a TCP proxy load balancer.
• B.Configure the firewall rules to allow all ingress traffic to connect to the Compute Engine web servers, with each server having a unique external IP address.
• C.Configure Cloud Identity-Aware Proxy API for SSH access. Then configure the Compute Engine servers with private IP addresses behind an HTTP(s) load balancer for the application web traffic.
• D.Set up a backend with Compute Engine web server instances with a private IP address behind an HTTP(S) load balancer. Set up a bastion host with a public IP address and open firewall ports. Connect to the web instances using the bastion host.

Comment: *

Name: *

Email: *

Verification: *