Which are the two asynchronous file-replication configuration requirements? (Choose two.)

Question

Options

• AMap the File Mobility Network to Management Network
• BConfigure the File Mobility Network IP address on Management subnet and VLAN
• CConfigure the File Mobility Network IP address on Storage Network subnet and VLAN
• DMap the File Mobility Network to Storage Network

• A
  6% (1)
• C
  94% (16)

Explanation

For asynchronous file replication, the File Mobility Network must be tied to the Storage Network - both in terms of IP addressing (C) and network mapping (D). This is because file replication traffic is data-plane activity that flows over storage infrastructure, not the management plane. Using the Storage Network subnet/VLAN and mapping to the Storage Network ensures replication traffic stays on the appropriate high-throughput, low-latency path.

Why A and B are wrong: Options A and B both point toward the Management Network, which handles administrative/control traffic (UI, SSH, monitoring). Routing replication data through the Management Network would create a bottleneck, mix traffic types inappropriately, and is not a supported configuration requirement for async replication.

Memory tip: Think "Storage replicates Storage." Async file replication moves large amounts of data between systems - that's a storage job, so both the IP configuration (C) and the network mapping (D) belong on the Storage Network. If you see "Management Network" in an answer about replication traffic, it's almost certainly a distractor.

No community discussion yet for this question.