In a multi-tenant ECS environment, which feature ensures that one tenant cannot access another tenant's data?

Question

Options

• AGlobal read/write permissions for efficiency
• BTenant-specific namespaces
• CA single, common database for all tenants
• DIdentical encryption keys for all tenants

• B
  93% (38)
• C
  2% (1)
• D
  5% (2)

Explanation

Tenant-specific namespaces (B) provide logical isolation boundaries that scope each tenant's resources, services, and data exclusively to that tenant - preventing cross-tenant access by design.

Option A is the opposite of isolation; global read/write permissions would allow any tenant to read or modify any other tenant's data, creating a serious security breach. Option C is wrong because a single shared database without namespace-level partitioning makes it trivially easy for one tenant's queries to leak into another's data. Option D is wrong because identical encryption keys defeat the purpose of encryption entirely - if Tenant A holds the same key as Tenant B, A can decrypt B's data.

Memory tip: Think of namespaces like apartment mailboxes - each tenant has their own locked slot with a unique label. Shared databases (C) and shared keys (D) are like leaving all mail in one unlocked pile; global permissions (A) is like giving everyone a master key. Only Namespaces give each tenant their own Niche.

No community discussion yet for this question.