Which design consideration is least relevant when creating a multi-tenant ECS solution?

Question

Options

• AThe color scheme of the tenant's logo
• BIsolation of network traffic between tenants
• CData encryption at rest and in transit
• DImplementation of quotas and limits per tenant

• A
  88% (29)
• B
  3% (1)
• C
  6% (2)
• D
  3% (1)

Explanation

Option A is correct because logo color schemes are a UI/branding concern with no bearing on the architectural integrity, security, or resource management of a multi-tenant ECS platform - it's simply not a design consideration at the infrastructure level.

Why the distractors are wrong:

• B (network isolation) is critical - tenants must not be able to access each other's traffic, making VPC segmentation, security groups, and namespace isolation essential design decisions.
• C (encryption) is a core security requirement - multi-tenant environments must protect each tenant's data from other tenants and external threats, both at rest (EBS/S3) and in transit (TLS).
• D (quotas and limits) is fundamental - without per-tenant resource constraints, a single noisy tenant can starve others of CPU, memory, or API rate limits, breaking the shared-infrastructure model.

Memory tip: Think of it as the "NERD" rule for multi-tenancy - Network isolation, Encryption, Resource limits, and Data separation are the pillars. Anything outside those pillars (like branding) belongs to the application layer, not the infrastructure design.

No community discussion yet for this question.