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.

Option B (changing to DHCP Relay) is incorrect because relay mode does not configure DNS/NTP---it delegates DHCP to an external DHCP server. Option C (enable DNS/NTP passthrough) is not a feature of NSX DHCP. Option D (changing connectivity mode) affects routing and service placement, not DHCP options.