Which solution will meet these requirements?
Create a beta stage for the new version of the API. Send the updated endpoint to the users.
Create a development stage for the new version of the API. Use a canary deployment.
Create a development stage for the new version of the API. Promote a canary release.
Create a deployment stage. Enable mutual TLS for the new version of the API.
Explanations:
Creating a beta stage does not minimize the impact on users because sending the updated endpoint to users would cause them to access the new version directly. This would not allow gradual testing with minimal disruption.
Using a development stage for the new version of the API and enabling a canary deployment allows for testing with minimal impact. The canary deployment enables a small portion of traffic to be directed to the new version, which allows for safe testing before full-scale rollout.
A canary release is the correct approach, but promoting it is unnecessary here. The key is to test the canary release first, and there’s no need to “promote” it in this context. The option wording suggests an unnecessary step.
Enabling mutual TLS for the new version of the API provides secure communication but does not address the need to test the new version with minimal impact. Mutual TLS does not solve the problem of testing with a controlled amount of traffic to avoid affecting users.
I surmise that the answer is:
Create a development stage for the new version of the API. Use a canary deployment.
From my perspective, the answer is:
Create a development stage for the new version of the API. Use a canary deployment.