HPE6-A87 · Question #28
Which method is recommended for high-availability deployment of Fabric Composer?
The correct answer is B. Deploying multiple instances across different hosts. Deploying multiple instances across different hosts (B) is the standard high-availability pattern because it eliminates single points of failure - if one host goes down, other instances continue serving requests, ensuring continuity. VLAN-based redundancy (A) addresses network…
Question
Which method is recommended for high-availability deployment of Fabric Composer?
Options
- AUsing VLAN-based redundancy
- BDeploying multiple instances across different hosts
- CInstalling on a single physical server
- DUsing DHCP-based failover
How the community answered
(37 responses)- A3% (1)
- B86% (32)
- C8% (3)
- D3% (1)
Explanation
Deploying multiple instances across different hosts (B) is the standard high-availability pattern because it eliminates single points of failure - if one host goes down, other instances continue serving requests, ensuring continuity. VLAN-based redundancy (A) addresses network segmentation, not application-level availability, and doesn't protect against host or software failures. A single physical server (C) is the opposite of high availability - it concentrates all risk on one machine. DHCP-based failover (D) is a network IP management technique unrelated to application deployment resilience.
Memory tip: Think "HA = spread the risk." Any time you see "high availability," the correct answer almost always involves distributing instances across multiple independent hosts - never consolidating onto one.
Topics
Community Discussion
No community discussion yet for this question.