An administrator is enabling IPv6-to-IPv4 communication for workloads hosted in an NSX environment. The workloads use IPv6-only addressing, but the external systems they must reach are IPv4-only. To…

Question

Options

• ANAT64 is stateless and requires gateways to be deployed in active-standby mode.
• BNAT64 requires the Tier-1 gateway to be configured in active-standby mode.
• CNAT64 is supported on Tier-1 gateways only.
• DNAT64 is supported on Tier-0 and Tier-1 gateways.
• ENAT64 requires the Tier-1 gateway to be configured in active-active mode.

• A
  17% (5)
• B
  72% (21)
• C
  3% (1)
• E
  7% (2)

Explanation

As organizations modernize their infrastructure with VCF 5.x and 9.0, IPv6 adoption becomes more prevalent. NAT64 is a critical transition technology that allows IPv6-only hosts to communicate with IPv4-only resources by translating the packet headers. In NSX, NAT64 is a stateful service. Stateful services in the NSX architecture require a centralized point of processing to maintain the session state table. Because of this requirement, any gateway (Tier-0 or Tier-1) providing NAT64 services must be configured in Active-Standby high availability mode. In Active-Active mode, asymmetric return traffic could hit a different Edge node that does not have the session information, causing the translation to fail. This is a fundamental design constraint for stateful NAT in NSX. Furthermore, VMware NSX documentation specifies that NAT64 is a flexible service that can be implemented at multiple tiers of the logical routing hierarchy. It is supported on both Tier-0 and Tier- 1 gateways. The choice of where to place the NAT64 service depends on the design placing it on the Tier-1 gateway allows for tenant-specific translation and offloads the Tier-0, while placing it on the Tier-0 provides a centralized translation point for all connected segments. Option A is incorrect because NAT64 in NSX is stateful, not stateless. Option C is incorrect because it is not limited to Tier-1. Option E is incorrect because Active-Active mode does not support the stateful nature of the NAT64 engine. Consequently, the correct architecture requires an Active- Standby configuration on either a Tier-0 or Tier-1 gateway to properly facilitate the translation between the IPv6 workloads and the IPv4 external world.

No community discussion yet for this question.