You have created an HTTP(S) load balanced service. You need to verify that your backend instances are responding properly.
How should you configure the health check?

• A. Set request-pathto a specific URL used for health checking, and set proxy-headerto PROXY_V1.
• B. Set request-path to a specific URL used for health checking, and set responseto a string that the backend service will always return in the response body.
• C. Set proxy-header to the default value, and set hostto include a custom host header that identifies the health check.
• D. Set request-path to a specific URL used for health checking, and set hostto include a custom host header that identifies the health check.

Erklärung: (Nur für ITZert-Mitglieder sichtbar)

Your organization requires its cloud network environment to inspect and deny traffic through a third party virtual firewall appliance. You currently operate a single standalone appliance, which is the next-hop target of a custom static route. You have recently deployed a new redundant appliance for high availability and load-sharing. You need to route the cloud network traffic through these appliances in an active/active configuration, while avoiding asymmetric routing.
You also need to deploy this configuration with minimal traffic disruption and follow Google- recommended practices. What should you do?

• A. Configure an internal passthrough network load balancer to send traffic to the redundant appliance. Then configure a packet mirroring policy that mirrors all traffic from the pre-existing standalone appliance to the new redundant appliance.
• B. Create routes for both appliances at the same priority, but higher than the existing standalone appliance's route. Then remove the pre-existing route that directed traffic to the standalone appliance.
• C. Configure an internal passthrough network load balancer to balance traffic to both appliances.
  Create a route with this internal load balancer as a next hop at a higher priority than the existing route. Then remove the pre-existing route that directed traffic to the standalone appliance.
• D. Create a route for the redundant appliance at the same priority as the pre-existing standalone appliance.

Erklärung: (Nur für ITZert-Mitglieder sichtbar)

Your company runs an enterprise platform on-premises using virtual machines (VMs). Your internet customers have created tens of thousands of DNS domains pointing to your public IP addresses allocated to the VMs. Typically, your customers hard-code your IP addresses in their DNS records. You are now planning to migrate the platform to Compute Engine and you want to use Bring Your Own IP. You want to minimize disruption to the platform. What should you do?

• A. Verify ownership of your IP addresses. Use live migration to import the prefix. Assign the IP addresses to the Compute Engine instances.
• B. Verify ownership of your IP addresses. After the verification, Google Cloud advertises and provisions the IP prefix for you. Assign the IP addresses to the Compute Engine instances.
• C. Create a VPC and request static external IP addresses from Google Cloud. Assign the IP addresses to the Compute Engine instances. Notify your customers of the new IP addresses so they can update their DNS records.
• D. Create a VPC with the same IP address range as your on-premises network. Assign the IP addresses to the Compute Engine instances.

Erklärung: (Nur für ITZert-Mitglieder sichtbar)

You have a data workflow which consists of data ingestion layer, data transformation layer, data analytics layer and data storage layer. You are looking for a service that would ease the tasks of creating, scheduling, monitoring and managing workflows without dealing with the management of the infrastructure .Please select the right service that would fulfil the requirement.

• A. Stackdriver
• B. Apache Airflow
• C. Istio
• D. Cloud Composer

Erklärung: (Nur für ITZert-Mitglieder sichtbar)

You have installed Apache Tomcat 8.X on a compute engine in google cloud on port 8085 and you have also installed Jenkins on the same machine on a custom port. You have created a firewall rule that allows traffic to port 8085. You can see the Apache Tomcat page when you browse X.X.X.X:8085, but when you browse X.X.X.X:custom port, the Jenkins page doesn't load.
What could be the possible solution? Please select the right choice.

• A. Create a firewall rule; select the correct subnet which has the compute engine and allow all protocols and ports.
• B. Create a firewall rule; select the correct subnet, create a target tag attach it to the compute engine instance and allow all protocols and ports.
• C. Create a firewall rule; select the correct network and select the target as all instances in the network and specify the custom port and protocol.
• D. Create a firewall rule; select the correct network, create a target tag and attach the tag to the compute engine instance and allow traffic to custom port that is mapped with Jenkins.

Erklärung: (Nur für ITZert-Mitglieder sichtbar)