exam questions

Exam AZ-800 All Questions

View all questions & answers for the AZ-800 exam

Exam AZ-800 topic 4 question 27 discussion

Actual exam question from Microsoft's AZ-800
Question #: 27
Topic #: 4
[All AZ-800 Questions]

Case Study -

This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.

To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study.

At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section.


To start the case study -
To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click the Question button to return to the question.


Overview -


Company Information -
ADatum Corporation is a manufacturing company that has a main office in Seattle and two branch offices in Los Angeles and Montreal.


Fabrikam Partnership -

ADatum recently partnered with 2 company named Fabrikam, Inc.

Fabrikam is a manufacturing company that has a main office in Boston and a branch office in Orlando.

Both companies intend to collaborate on several joint projects.


Existing Environment -


ADatum AD DS Environment -

The on-premises network of ADatum contains an Active Directory Domain Services (AD DS) forest named adatum.com.

The forest contains two domains named adatum.com and east.adatum.com and the domain controllers shown in the following table.




Fabrikam AD DS Environment -

The on-premises network of Fabrikam contains an AD DS forest named fabrikam.com.

The forest contains two domains named fabrikam.com and south.fabrikam.com.

The fabrikam.com domain contains an organizational unit (OU) named Marketing.


Server Infrastructure -

The adatum.com domain contains the servers shown in the following table.



HyperV1 contains the virtual machines shown in the following table.



All the virtual machines on HyperV1 have only the default management tools installed.

SSPace1 contains the Storage Spaces virtual disks shown in the following table.




Azure Resources -

ADatum has an Azure subscription that contains an Azure AD tenant. Azure AD Connect is configured to sync the adatum.com forest with Azure AD.

The subscription contains the virtual networks shown in the following table.



The subscription contains the Azure Private DNS zones shown in the following table.



The subscription contains the virtual machines shown in the following table.



All the servers are in a workgroup.

The subscription contains a storage account named storage1 that has a file share named share1.


Requirements -


Planned Changes -

ADatum plans to implement the following changes:

• Sync Data1 to share1.
• Configure an Azure runbook named Task1.
• Enable Azure AD users to sign in to Server1.
• Create an Azure DNS Private Resolver that has the following configurations:
• Name: Private1
• Region: West US
• Virtual network: VNet1
• Inbound endpoint: SubnetB
• Enable users in the adatum.com domain to access the resources in the south.fabrikam.com domain.


Technical Requirements -

ADatum identifies the following technical requirements:

• The data on SSPace1 must be available always.
• DC2 must become the schema master if DC1 fails.
• VM3 must be configured to enable per-folder quotas.
• Trusts must allow access to only the required resources.
• The users in the Marketing OU must have access to storage1.
• Azure Automanage must be used on all supported Azure virtual machines.
• A direct SSH session must be used to manage all the supported virtual machines on HyperV1.


You need to implement the planned changes for the Azure DNS Private Resolver.

Which private DNS zones can you use for name resolution?

  • A. Zone1.com only
  • B. Zone2.com only
  • C. Zone1.com and Zone2.com only
  • D. Zone2.com and Zone3.com only
  • E. Zone1.com, Zone2.com, and Zone3.com
Show Suggested Answer Hide Answer
Suggested Answer: A 🗳️

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
jpcapobianco
2 months, 4 weeks ago
there's an errror, subnet B is not on VNET1, subnetB is in VNET2. so if you want to use an azure private dns resolver and implement an inbound endpoint in VNET1 you need to put the endpoint in subnet 1 or subnet2. in that case, if you have your on prem client connected with azure using a vpn or express route, which sends a dns query to the inbound endpoint in the subnet 1 or subnet2 you can use zone1.com
upvoted 1 times
...
Ksk08
7 months, 1 week ago
Correct answer is A
upvoted 1 times
...
Kuikz
1 year, 1 month ago
Correct, answer is A. https://learn.microsoft.com/en-us/azure/dns/private-dns-privatednszone The records contained in a private DNS zone aren't resolvable from the Internet. DNS resolution against a private DNS zone works only from virtual networks that are linked to it.
upvoted 2 times
...
Payday123
1 year, 6 months ago
Selected Answer: A
I guess there is an error: " Virtual network: VNet1 • Inbound endpoint: SubnetB" Inbound endpoint should (must?) be in the same VNet Anyway I think the answer is correct
upvoted 2 times
jpcapobianco
2 months, 4 weeks ago
yes there's an error in the description of the case study. the inbound endpoint must be in the same vnet. so if we assume that we are using private dns resolver with an inbound endpoint in vnet1 we need to put it in subnet 1 or subnet2, not in subnet b.
upvoted 1 times
...
sardonique
9 months, 3 weeks ago
Totally Agree, may be with Vnet Peering this could be somehow possible
upvoted 1 times
...
...
NazerRazer
1 year, 7 months ago
Selected Answer: A
To implement the planned changes for the Azure DNS Private Resolver named "Private1" in region West US with Virtual network VNet1 and inbound endpoint SubnetB, you need to consider the virtual network links of the private DNS zones. Here's the breakdown: VNet1 is connected to Zone1.com, which means you can use Zone1.com for name resolution. VNet2 is connected to Zone2.com, which is not relevant for the specific configuration in VNet1. Zone3.com is not linked to any virtual network. Based on this information, the private DNS zones you can use for name resolution with the Azure DNS Private Resolver "Private1" are: A. Zone1.com only You can use Zone1.com for name resolution within VNet1, which aligns with the planned configuration for the Azure DNS Private Resolver. Zone2.com and Zone3.com are not linked to VNet1, so they are not directly relevant to this specific configuration.
upvoted 2 times
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
Loading ...