As shown in the figure, which of the following descriptions of the container and microservice engine architecture is wrong?

Question

Options

• AConfigure and use rolling upgrades for CCE and CCI to ensure interface compatibility between new
• BRationally configure CCE cluster expansion strategies and application scaling strategies to cope with
• CConfigure API backend timeouts and coordinate with client retry and circuit breaking capabilities to
• DApplication Operation and Maintenance Management (AOM) and Application Performance

• A
  4% (2)
• B
  11% (5)
• C
  70% (32)
• D
  15% (7)

Explanation

Option C is marked as the wrong description because in a microservice architecture, API backend timeouts, client-side retries, and circuit breaking must be configured with strict sequencing and hierarchy - not merely "coordinated." Specifically, the backend timeout should be shorter than the client timeout, and the circuit breaker threshold must account for retry amplification; treating these as loosely cooperative rather than strictly ordered can cause cascading failures rather than preventing them.

Why the distractors (A, B, D) are correct:

• A is correct: Rolling upgrades on CCE/CCI are a standard strategy to maintain backward interface compatibility during version transitions.
• B is correct: Configuring cluster auto-scaling (HPA/CA) alongside application scaling policies is a well-established best practice for handling variable load.
• D is correct: AOM and APM are complementary monitoring layers - infrastructure-level and application-level - and using both together is a recommended observability pattern.

Memory tip: Think of timeout and circuit breaking configuration as a waterfall, not a handshake - each layer (client → gateway → backend) must be set with progressively shorter timeouts so failures fail fast and don't stack up. Any answer that implies these can be independently or loosely configured is describing it wrong.

No community discussion yet for this question.