Correct Answer: A  🗳️

Explanation: Only visible for Lead2PassExam members. You can sign-up / login (it's free).

Correct Answer:

Explanation:
User1 can be assigned permissions for Share3: Yes. User2 can be assigned permissions for Share1: No. User3 can be assigned permissions for Share1: No.
The external trust here is configured on east.contoso.com, directed one-way outgoing toward adatum.com; an outgoing trust means the domain that owns the trust (east.contoso.com) trusts the named target domain (adatum.com), which allows security principals from the trusted domain, adatum.com, to be granted access to resources in the trusting domain, east.contoso.com - but grants nothing in the reverse direction, and, being an external (not forest) trust, it is non-transitive and does not extend to any other domain such as the contoso.
com root. User1 belongs to adatum.com, the trusted domain, and Share3 sits in east.contoso.com, the trusting domain, so User1 can indeed be assigned permissions for Share3 - that is precisely what an outgoing trust from east.contoso.com to adatum.com enables. User2 belongs to contoso.com, the forest root, which is not a party to this external trust at all (the trust exists only on east.contoso.com, and external trusts don ' t extend automatically to a parent domain), so there is no path allowing User2 into adatum.com ' s Share1. User3 belongs to east.contoso.com itself, but the trust direction only lets adatum.com principals reach into east.
contoso.com, not the reverse; east.contoso.com does not trust adatum.com as a resource domain from its own users ' perspective, so User3 likewise cannot be assigned permissions for Share1.

Correct Answer:

Explanation:
Server1 can successfully ping Server2 by using the name of Server2: No. Server2 can successfully ping Server3 by using the IP address of Server3: No. Running ipconfig /all on Server4 will display an IP address from the 169.254.0.0/16 IPv4 address space: No.
A host decides whether a destination is local by comparing the destination IP against its own subnet mask; if the destination falls outside its own subnet, the host forwards through its default gateway, and if within its own subnet, it uses ARP directly on the local segment. Server2 is physically cabled to Segment1 but has been configured with an IP address (172.16.2.2/24) that places it in the 172.16.2.0/24 network -- a subnet that is physically Segment2. When Server1 (172.16.1.10/24) resolves and pings Server2 ' s name, it gets back
172.16.2.2, which Server1 treats as a remote address (outside its own 172.16.1.0/24) and forwards to its gateway, 172.16.1.1; the router then forwards toward the 172.16.2.0/24 network (physically Segment2), where Server2 is not actually present, so the ping fails. Likewise, when Server2 (believing itself to be on
172.16.2.0/24) tries to reach Server3 (172.16.2.20), it thinks the destination is local and issues an ARP request on the wire it ' s actually attached to (Segment1); ARP requests never cross a router, so the request never reaches Server3 (physically on Segment2), and the ping fails. Server4 was given a static IP address (172.16.1.1); APIPA (169.254.0.0/16) is assigned only to interfaces configured for automatic (DHCP) addressing when no DHCP server responds -- a statically configured interface never receives an APIPA address regardless of any conflict, so ipconfig /all on Server4 will show its configured static address,
172.16.1.1 (which incidentally also collides with Segment1 ' s gateway address, a separate misconfiguration), not an APIPA address.

Correct Answer:

Explanation:
1. roles 2. connections 3. connect to server dc2.adatum.com 4. quit 5. seize schema master Because DC1 has failed and cannot gracefully transfer the schema master role, DC2 must forcibly seize it using ntdsutil.exe. From the initial ntdsutil prompt, the first command is roles, which enters the Role Management submenu where FSMO role transfers and seizures are performed. From within that submenu, the command connections opens the Connections submenu, which is required before you can bind ntdsutil to a specific target domain controller. Inside the Connections submenu, connect to server dc2.adatum.com establishes the bind to DC2, the domain controller that will actually take over the schema master role. The quit command then exits the Connections submenu and returns to the Role Management submenu while keeping the established connection to DC2 active. Finally, seize schema master, executed from the Role Management submenu while bound to DC2, forces DC2 to take ownership of the schema master role even though DC1 (the previous holder) is offline and cannot be contacted to confirm the transfer. The unused command in the list, metadata cleanup, is a separate, later step used to remove the failed DC1 ' s leftover directory metadata once its roles have been reassigned; it is not part of seizing the schema master role itself, so it is correctly left out of this five-step sequence.