Which issue requires elastic scale-out?

Question

Options

• AMitigating disruption if a Controller fails
• BManaging heavy increases in traffic volume without disruption
• CHandling Layer 7 processing such as SSL Termination or Web Application Firewall
• DProcessing requests across multiple protocols

• A
  3% (1)
• B
  94% (32)
• D
  3% (1)

Explanation

Elastic scale-out means dynamically adding more instances/nodes to handle increased demand - it's fundamentally a solution to variable or unpredictable traffic volume (B). When traffic spikes, you scale out horizontally; when it drops, you scale back in, all without service disruption.

• A is wrong because Controller failover is a high availability / redundancy concern, solved by clustering or failover mechanisms, not by scaling out.
• C is wrong because SSL termination and WAF are Layer 7 feature concerns, addressed by load balancer capabilities or dedicated appliances, not by adding more capacity.
• D is wrong because multi-protocol support is a feature/compatibility requirement, not a capacity problem - it's solved by protocol-aware proxies or gateways.

Memory tip: "Elastic" = rubber band - it stretches when load grows and shrinks when load drops. Any time an exam question mentions handling surges, spikes, or heavy increases in traffic, think elastic scale-out.

No community discussion yet for this question.