As long as the latency and isolation conditions are met, a physical AZ can belong to two physical AZ groups at the same time.

Question

Options

• ATrue
• BFalse

• A
  84% (31)
• B
  16% (6)

Explanation

Option A is correct because physical AZ membership in logical AZ groups is not mutually exclusive - what matters is whether the zone satisfies the required conditions for each group it belongs to, specifically that inter-AZ latency thresholds are met and that the zone maintains fault isolation from other zones in the group. Cloud infrastructure designs allow overlapping logical groupings of the same physical assets when those groupings serve different architectural purposes (e.g., one group optimized for geographic proximity, another for regulatory boundaries).

Option B is wrong because it assumes strict one-to-one membership between a physical AZ and a single group, but nothing in the latency/isolation model technically prevents a zone from qualifying for and belonging to more than one group simultaneously.

Memory tip: Think of AZ groups like overlapping sports leagues - a team (physical AZ) can compete in two leagues at once as long as it meets each league's eligibility rules (latency + isolation). The physical team doesn't change; only the grouping context does.

No community discussion yet for this question.