ACE practice questions 211–220

1. Question 211 · 325 in bank

   You create a new Google Kubernetes Engine (GKE) cluster and want to make sure that it always runs a supported and stable version of Kubernetes. What should you do?

   • AEnable the Node Auto-Repair feature for your GKE cluster.
   • BEnable the Node Auto-Upgrades feature for your GKE cluster.
   • CSelect the latest available cluster version for your GKE cluster.
   • DSelect ג€Container-Optimized OS (cos)ג€ as a node image for your GKE cluster.

   Show answer

   Answer: B

   Explanation

   "Creating or upgrading a cluster by specifying the version as does not provide automatic upgrades. Enable automatic node upgrades to ensure that the nodes in your cluster up to date with the latest stable version." --source: https://cloud.google.com/kubernetes-engine/versioning-and-upgrades -Correct answer: B

   Source: Adapted from community discussion — 4bsolut

   References

   • Google Cloud documentation
   • Google Cloud documentation
   • Google Cloud documentation
   • Google Cloud documentation
   • Google Cloud documentation

   Next question

2. Question 212 · 325 in bank

   You want to configure autohealing for network load balancing for a group of Compute Engine instances that run in multiple zones, using the fewest possible steps. You need to configure re-creation of VMs if they are unresponsive after 3 attempts of 10 seconds each. What should you do?

   • ACreate an HTTP load balancer with a backend configuration that references an existing instance group. Set the health check to healthy (HTTP)
   • BCreate an HTTP load balancer with a backend configuration that references an existing instance group. Define a balancing mode and set the maximum RPS to 10.
   • CCreate a managed instance group. Set the Autohealing health check to healthy (HTTP)
   • DCreate a managed instance group. Verify that the autoscaling setting is on.

   Show answer

   Answer: C

   Explanation

   C, Agreed reference : https://cloud.google.com/compute/docs/tutorials/high-availability-autohealing Pro Tip: Use separate health checks for load balancing and for autohealing. Health checks for load balancing detect unresponsive instances and direct traffic away from them. Health checks for autohealing detect and recreate failed instances, so they should be less aggressive than load balancing health checks. Using the same health check for these services would remove the distinction between unresponsive instances and failed instances, causing unnecessary latency and unavailability for your users.

   Source: Adapted from community discussion — ReyBan

   References

   • Google Cloud documentation
   • Google Cloud documentation
   • Google Cloud documentation
   • Google Cloud documentation

   Next question

3. Question 213 · 325 in bank

   You have an instance group that you want to load balance. You want the load balancer to terminate the client SSL session. The instance group is used to serve a public web application over HTTPS. You want to follow Google-recommended practices. What should you do?

   • AConfigure an HTTP(S) load balancer.
   • BConfigure an internal TCP load balancer.
   • CConfigure an external SSL proxy load balancer.
   • DConfigure an external TCP proxy load balancer.

   Show answer

   Answer: A

   Explanation

   According to the documentation of SSL Proxy Load Balacing on Google, "SSL Proxy Load Balancing is intended for non-HTTP(S) traffic. For HTTP(S) traffic, we recommend that you use HTTP(S) Load Balancing." in my opinion A should be the most suitable choice.

   Source: Adapted from community discussion — Gini

   References

   • Google Cloud documentation
   • Google Cloud documentation
   • Google Cloud documentation
   • Google Cloud documentation
   • Google Cloud documentation

   Next question

4. Question 214 · 325 in bank

   You have 32 GB of data in a single file that you need to upload to a Nearline Storage bucket. The WAN connection you are using is rated at 1 Gbps, and you are the only one on the connection. You want to use as much of the rated 1 Gbps as possible to transfer the file rapidly. How should you upload the file?

   • AUse the GCP Console to transfer the file instead of gsutil.
   • BEnable parallel composite uploads using gsutil on the file transfer.
   • CDecrease the TCP window size on the machine initiating the transfer.
   • DChange the storage class of the bucket from Nearline to Multi-Regional.

   Show answer

   Answer: B

   Explanation

   Correct answer is B as the bandwidth is good and its a single file, gsutil parallel composite uploads can be used to split the large file and upload in parallel.Refer GCP documentation - Transferring Data to GCP &amp

   Source: Adapted from community discussion — leba

   References

   • Google Cloud documentation
   • Google Cloud documentation
   • Google Cloud documentation

   Next question

5. Question 215 · 325 in bank

   You've deployed a microservice called myapp1 to a Google Kubernetes Engine cluster using the YAML file specified below:

   

   You need to refactor this configuration so that the database password is not stored in plain text. You want to follow Google-recommended practices. What should you do?

   • AStore the database password inside the Docker image of the container, not in the YAML file.
   • BStore the database password inside a Secret object. Modify the YAML file to populate the DB_PASSWORD environment variable from the Secret.
   • CStore the database password inside a ConfigMap object. Modify the YAML file to populate the DB_PASSWORD environment variable from the ConfigMap.
   • DStore the database password in a file inside a Kubernetes persistent volume, and use a persistent volume claim to mount the volume to the container.

   Show answer

   Answer: B

   Explanation

   it is good practice to use Secrets for confidential data (like API keys) and ConfigMaps for non-confidential data (like port numbers). B is correct.

   Source: Adapted from community discussion — rramani7

   References

   • Google Cloud documentation
   • Kubernetes documentation
   • Kubernetes documentation
   • Google Cloud documentation
   • Google Cloud documentation

   Next question

