Google Cloud Exam Preparation: Creating Health Checks for HTTP(s) Load Balancing

Create New Health Check for HTTP(s) Load Balancing

Prev Question Next Question

Question

You are creating an instance group and need to create a new health check for HTTP(s) load balancing.

Which two methods can you use to accomplish this? (Choose two.)

Answers

A. Create a new health check using the gcloud command line tool.

B. Create a new health check using the VPC Network section in the GCP Console.

C. Create a new health check, or select an existing one, when you complete the load balancer`s backend configuration in the GCP Console.

D. Create a new legacy health check using the gcloud command line tool.

E. Create a new legacy health check using the Health checks section in the GCP Console.

Show Answer

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D. E.

AE.

https://cloud.google.com/load-balancing/docs/health-checks

When creating an instance group and configuring HTTP(s) load balancing, you can create a new health check using two different methods:

A. Create a new health check using the gcloud command line tool: You can create a new health check using the gcloud command line tool by specifying the type of health check, the protocol to use (HTTP or HTTPS), the request path, and other parameters. The command looks like this:

css
gcloud compute health-checks create http [HEALTH_CHECK_NAME] --port [PORT_NUMBER] --request-path [REQUEST_PATH]

For example, if you wanted to create a new HTTP health check with the name "my-health-check", you would run the following command:

sql
gcloud compute health-checks create http my-health-check --port 80 --request-path /

B. Create a new health check using the VPC Network section in the GCP Console: You can also create a new health check by navigating to the VPC Network section of the GCP Console, selecting the "Health checks" tab, and clicking the "Create health check" button. From there, you can specify the type of health check (HTTP or HTTPS), the request path, and other parameters.

C. Create a new health check, or select an existing one, when you complete the load balancer's backend configuration in the GCP Console: When you are configuring the backend for your load balancer in the GCP Console, you have the option to create a new health check or select an existing one. You can specify the type of health check (HTTP or HTTPS), the request path, and other parameters.

D. Create a new legacy health check using the gcloud command line tool: Legacy health checks are deprecated and should not be used for new deployments. Therefore, this option is not recommended.

E. Create a new legacy health check using the Health checks section in the GCP Console: This option is also not recommended for new deployments, as legacy health checks are deprecated.

In summary, options A and B allow you to create a new health check for HTTP(s) load balancing, while option C allows you to create a new health check or select an existing one during the backend configuration process. Options D and E are not recommended, as legacy health checks are deprecated.

Prev Question Next Question