When designing resiliency for potential failure scenarios in ECS, which of the following is least effective?

Question

Options

• AMulti-region deployment for critical services
• BRegular vulnerability assessments and patching
• CRelying solely on physical security measures
• DImplementing robust data encryption techniques

• A
  8% (3)
• B
  3% (1)
• C
  84% (31)
• D
  5% (2)

Explanation

Relying solely on physical security measures (C) is the least effective resiliency strategy because physical security - like locked server rooms - does nothing to address software failures, network outages, container crashes, or distributed system faults that are the primary failure scenarios in ECS environments.

Why the distractors are wrong:

• A is highly effective - multi-region deployment ensures services survive regional AWS outages or data center failures, a core ECS resiliency pattern.
• B is effective - vulnerability assessments and patching reduce the attack surface and prevent failures caused by exploited weaknesses in container images or the underlying EC2/Fargate infrastructure.
• D is effective - encryption protects data integrity and confidentiality during transit and at rest, guarding against data corruption and breaches that could cause service failures.

Memory tip: Think "ECS lives in the cloud, not a cage." Physical security protects hardware you can touch; ECS resiliency is about surviving logical failures - bad deployments, network partitions, and resource exhaustion. Any answer that addresses only the physical layer while ignoring software/network concerns will always be the weakest choice for cloud-native resiliency questions.

No community discussion yet for this question.