An administrator created a new VPC with an associated subnet, configured with a DHCP Server. When attaching virtual machines to the VPC subnet, an IP address is assigned, but the DNS and NTP…

Question

Options

• AUpdate the default VPC Service Profile to include the IP addresses for the DNS and NTP servers.
• BChange the DHCP Server mode from DHCP Server to DHCP Relay.
• CEnable DNS and NTP Passthrough on the DHCP Server.
• DSwitch the DHCP Network mode from Distributed Connectivity to Centralized Connectivity.

• A
  76% (31)
• B
  5% (2)
• C
  15% (6)
• D
  5% (2)

Explanation

In VMware Cloud Foundation 9.0 Automation, each VPC is governed by a VPC Service Profile, which defines the default network services applied to the VPC's DHCP server--this includes DNS servers, NTP servers, DHCP lease values, and other network attributes. When a subnet is associated with a VPC and DHCP is enabled, the DHCP service inherits its DNS and NTP configuration from the VPC Service Profile. In the scenario, virtual machines attached to the new VPC subnet receive an IP address, but not DNS or NTP settings. This indicates that the DHCP server is functioning correctly, but its service profile lacks DNS and NTP configuration. Updating the default VPC Service Profile allows the administrator to specify DNS resolver addresses and NTP time sources, which will then automatically be pushed to all DHCP-enabled subnets under that VPC.

No community discussion yet for this question.