| Question.6 You are deploying an application to App Engine. You want the number of instances to scale based on request rate. You need at least 3 unoccupied instances at all times. Which scaling type should you use? (A) Manual Scaling with 3 instances. (B) Basic Scaling with min_instances set to 3. (C) Basic Scaling with max_instances set to 3. (D) Automatic Scaling with min_idle_instances set to 3. |
6. Click here to View Answer
Answer is (D) Automatic Scaling with min_idle_instances set to 3.
App Engine calculates the number of instances necessary to serve your current application traffic based on scaling settings such as target_cpu_utilization and target_throughput_utilization. Setting min_idle_instances specifies the number of instances to run in addition to this calculated number. For example, if App Engine calculates that 5 instances are necessary to serve traffic, and min_idle_instances is set to 2, App Engine will run 7 instances (5, calculated based on traffic, plus 2 additional per min_idle_instances).
Reference:
https://cloud.google.com/appengine/docs/standard/go/config/appref
| Question.7 You need a dynamic way of provisioning VMs on Compute Engine. The exact specifications will be in a dedicated configuration file. You want to follow Google’s recommended practices. Which method should you use? (A) Deployment Manager (B) Cloud Composer (C) Managed Instance Group (D) Unmanaged Instance Group |
7. Click here to View Answer
Answer is Deployment Manager
Deployment Manager is a configuration management tool that allows you to define and deploy a set of resources, including Compute Engine VMs, in a declarative manner. You can use it to specify the exact specifications of your VMs in a configuration file, and Deployment Manager will create and manage those VMs for you. Deployment Manager is recommended by Google as a way to automate and manage the deployment of resources on the Google Cloud Platform.
| Question.8 You have a Dockerfile that you need to deploy on Kubernetes Engine. What should you do? (A) Use kubectl app deploy . (B) Use gcloud app deploy . (C) Create a docker image from the Dockerfile and upload it to Container Registry. Create a Deployment YAML file to point to that image. Use kubectl to create the deployment with that file. (D) Create a docker image from the Dockerfile and upload it to Cloud Storage. Create a Deployment YAML file to point to that image. Use kubectl to create the deployment with that file. |
8. Click here to View Answer
Answer is (C) Create a docker image from the Dockerfile and upload it to Container Registry. Create a Deployment YAML file to point to that image. Use kubectl to create the deployment with that file.
To deploy a Docker container on Kubernetes Engine, you should first create a Docker image from the Dockerfile and push it to Container Registry, which is a fully-managed Docker container registry that makes it easy for you to store, manage, and deploy Docker container images. Then, you can create a Deployment YAML file that specifies the image to use and other desired deployment options, and use the kubectl command-line tool to create the deployment based on the YAML file.
Option A is incorrect because kubectl app deploy is not a valid command.
Option B is incorrect because gcloud app deploy is used to deploy applications to App Engine, not Kubernetes Engine.
Option D is incorrect because it involves storing the image in Cloud Storage rather than Container Registry.
Reference:
https://cloud.google.com/kubernetes-engine/docs/how-to/deploying-a-container
| Question.9 Your development team needs a new Jenkins server for their project. You need to deploy the server using the fewest steps possible. What should you do? (A) Download and deploy the Jenkins Java WAR to App Engine Standard. (B) Create a new Compute Engine instance and install Jenkins through the command line interface. (C) Create a Kubernetes cluster on Compute Engine and create a deployment with the Jenkins Docker image. (D) Use GCP Marketplace to launch the Jenkins solution. |
9. Click here to View Answer
Answer is (D) Use GCP Marketplace to launch the Jenkins solution.
By using GCP Marketplace to launch the Jenkins solution, you can quickly deploy a Jenkins server with minimal steps.
Option A involves deploying the Jenkins Java WAR to App Engine Standard, which requires more steps and may not be suitable for your requirements.
Option B involves creating a new Compute Engine instance and manually installing Jenkins, which also requires more steps.
Option C involves creating a Kubernetes cluster and creating a deployment with the Jenkins Docker image, which again involves more steps and may not be the most efficient solution.
Reference:
https://cloud.google.com/solutions/using-jenkins-for-distributed-builds-on-compute-engine
| Question.10 Your company uses Cloud Storage to store application backup files for disaster recovery purposes. You want to follow Google’s recommended practices. Which storage option should you use? (A) Multi-Regional Storage (B) Regional Storage (C) Nearline Storage (D) Coldline Storage |
10. Click here to View Answer
Answer is (D) Coldline Storage
Cloud Storage Coldline: a low-latency storage class for long-term archiving
Coldline is a new Cloud Storage class designed for long-term archival and disaster recovery. Coldline is perfect for the archival needs of big data or multimedia content, allowing businesses to archive years of data. Coldline provides fast and instant (millisecond) access to data and changes the way that companies think about storing and accessing their cold data.