Which approach is least effective in designing a multi-tenant architecture for ECS?

Question

Options

• AImplementing strict quota management for each tenant
• BEnforcing tenant isolation at the network layer
• CAllocating the same computational resources to all tenants, regardless of need
• DUsing separate storage buckets for each tenant

• A
  15% (6)
• B
  23% (9)
• C
  56% (22)
• D
  5% (2)

Explanation

Allocating identical computational resources to all tenants regardless of their actual needs (C) is the least effective approach because it leads to resource waste for low-usage tenants and potential starvation for high-demand ones - directly undermining the efficiency goals of multi-tenancy. Options A, B, and D are all recommended practices: quota management (A) prevents any single tenant from monopolizing shared infrastructure (the "noisy neighbor" problem), network-layer isolation (B) ensures tenants cannot access each other's traffic or services, and separate storage buckets (D) enforce data isolation and simplify access control per tenant. Think of it this way: good multi-tenancy = fair + isolated - options A, B, and D each enforce one of those properties, while C ignores fairness entirely. A memory tip: watch for answers that treat all tenants as identical - real-world tenants have varying workloads, so "one size fits all" resource allocation is almost always the wrong answer on cloud architecture exams.

No community discussion yet for this question.