Free AZ-802 Exam Braindumps
Administering Windows Server Questions 4–8 (page: 4)

Updated On: 29-Oct-2026
View Related Case Study

Your network contains an Active Directory Domains Services (AD DS) forest named adatum.com. Adatum.com contains the users shown in the following table.

You deploy a workgroup server named RODC1 that runs Windows Server. RODC1 contains a user named User4 that is a member of the local Administrators group.
You pre-create a read-only domain controller (RODC) account named RODC1 in east.adatum.com and delegate RODC installation and administration permissions to User3.
You sign-in to RODC1 as User4.
Which credentials can be used to promote RODC1 to a RODC in east.adatum.com?

  1. User3 only
  2. User3 and User1 only
  3. User3 and User2 only
  4. User1, User2, and User3

Answer(s): D

Explanation:

User1 has forest-wide privileges through Enterprise Admins, and User2 has administrative privileges in east.adatum.com through Domain Admins. User3 can complete the staged RODC installation because installation permissions were explicitly delegated to that account. Any of these credentials can therefore attach RODC1 to its pre-created account and complete promotion.


Reference:

https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/deploy/install-active-directory-dom ain-services--level-100-



View Related Case Study

Your network contains an Active Directory Domain Services (AD DS) forest named contoso.com. The forest root domain contains a server named server1.contoso.com.
A two-way forest trust exists between the contoso.com forest and an AD DS forest named fabrikam.com. The fabrikam.com forest contains 10 child domains.
You need to ensure that only the members of a group named fabrikam\Group1 can authenticate to server1.contoso.com.
What should you do first?

  1. Enable SID filtering for the trust.
  2. Enable Selective authentication for the trust.
  3. Change the trust to a one-way external trust.
  4. Add fabrikam\Group1 to the local Users group on server1.contoso.com.

Answer(s): B

Explanation:

Selective authentication lets you explicitly control which users from a trusted forest can authenticate to particular computers. Enable it for access from fabrikam.com to contoso.com, then grant fabrikam\Group1 the Allowed to authenticate permission on Server1’s computer object.



View Related Case Study

HOTSPOT (Drag and Drop is not supported)
Your network contains the Active Directory Domain Services (AD DS) forests shown in the following table.

You need to configure trust relationships as shown in the following table.

For each of the following statements, select Yes if the statement is true. Otherwise, select No.
Note: Each correct selection is worth one point.
Hot Area:

  1. See Explanation section for answer.

Answer(s): A

Explanation:



Box 1: No
No, contoso.com users cannot access resources in adatum.com after both trusts are configured.
Forest Trusts are not transitive across multiple forests: While a forest trust allows transitivity within the participant forests (covering all their child domains), the transitivity stops at the forest boundary. It does not automatically cross over into a third forest.
The Trust Chain Breaks: In the configuration, you have established separate trust relationships linking contoso.com ↔ fabrikam.com and fabrikam.com ↔ adatum.com. Because trust cannot route implicitly through fabrikam.com from one external forest to another, there is no valid authentication path between contoso.com and adatum.com.
Box 2: Yes
Yes, a single two-way forest trust between contoso.com and fabrikam.com satisfies the first required trust relationship.
By definition, a forest trust is inherently transitive across all child domains within the involved forests.
When you establish a two-way forest trust between the root domains (contoso.com and fabrikam.com), the trust relationship automatically extends to all domains inside both forest infrastructures.
This allows users from any domain in the contoso.com forest (contoso.com, europe.contoso.com, and asia.contoso.com) to be authenticated and access authorized resources in any domain in the fabrikam.com forest (fabrikam.com and research.fabrikam.com), and vice versa. No separate domain-level trusts are required to achieve this scope of access.
Box 3: Yes
Yes, a one-way external trust in which research.fabrikam.com trusts adatum.com fully satisfies the second trust relationship requirement.
Direction of Trust vs. Direction of Access: In Active Directory, trust flows in one direction while resource access flows in the exact opposite direction. Setting up a one-way trust where research.fabrikam.com (the resource domain) trusts adatum.com (the user domain) means that authentication requests are passed to adatum.com. As a result, users from adatum.com are allowed to authenticate and access authorized resources inside research.fabrikam.com.
Non-Transitivity of External Trusts: External trusts are explicitly non-transitive. This ensures that trust and access are strictly limited to the two specific domains involved (adatum.com and research.fabrikam.com). Users from adatum.com will not gain unauthorized access to the parent domain (fabrikam.com), keeping the rest of the forest isolated and secure.


