AZ-800 Online Practice Questions and Answers

Correct Answer: AB

Reference: https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/learn-more/use-local-resources-on-hyper-v-virtual-machine-with-vmconnect

Correct Answer: D

Reference: https://docs.microsoft.com/en-us/windows-server/storage/fsrm/fsrm-overview

Correct Answer:

Box 1: Turn on BranchCache

To create a Group Policy Object and configure BranchCache modes (see steps 5 and 7 below).

On a computer upon which the Active Directory Domain Services server role is installed, in Server Manager, click Tools, and then click Group Policy Management. The Group Policy Management console opens.

In the Group Policy Management console, expand the following path: Forest: example.com, Domains, example.com, Group Policy Objects, where example.com is the name of the domain where the BranchCache client computer accounts that

you want to configure are located.

Right-click Group Policy Objects, and then click New. The New GPO dialog box opens. In Name, type a name for the new Group Policy Object (GPO). For example, if you want to name the object BranchCache Client Computers, type

BranchCache Client Computers. Click OK.

In the Group Policy Management console, ensure that Group Policy Objects is selected, and in the details pane right-click the GPO that you just created. For example, if you named your GPO BranchCache Client Computers, right-click

BranchCache Client Computers. Click Edit. The Group Policy Management Editor console opens.

In the Group Policy Management Editor console, expand the following path: Computer Configuration, Policies, Administrative Templates: Policy definitions (ADMX files) retrieved from the local computer, Network, BranchCache.

Click BranchCache, and then in the details pane, double-click Turn on BranchCache. The policy setting dialog box opens.

In the Turn on BranchCache dialog box, click Enabled, and then click OK.

To enable BranchCache distributed cache mode, in the details pane, double-click Set BranchCache Distributed Cache mode. The policy setting dialog box opens.

In the Set BranchCache Distributed Cache mode dialog box, click Enabled, and then click OK.

If you have one or more branch offices where you are deploying BranchCache in hosted cache mode, and you have deployed hosted cache servers in those offices, double-click Enable Automatic Hosted Cache Discovery by Service

Connection Point. The policy setting dialog box opens.

In the Enable Automatic Hosted Cache Discovery by Service Connection Point dialog box, click Enabled, and then click OK.

Box 2: Set BranchCache Distributed Cache mode

BranchCache modes

BranchCache has two modes of operation: distributed cache mode and hosted cache mode.

When you deploy BranchCache in distributed cache mode, the content cache at a branch office is distributed among client computers.

When you deploy BranchCache in hosted cache mode, the content cache at a branch office is hosted on one or more server computers, which are called hosted cache servers.

Reference: https://learn.microsoft.com/en-us/windows-server/networking/branchcache/deploy/use-group-policy-to-configure-domain-member-client-computers

Correct Answer:

Reference: https://learn.microsoft.com/en-us/windows-server/storage/data-deduplication/overview

Correct Answer:

1.

User1 can use self-service password reset (SSPR) to reset his password.

-> [YES]. User1 can use self-service password reset (SSPR) because they are in the synchronized organizational unit (OU1), and "Enable Password writeback" is configured.

2.

If User1 connects to Microsoft Exchange Online, an on-premises domain controller provides authentication.

-> [Yes]. When User1 connects to Microsoft Exchange Online or any other Azure AD-integrated service, their authentication request is passed directly to an on-premises AD domain controller for validation because Pass-through Authentication (PTA) is used.

3.

You can add User2 to Group1 as a member.

-> [No]. User2 is in OU2, which is not selected for synchronization according to the provided configuration details. Since User2's OU is not included in the synchronization scope, you cannot directly add User2 to Group1 from the on-premises AD.

Correct Answer:

Box 1: Azure AD Connect Implement password hash synchronization with Azure AD Connect sync

When you install Azure AD Connect by using the Express Settings option, password hash synchronization is automatically enabled.

Box 2: Azure Portal Express installation of Azure AD Connect

1.

Sign in as Local Administrator on the server you want to install Azure AD Connect on. The server you sign in on will be the sync server.

2.

Go to AzureADConnect.msi and double-click to open the installation file.

3.

In Welcome, select the checkbox to agree to the licensing terms, and then select Continue.

4.

In Express settings, select Use express settings

Reference: https://learn.microsoft.com/en-us/azure/active-directory/hybrid/connect/how-to-connect-password-hash-synchronization https://learn.microsoft.com/en-us/azure/active-directory/hybrid/connect/how-to-connect-install-express

Correct Answer:

User1:

This is a domain-level object.

Since DC1 and DC2 are in the same domain (adatum.com), User1 will be replicated to DC2.

DC3 is in a different domain (west.adatum.com), but it is in the same forest. Since it's a Global Catalog (GC) server, it will receive a partial replica of the adatum.com domain, including the newly created User1.

DC4 is in a completely different forest (contoso.com) and there is no direct trust relationship between contoso.com and west.adatum.com, so User1 will not be replicated to DC4.

Attribute1:

This is a schema-level object. The schema is a forest-wide object.

The schema master for the adatum.com forest is DC1, so any changes to the schema (such as adding a new attribute) are initially made on DC1.

These changes are then replicated to all other domain controllers in the adatum.com forest, which includes DC2 and DC3.

However, DC4 is in a different forest, so it will not receive the schema changes made in the adatum.com forest.

In summary, User1 and Attribute1 will be replicated to DC2 and DC3

Correct Answer:

Box 1: Hyper-V isolation or process isolation Isolation Modes Windows Server host OS compatibility

Box 2: Hyper-V isolation only

Note: Windows containers offer two distinct modes of runtime isolation: process and Hyper-V isolation. Containers running under both isolation modes are created, managed, and function identically. They also produce and consume the same container images. The difference between the isolation modes is to what degree of isolation is created between the container, the host operating system, and all of the other containers running on that host.

Reference: https://learn.microsoft.com/en-us/virtualization/windowscontainers/deploy-containers/version-compatibility

Correct Answer:

Reference: https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/user-guide/nested-virtualization

Correct Answer: