Google Professional Cloud Network Engineer Question 449
Select 2Google Cloud PlatformYour company is deploying a new version of a web application on Google Cloud using an Application Load Balancer (ALB). The deployment requires gradually increasing traffic to the new version while still serving the existing version. Additionally, certain HTTP requests need to be routed to a specific backend service based on the URL path. How can you configure the ALB to meet these requirements?
- A
Configure traffic splitting on the ALB to gradually increase traffic to the new backend service.
- B
Use traffic mirroring to send a copy of the incoming requests to the new backend service for testing.
- C
Set up URL-based routing rules to direct specific URL paths to a designated backend service.
- D
Enable session affinity to ensure users are consistently routed to the same backend service.
- E
Use HTTP(S) redirect rules to forward all incoming traffic to the new version of the application.
Show answer and explanation
Correct answers: A, C
Explanation
To meet the requirements of gradually increasing traffic to the new version and routing specific HTTP requests based on URL paths, you need to configure traffic splitting and URL-based routing on the Application Load Balancer. Traffic splitting enables controlled rollouts by distributing traffic between backend services, while URL-based routing ensures specific requests are sent to appropriate backend services. Other options like traffic mirroring, session affinity, and HTTP(S) redirects are not suitable for these requirements.
- A. Correct.
Correct. Traffic splitting allows you to distribute incoming traffic between different backend services, enabling gradual rollout to the new version of the application.
- B. Incorrect.
Incorrect. Traffic mirroring duplicates traffic for testing purposes but does not enable gradual rollout, which is required in this scenario.
- C. Correct.
Correct. URL-based routing allows you to define rules to route traffic to specific backend services based on the URL path, meeting the requirement to handle specific HTTP requests.
- D. Incorrect.
Incorrect. Session affinity ensures consistency for user sessions but does not address the need for traffic splitting or URL-based routing.
- E. Incorrect.
Incorrect. HTTP(S) redirect rules forcefully redirect all traffic to another location but do not allow for gradual rollout or URL-based routing.