Question
Your network contains an Active Directory Domain Services (AD DS) domain named contoso.com.
The network contains the servers shown in the following table.
| Name | Role | Domain/workgroup | Operating system |
| --- | --- | --- | --- |
| DC1 | Active Directory Domain Services, DNS Server | contoso.com | Windows Server |
| Server1 | DHCP Server | contoso.com | Windows Server |
| Server2 | None | contoso.com | Windows Server Core |
| Server3 | None | Workgroup1 | Windows Server Core |
You plan to implement IP Address Management (IPAM).
You need to use the Group Policy based provisioning method for managed servers. The solution must support server discovery.
What should you do? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
Hot Area:
Explanation
Server on which to deploy the IPAM server role: Server2 — The IPAM Server feature must be installed on a domain-joined member server, and Microsoft explicitly does not support installing IPAM on a domain controller or on the same machine as a DHCP server (IPAM disables DHCP server discovery on such a host), so DC1 is not a valid target and Server2 is the member server that carries no conflicting infrastructure role.
Servers that must be provisioned for IPAM: DC1 and Server1 — Provisioning applies only to the managed infrastructure servers that IPAM discovers and administers, namely the domain controllers, DNS servers, DHCP servers, and NPS servers in the domain; the IPAM server itself is never provisioned as a managed server. With Group Policy based provisioning, running Invoke-IpamGpoProvisioning creates the IPAM_DC_NPS_Server, IPAM_DHCP, and IPAM_DNS GPOs, and each discovered server has the matching GPO applied so IPAM gains the firewall rules, security group membership, and audit/share permissions it needs — hence DC1 (domain controller/DNS) and Server1 (DHCP) are the servers to provision, not Server2, which hosts IPAM itself.
