Your company has decided to make a major revision of their API in order to create better experiences for their developers. They need to keep the old version of the API available and deployable…

Question

Options

• AConfigure a new load balancer for the new version of the API.
• BReconfigure old clients to use a new endpoint for the new API.
• CHave the old API forward traffic to the new API based on the path.
• DUse separate backend pools for each API path behind the load balancer.

• A
  6% (2)
• B
  3% (1)
• C
  16% (5)
• D
  74% (23)

Explanation

A is not correct because a single load balancer with URL maps is sufficient. B is not correct because it goes against the requirements. The company wants to keep the old API available while new customers and testers try the new API. C is not correct because it is not a requirement to decommission the implementation behind the old API Moreover, it introduces unnecessary risk in case bugs or incompatibilities are discovered D is correct because an HTTP(S) load balancer can direct traffic reaching a single IP to different backends based on the incoming URL.

No community discussion yet for this question.