A customer must separate ECS S3 traffic on two different VLANs. What should a technology architect recommend?

Question

Options

• ACreate s3.data and s3.data2 interfaces.
• BCreate public.data and public.data2 interfaces.
• CCreate public.mgmt and public.data interfaces.
• DCreate s3.mgmt and s3.data interfaces.

• A
  8% (2)
• B
  73% (19)
• C
  4% (1)
• D
  15% (4)

Explanation

Option B is correct because Dell EMC ECS (Elastic Cloud Storage) uses public as the required prefix for all network interfaces, and to route S3 data traffic across two separate VLANs you create public.data and public.data2 - the numbered suffix is the supported ECS convention for adding a second data interface on a distinct VLAN.

Why the distractors are wrong:

• A & D use s3 as the interface prefix, which is not a valid ECS interface naming convention - ECS only recognizes the public prefix.
• C (public.mgmt + public.data) separates management traffic from data traffic, which is a different design goal; it does not give you two separate VLANs both carrying S3 data.

Memory tip: Think "public = ECS prefix, always." Then remember that ECS data interfaces just append a number for additional VLANs: .data, .data2, .data3, etc. If a choice swaps public for a protocol name like s3, it's wrong.

No community discussion yet for this question.