An organization has implemented a monitoring system and is focused on separating the replication traffic monitoring. Which ECS network separation deployment is recommended to separate replication…

Question

Options

• AAll Separated with management traffic on public.mgmt, replication traffic on public.repl, and data traffic
• BDual with data and replication traffic on the public network and management traffic on the public.mgmt
• CDual with management and data traffic on the public network and replication traffic on the public.repl
• DDual with management and replication traffic on the public network and data traffic on the public.data

• A
  4% (1)
• B
  8% (2)
• C
  76% (19)
• D
  12% (3)

Explanation

Option C is correct because the Dual deployment model uses exactly two networks, and placing replication traffic on its own dedicated public.repl network while grouping management and data traffic together on the public network achieves the stated goal: replication traffic is fully isolated from everything else.

Why the distractors fail:

• B is wrong because it groups replication with data on the public network - replication is not separated.
• D is wrong because it groups replication with management on the public network - again, replication is not separated.
• A is wrong not because it fails to separate replication, but because "All Separated" is a three-network model (overkill) used when all three traffic types need isolation, not just replication - it's a different use case than what's described.

Memory tip: Think "Dual = split in two." When the requirement is only to isolate replication, a Dual deployment gives replication its own lane (public.repl) and puts everything else on the main public road. If all traffic types need their own lane, then you'd escalate to All Separated.

No community discussion yet for this question.