You need to create a custom VPC with a single subnet. The subnet's range must be as large as possible.
Which range should you use?
0.0.0.0/0
10.0.0.0/8
172.16.0.0/12
192.168.0.0/16
Answer is 10.0.0.0/8
The question, is talking about custom VPC subnet and is not mentioning you will use automatic subnet mode creation. If you set subnet to custom, the minimum size is /8.
The private network range is defined by IETF (Ref: https://tools.ietf.org/html/rfc1918 ) and adhered to by all cloud providers. The supported internal IP Address ranges are;
1. 24-bit block 10.0.0.0/8 (16777216 IP Addresses)
2. 20-bit block 172.16.0.0/12 (1048576 IP Addresses)
3. 16-bit block 192.168.0.0/16 (65536 IP Addresses)
10.0.0.0/8 gives you the most extensive range - 16777216 IP Addresses.
Question 2
Several employees at your company have been creating projects with Cloud Platform and paying for it with their personal credit cards, which the company reimburses. The company wants to centralize all these projects under a single, new billing account.
What should you do?
Contact cloud-billing@google.com with your bank account details and request a corporate billing account for your company.
Create a ticket with Google Support and wait for their call to share your credit card details over the phone.
In the Google Platform Console, go to the Resource Manage and move all projects to the root Organizarion.
In the Google Cloud Platform Console, create a new billing account and set up a payment method.
Answer is In the Google Cloud Platform Console, create a new billing account and set up a payment method.
The question is under the organization different projects are maintained the different cloud platforms.all the different project should single corporate bill account instead of the employee billing account. So try to update the corporate bill account details and mark it as primary for the all projects, post that employee account details need to removed.
Option A is incorrect because you cannot request a corporate billing account by emailing cloud-billing@google.com. This email address is for general billing inquiries and support.
Option B is incorrect because you cannot create a ticket with Google Support to share your credit card details over the phone. To set up a payment method for a billing account, you must do it through the Google Cloud Platform Console.
Option C is incorrect because moving projects to the root organization will not create a new billing account. You must first create a new billing account and then move the projects to the root organization to ensure that they are all billed to the same billing account.
You want to select and configure a cost-effective solution for relational data on Google Cloud Platform. You are working with a small set of operational data in one geographic location. You need to support point-in-time recovery.
What should you do?
Select Cloud SQL (MySQL). Verify that the enable binary logging option is selected.
Select Cloud SQL (MySQL). Select the create failover replicas option.
Select Cloud Spanner. Set up your instance with 2 nodes.
Select Cloud Spanner. Set up your instance as multi-regional.
Answer is Select Cloud SQL (MySQL). Verify that the enable binary logging option is selected.
For a small set of operational data in one geographic location with the need to support point-in-time recovery, the most cost-effective solution on Google Cloud Platform would be option A, "Select Cloud SQL (MySQL). Verify that the enable binary logging option is selected."
Cloud SQL is a fully-managed relational database service that provides high availability and automatic backups, making it an ideal choice for small data sets that require point-in-time recovery. By enabling binary logging in Cloud SQL, you can perform point-in-time recovery and roll back changes to your database to a specific time in the past
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?
Create an HTTP load balancer with a backend configuration that references an existing instance group. Set the health check to healthy (HTTP)
Create 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.
Create a managed instance group. Set the Autohealing health check to healthy (HTTP)
Create a managed instance group. Verify that the autoscaling setting is on.
Answer is Create a managed instance group. Set the Autohealing health check to healthy (HTTP)
creating a managed instance group allows you to use autohealing to automatically recreate VMs that are unresponsive after 3 attempts of 10 seconds each. You can set the Autohealing health check to healthy (HTTP) to specify the health check that determines whether the instances are considered healthy or not. If an instance becomes unresponsive, Autohealing will recreate the instance and attach it to the managed instance group.
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.
You are using multiple configurations for gcloud. You want to review the configured Kubernetes Engine cluster of an inactive configuration using the fewest possible steps.
What should you do?
Use gcloud config configurations describe to review the output.
Use gcloud config configurations activate and gcloud config list to review the output.
Use kubectl config get-contexts to review the output.
Use kubectl config use-context and kubectl config view to review the output.
Answer is Use kubectl config use-context and kubectl config view to review the output.
"get-contexts" shows us our Kubernetes cluster contexts, that's right. But the question says that you want to review the cluster itself, so you need to use-context to get into the cluster.
Answer A: Using `gcloud config configurations described` will only show you the details of the current configuration, not the Kubernetes Engine cluster of an inactive configuration.
Answer B: Using `gcloud config configurations activate` and `gcloud config list` to review the output will only show you the list of configurations and activate one of them, but it won't provide you with the details of the Kubernetes Engine cluster of an inactive configuration.
Answer C: Using `kubectl config get-contexts` will only list the available contexts, including their clusters, but it won't provide you with the details of the Kubernetes Engine cluster of an inactive configuration.
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?
Manual Scaling with 3 instances.
Basic Scaling with min_instances set to 3.
Basic Scaling with max_instances set to 3.
Automatic Scaling with min_idle_instances set to 3.
Answer is 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).
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?
Deployment Manager
Cloud Composer
Managed Instance Group
Unmanaged Instance Group
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.
You have a Dockerfile that you need to deploy on Kubernetes Engine.
What should you do?
Use kubectl app deploy .
Use gcloud app deploy .
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.
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.
Answer is 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.
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?
Download and deploy the Jenkins Java WAR to App Engine Standard.
Create a new Compute Engine instance and install Jenkins through the command line interface.
Create a Kubernetes cluster on Compute Engine and create a deployment with the Jenkins Docker image.
Use GCP Marketplace to launch the Jenkins solution.
Answer is 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.
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?
Multi-Regional Storage
Regional Storage
Nearline Storage
Coldline Storage
Answer is 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.