- 18 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 a name resolution solution 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. Configure the DNS Servers settings for Vnet1.
- B. On DC3, install the DNS Server role.
- C. Create a virtual network link in the corp.fabrikam.com Azure private DNS zone.
- D. Configure a conditional forwarder on DC3.
- E. Enable autoregistration in the corp.fabrikam.com Azure private DNS zone.
- F. Create an Azure private DNZ zone named corp.fabrikam.com.
- G. Create an Azure DNZ zone named corp.fabrikam.com.
- A. Configure the DNS Servers settings for Vnet1.
- B. On DC3, install the DNS Server role.
The suggested answer is correct
- correct - A. Configure the DNS Servers settings for Vnet1. - All resources in Vnet1 will obtain as DNS server IP address of DC3, rather than Azure DNS by default
- correct - B. On DC3, install the DNS Server role. - this will be done as part of domain controller setup, but for this case seems that right answer
- incorrect - C. Create a virtual network link in the corp.fabrikam.com Azure private DNS zone. - corp.fabrikam.com is AD integrated DNS zone
- incorrect - D. Configure a conditional forwarder on DC3. - corp.fabrikam.com is AD integrated DNS zone and replicated by native active directory replication
- incorrect - E. Enable autoregistration in the corp.fabrikam.com Azure private DNS zone. - corp.fabrikam.com is AD integrated DNS zone
- incorrect - F. Create an Azure private DNZ zone named corp.fabrikam.com. - corp.fabrikam.com is AD integrated DNS zone
- incorrect - G. Create an Azure DNZ zone named corp.fabrikam.com. - corp.fabrikam.com is AD integrated DNS zone
stormyR
Highly Voted 1 year, 11 months ago
Selected Answer: AB
D is incorrect, due to the fact, there is no requirement stated in question nor architecture for conditional forwarding. Why question forest or DNS structure when in single DC model. ? Can someone provide links to support that claim? Single domain, don't need a conditional forwarder.
upvoted 8 times
syu31svc
Highly Voted 1 year, 8 months ago
Selected Answer: AB
"Ensure that the resources in Vnet1 can resolve the names of the on-premises servers in the corp.fabrikam.com domain" A and B meet this requirement; the rest are invalid
upvoted 5 times
Leocan
Most Recent 2 years ago
Selected Answer: AB
The network contains a single on-premises Active Directory Domain Services (AD DS) domain named corp.falbrikam.com. Create a domain controller named dc3.corp.fabrikam.com in Vnet1. Single domain, don't need a conditional forwarder.
upvoted 4 times
johosofat
2 years ago
Selected Answer: AD
Setting the dns server settings for VNET1 is going to be to itself - as this is a DC. the right way to setup parent-child domain is to use forestdns zones or domain dns zones- we dont know which is being used. The Domain dns zones is more common for as parent and child relationship- in this situation - their is a delegation form fabricam to corp- and even if this was forestdns zone- there would still be a conditional forwarder back to the root domain- thus A and D - not A and B
https://blogs.msmvps.com/acefekay/2010/10/01/dns-parent-child-dns-delegation-how-to-create-a-dns-delegation/
upvoted 1 times
kijken
2 years ago
B cannot be true because: All domain controllers have the DNS Server role installed and host a copy of the Active Directory integrated DNS zone of corp.fabrikam.com. A and D?
upvoted 1 times
kijken
2 years ago
Correction on the above. Its dc3, that one is not on prem. So A and B are correct
upvoted 2 times