VDCA owns ECS namespace N and contains bucket B. VDCA owns bucket B. Bucket B is replicated to VDCB. During an outage at VDCA, the application connects to VDCB. What are two expected behaviors of…

Question

Options

• AIt cannot list the buckets in namespace N.
• BIt cannot access the contents of bucket B by explicitly referencing the bucket.
• CIt can list the buckets in namespace N.
• DIt can access the contents of bucket B by explicitly referencing the bucket.

• A
  17% (7)
• B
  21% (9)
• C
  62% (26)

Explanation

When bucket B is replicated from VDCA to VDCB in an ECS replication group, both the bucket data and the associated namespace metadata are replicated. This means VDCB holds a full, functional copy of namespace N's structure (enabling bucket listing) as well as the actual object data in bucket B (enabling direct access). Even with VDCA completely offline, VDCB can independently satisfy both types of requests because replication is not just a data mirror - it includes the namespace layer needed to resolve bucket listings.

Why A is wrong: The namespace N metadata is part of what gets replicated to VDCB, so listing buckets within that namespace remains possible at the replica site during an outage.

Why B is wrong: Since bucket B itself is replicated (not just referenced) to VDCB, explicitly addressing bucket B from VDCB works - the data lives there locally.

Memory tip: Think "replication = full copy, not a redirect." A replicated bucket brings its namespace context with it, so the replica VDC behaves as a self-sufficient owner for both metadata (list) and data (access) operations during a primary-site outage.

No community discussion yet for this question.