Reference:

https://learn.microsoft.com/en-us/entra/identity/domain-services/concepts-forest-trust



View Related Case Study

Your network contains an on-premises Active Directory Domain Services (AD DS) domain named contoso.com.
You have an Azure virtual network named VNet1 that is connected to the on-premises network by using a Site-to-Site (S2S) VPN.
VNet1 contains a domain-joined virtual machine named VM1 that hosts an application named App1.
App1 uses Kerberos authentication and updates objects in AD DS. An Azure Firewall filters communication from VM1 to the domain controllers in contoso.com.
You need to deploy domain controllers to VNet1. The solution must support the requirements of VM1 and provide domain controller redundancy in Azure.
What should you deploy?

  1. two writable domain controller virtual machines across availability zones
  2. two read-only domain controller (RODC) virtual machines across availability sets
  3. two writable domain controller virtual machines, each in a distinct Azure region
  4. two read-only domain controller (RODC) virtual machines, each in a distinct Azure region

Answer(s): A

Explanation:

Two writable domain controller virtual machines across availability zones should be deployed.
Writable Requirement: The application running on the virtual machine updates objects in Active Directory Domain Services (AD DS). Read-only domain controllers (RODCs) cannot process write operations or object updates, which means an RODC would fail to support the application's write requirements.
Redundancy and High Availability: Availability zones provide a high-availability offering that protects your applications and data from datacenter failures, making them superior to availability sets for domain controller redundancy in Azure.


Reference:

https://learn.microsoft.com/en-us/azure/architecture/example-scenario/identity/adds-extend-domain



View Related Case Study

Your network contains an Active Directory Domain Services (AD DS) forest.
The forest contains a root domain named contoso.com and a child domain named branch.contoso.com.
The forest contains the domain controllers shown in the following table.

You discover that cross-domain object references in contoso.com fail to update for objects in branch.contoso.com.
You need to modify the FSMO role placement. The solution must minimize administrative changes.
What should you do?

  1. Transfer the infrastructure master role for contoso.com from DC1 to DC2.
  2. Transfer the PDC emulator role for contoso.com from DC1 to DC2.
  3. Transfer the schema master role from DC1 to DC2.
  4. Transfer the infrastructure master role for branch contoso.com from DC4 to DC3.
  5. Transfer the domain naming master role from DC1 to DC2.

Answer(s): A

Explanation:

Transfer the infrastructure master role in contoso.com from DC1 to DC2.
The Conflict: In a multi-domain forest where not all domain controllers are global catalog servers, the Infrastructure Master (IM) role must not be placed on a Global Catalog (GC) server.
The Symptom: DC1 in contoso.com holds the IM role and is also a GC server. Because a GC holds a partial replica of all objects in the forest, an IM on a GC assumes its data is always up-to-date and fails to detect or replicate cross-domain reference updates from branch.contoso.com.
Action to take with low administrative effort
Move the Role: Transfer only the Infrastructure Master role in the root domain (contoso.com) from DC1 to DC2.
DC2 is ideal because it resides in contoso.com and is not a global catalog server, which directly satisfies Active Directory best practices and resolves the cross-domain update failure.


Reference:

https://vinitpandey.com/2016/09/05/why-global-catalog-server-and-infrastructure-operation-master-shouldnt-be -on-same-server/



Viewing page 4 of 37
Viewing questions 16 - 20 out of 224 questions


Post your Comments and Discuss Microsoft AZ-802 exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!