H13-821_V3.0 · Question #122
Through the Huawei application service grid ASM service, users can easily and quickly complete the entire process of grayscale publishing. Which of the following process descriptions about grayscale…
The correct answer is C. 1-4-6-3-5-2. Option C (1-4-6-3-5-2) is correct because it follows the only logical and safe sequence for grayscale publishing: first add the new version (1), then immediately verify it has come online with healthy instances (4), then configure the canary traffic-routing strategy to start…
Question
Through the Huawei application service grid ASM service, users can easily and quickly complete the entire process of grayscale publishing. Which of the following process descriptions about grayscale publishing is correct? check mark (1) Add a grayscale version (2) The original version is offline (3) Confirm that the status of the grayscale version is normal (4) Check that the grayscale version is online normally (confirm the numbers of instances/number of available instances) (5) Pass the verification and use the grayscale release version (6) Configure the canary grayscale strategy
Options
- A6-5-4-3-1-2
- B1-2-3-4-5-6
- C1-4-6-3-5-2
- D1-6-4-5-3-2
How the community answered
(25 responses)- A16% (4)
- B4% (1)
- C76% (19)
- D4% (1)
Explanation
Option C (1-4-6-3-5-2) is correct because it follows the only logical and safe sequence for grayscale publishing: first add the new version (1), then immediately verify it has come online with healthy instances (4), then configure the canary traffic-routing strategy to start sending a portion of traffic to it (6), then confirm the version remains stable under real traffic (3), then officially promote it as the release version (5), and finally take the original offline (2) only after the new version is fully validated. Option A (6-5-4-3-1-2) fails immediately because it tries to configure a canary strategy and pass verification before the grayscale version even exists. Option B (1-2-3-4-5-6) is dangerous because it takes the original version offline as the second step, leaving users with no fallback if the grayscale version has problems. Option D (1-6-4-5-3-2) configures the traffic strategy before confirming instances are healthy, and worse, it checks version status after promotion has already been decided, making the health check meaningless. A reliable memory anchor is that the original version must always be the very last thing to go offline -- the entire point of grayscale publishing is maintaining a safe fallback until the new version is fully proven, so any option where step 2 appears early can be eliminated immediately.
Topics
Community Discussion
No community discussion yet for this question.