- 7 views
Overview
Fabrikam, Inc is a manufacturing company that has a main office in New York and a branch office in Seattle.
Existing Environment
On-premises Servers
The on-premises network contains servers that run Windows Server as shown in the following table.

DC1 hosts all the operation master roles.
WEB1 and WEB2 run an Internet Information Services (IIS) web app named Webapp1.
On-premises Network
The New York and Seattle offices are connected by using redundant WAN links.
The client computers in each office get IP addresses from their local DHCP server.
DHCP1 contains a scope named Scope1 that has addresses for the New York office, DHCP2 contains a scope named Scope2 that has addresses for the Seattle office.
Identity Infrastructure
The network contains a single on-premises Active Directory Domain Services (AD DS) domain named corp.falbrikam.com. Currently, all the service accounts use individual domain user accounts.
All domain controllers have the DNS Server role installed and host a copy of the Active Directory integrated DNS zone of corp.fabrikam.com.
The corp.fabrikam.com AD DS domain syncs with an Azure Active Directory (Azure AD) tenant.
Group Policy Objects (GPOs)
The corp.fabrikam.com domain contains the organizational units (OUs) and custom Group Policy Objects (GPOs) shown in the following table.
Requirements
Planned Changes
Fabrikam identifies the following planned changes:
- Create a single Azure subscription named Sub1 that will contain a single Azure virtual network named Vnet1.
- Replace the WAN links between the Seattle and New York offices by using Azure Virtual WAN and FxpressRoute. Both on premises offices will be conected to Vnet1 by using ExpressRoute.
- Create three Azure file shares named newyorkhiles, seattlefiles, and companyfiles.
- Create a domain controller named dc3.corp.fabrikam.com in Vnet1.
- Deploy an Azure Virtual Desktop host pool to Vnet1. The Azure Virtual Desktop session hosts will be hybrid Azure AD-joined.
- License all servers for Microsoft Defender for servers.
- Use Azure Policy to enforce configuration management policies on the servers in Azure and on-premises.
Networking Requirements
Fabrikam identifies the following networking requirements:
- Implement Virtual WAN and ensure that all the network traffic between the sites uses Virtual WAN. All communications must occur over ExpressRoute.
- If a DHCP server fails, ensure that the client computers can continue to receive their dynamic IP address and renew their existing lease.
- Ensure that the resources in Vnet1 can resolve the names of the on-premises servers in the corp.fabrikam.com domain.
Security Requirements
Fabrikam identifies the following security requirements:
- Apply GPO4 to the Azure Virtual Desktop session hosts. Ensure that Azure Virtual Desktop user sessions lock after being idle for 10 minutes. Users must be able to control the lockout time manually from their client computer.
- Ensure that server administrators request approval before they can establish a Remote Desktop connection to an Azure virtual machine. If the request is aproved, the connection must be established within two hours.
- Prevent user passwords from containing all or part of words that are based on the company name, such as Fab, f@br1kAm or fabr!|.
- Ensure that all instances of Webapp1 use the same service account. The password of the service account must change automatically every 30 days.
- Prevent domain controllers from directly contacting hosts on the internet.
File Sharing Requirements
You need to configure the synchronization of Azure files to meet the following requirements:
- Ensure that seattlefiles syncs to FS2.
- Ensure that newyorkfiles syncs to FS1.
- Ensure that companyfiles syncs to both FS1 and FS2.
You need to implement an availability solution for DHCP that meets the networking requirements.
Which two actions should you perform? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.
- A. On DHCP1, create a scope that contains 25 percent of the IP addresses from Scope2.
- B. On the router in each office, configure a DHCP relay.
- C. DHCP2, configure a scope that contains 25 percent of the IP addresses from Scope1.
- D. On each DHCP server, install the Failover Clustering feature and add the DHCP cluster role.
- E. On each DHCP scope, configure DHCP failover.
- B. On the router in each office, configure a DHCP relay.
- E. On each DHCP scope, configure DHCP failover.
The suggested answer is correct
You need to configure DHCP Relay options, and configure on both servers DHCP failover
musmas82473
Highly Voted 2 years, 5 months ago
Correct Answers are DHCP failover (no split scope needed) & DHCP relay (as you need the IP helper to forward requests from different networks).
upvoted 14 times
AnonymousJhb
2 years, 4 months ago
yes B and E
upvoted 10 times
syu31svc
Most Recent 1 year, 8 months ago
Selected Answer: BE
E is a must so is part of the answer A DHCP relay agent is a host or router that forwards DHCP packets between clients and servers B is the other answer
upvoted 4 times
johosofat
2 years ago
Selected Answer: DE
Ok both links used to support the anweres here were not correct. one was a linux link and the other was incorrect. - the deploy and manage DHCP training page 6 discusses the dhcp failover and clustering- you cant have DHCP failover without a cluster... https://learn.microsoft.com/en-us/training/modules/deploy-manage-dynamic-host-configuration-protocol/6-select-dynamic-host-configuration-protocol-high-availability-options So the answers are d and e - but the issue with the other answer is why would you do split scope across this? the split scope is normally configed 75% 25% because its only used for backup. - of covering for a load... also the two offices are almost identical in function- so why would 25% be right? - the cluster answer is right and certainly makes more sense and is easier to setup.
upvoted 3 times
Verdural
2 years, 3 months ago
Correct Answers: - B On the router in each office, configure a DHCP relay - E On each DHCP scope, configure DHCP failover https://serverfault.com/questions/710642/symmetric-dhcp-failover-configuration
upvoted 3 times
SJHCI
2 years, 4 months ago
Selected Answer: BE
Confirmed BE.
upvoted 3 times
[Removed]
2 years, 4 months ago
Selected Answer: BE
DHCP failover (no split scope needed) & DHCP relay (as you need the IP helper to forward requests from different networks).
upvoted 2 times
bastien95
2 years, 4 months ago
Selected Answer: BE
DHCP failover for redundancy and DHCP relay to forward requests
upvoted 4 times
GoforIT21
2 years, 4 months ago
Correct, see https://docs.microsoft.com/en-us/learn/modules/deploy-manage-dynamic-host-configuration-protocol/7-implement-dynamic-host-configuration-protocol-failover. No need to install a failover clustering feature. The topology in the linked example is in one subnet. In the question here, a subnet boundary needs to be crossed, that's why B is also necessary.
upvoted 1 times
GoforIT21
2 years, 4 months ago
I meant to say that musmas82473's answer is correct. :-)
upvoted 2 times
RJM
2 years, 6 months ago
https://docs.microsoft.com/en-gb/archive/blogs/teamdhcp/multi-site-deployment-topologies-for-dhcp-failover
upvoted 2 times