6. Question 216 · 325 in bank

   You are running an application on multiple virtual machines within a managed instance group and have autoscaling enabled. The autoscaling policy is configured so that additional instances are added to the group if the CPU utilization of instances goes above 80%. VMs are added until the instance group reaches its maximum limit of five VMs or until CPU utilization of instances lowers to 80%. The initial delay for HTTP health checks against the instances is set to 30 seconds. The virtual machine instances take around three minutes to become available for users. You observe that when the instance group autoscales, it adds more instances then necessary to support the levels of end-user traffic. You want to properly maintain instance group sizes when autoscaling. What should you do?

   • ASet the maximum number of instances to 1.
   • BDecrease the maximum number of instances to 3.
   • CUse a TCP health check instead of an HTTP health check.
   • DIncrease the initial delay of the HTTP health check to 200 seconds.

   Show answer

   Answer: D

   Explanation

   D is correct. The reason is that when you do health check, you want the VM to be working. Do the first check after initial setup time of 3 mins = 180 s < 200 s is reasonable.

   Source: Adapted from community discussion — Abalagu

   Next question

7. Question 217 · 325 in bank

   You need to select and configure compute resources for a set of batch processing jobs. These jobs take around 2 hours to complete and are run nightly. You want to minimize service costs. What should you do?

   • ASelect Google Kubernetes Engine. Use a single-node cluster with a small instance type.
   • BSelect Google Kubernetes Engine. Use a three-node cluster with micro instance types.
   • CSelect Compute Engine. Use preemptible VM instances of the appropriate standard machine type.
   • DSelect Compute Engine. Use VM instance types that support micro bursting.

   Show answer

   Answer: C

   Explanation

   As everyone has said the answer is C but here is the source for the information. "For example, batch processing jobs can run on preemptible instances. If some of those instances stop during processing, the job slows but does not completely stop. Preemptible instances complete your batch processing tasks without placing additional workload on your existing instances and without requiring you to pay full price for additional normal instances." srouce: https://cloud.google.com/compute/docs/instances/preemptible

   Source: Adapted from community discussion — gcper

   References

   • Google Cloud documentation

   Next question

8. Question 218 · 325 in bank

   You recently deployed a new version of an application to App Engine and then discovered a bug in the release. You need to immediately revert to the prior version of the application. What should you do?

   • ARun gcloud app restore.
   • BOn the App Engine page of the GCP Console, select the application that needs to be reverted and click Revert.
   • COn the App Engine Versions page of the GCP Console, route 100% of the traffic to the previous version.
   • DDeploy the original version as a separate application. Then go to App Engine settings and split traffic between applications so that the original version serves 100% of the requests.

   Show answer

   Answer: C

   Explanation

   correct is C NOT D. Option A is wrong as gcloud app restore was used for backup and restore and has been deprecated.Option B is wrong as there is no application revert functionality available.Option D is wrong as App Engine maintains version and need not be redeployed.

   Source: Adapted from community discussion — coldpar

   References

   • Google Cloud documentation
   • Google Cloud documentation
   • Google Cloud documentation
   • Google Cloud documentation
   • Google Cloud documentation

   Next question

9. Question 219 · 325 in bank

   You deployed an App Engine application using gcloud app deploy, but it did not deploy to the intended project. You want to find out why this happened and where the application deployed. What should you do?

   • ACheck the app.yaml file for your application and check project settings.
   • BCheck the web-application.xml file for your application and check project settings.
   • CGo to Deployment Manager and review settings for deployment of applications.
   • DGo to Cloud Shell and run gcloud config list to review the Google Cloud configuration used for deployment.

   Show answer

   Answer: D

   Explanation

   I would opt option D : as it would help to check the config details and Option A is not correct, as app.yaml would have only the runtime and script to run parameters and not the Project details

   Source: Adapted from community discussion — Bharathy

   References

   • Google Cloud documentation
   • Google Cloud documentation
   • Google Cloud documentation
   • Google Cloud documentation
   • Google Cloud documentation

   Next question

10. Question 220 · 325 in bank

    You want to configure 10 Compute Engine instances for availability when maintenance occurs. Your requirements state that these instances should attempt to automatically restart if they crash. Also, the instances should be highly available including during system maintenance. What should you do?

    • ACreate an instance template for the instances. Set the 'Automatic Restart' to on. Set the 'On-host maintenance' to Migrate VM instance. Add the instance template to an instance group.
    • BCreate an instance template for the instances. Set 'Automatic Restart' to off. Set 'On-host maintenance' to Terminate VM instances. Add the instance template to an instance group.
    • CCreate an instance group for the instances. Set the 'Autohealing' health check to healthy (HTTP).
    • DCreate an instance group for the instance. Verify that the 'Advanced creation options' setting for 'do not retry machine creation' is set to off.

    Show answer

    Answer: A

    Explanation

    A https://cloud.google.com/compute/docs/instances/setting-instance-scheduling-options onHostMaintenance: Determines the behavior when a maintenance event occurs that might cause your instance to reboot. [Default] MIGRATE, which causes Compute Engine to live migrate an instance when there is a maintenance event. TERMINATE, which stops an instance instead of migrating it. automaticRestart: Determines the behavior when an instance crashes or is stopped by the system. [Default] true, so Compute Engine restarts an instance if the instance crashes or is stopped. false, so Compute Engine does not restart an instance if the instance crashes or is stopped.

    Source: Adapted from community discussion — lio123

    References

    • Google Cloud documentation
    • Google Cloud documentation

    Next question

Keyboard:J Kmove between questionsA–Dselect an answerRshow or hide the answer← →change page

ACE practice, question 211. 325 questions available.