An application runs on a fleet of Amazon EC2 instances in a VPC. All instances can reach one another using private IP addresses. The application owner has a new requirement that the domain name…

Question

Options

• AModify the existing DHCP option set and specify the different domain name for the specified
• BCreate a new DHCP option set with the different domain name, associate it with the specified
• CCreate a new subnet, configure the DHCP option set with the different domain name, and re-
• DCreate a new peered VPC, configure the DHCP option set with the different domain name, and

• A
  14% (2)
• B
  21% (3)
• C
  7% (1)
• D
  57% (8)

Explanation

https://docs.aws.amazon.com/vpc/latest/userguide/VPC_DHCP_Options.html After you create a set of DHCP options, you can't modify them. If you want your VPC to use a different set of DHCP options, you must create a new set and associate them with your VPC. You can also set up your VPC to use no DHCP options at all. You can have multiple sets of DHCP options, but you can associate only one set of DHCP options with a VPC at a time. If you delete a VPC, the DHCP options set that is associated with the VPC is disassociated from the VPC. You will have to create a new VPC and peer them since you cannot change DHCP per subnet

No community discussion yet for this question.