Free Preparation Discussions
MENU
Microsoft AZ-800 Exam Questions
Free Microsoft AZ-800 Exam Actual Questions
Note: Premium Questions for AZ-800 were last updated On Jun. 02, 2026 (see below)
You have a server named Server1 that hosts Windows containers. You plan to deploy an application that will have multiple containers. Each container will be You need to create a Docker network that supports the deployment of the application. Which type of network should you create?
In the context of Windows Server Hybrid Core Infrastructure and container networking, choosing the correct network driver is critical for application deployment. According to official documentation, the l2bridge (Layer 2 Bridge) network mode is used when container hosts are connected to the same IP subnet. In this configuration, each container is assigned an IP address from the same prefix as the container host. All container traffic is bridged to the physical network through an external Hyper-V Virtual Switch. Because the containers share the same underlying network infrastructure as the host, they are visible to the rest of the physical network without requiring Network Address Translation (NAT).
The documentation specifies that for multi-node clusters or deployments where containers must be directly reachable on the physical network via their own IP addresses, l2bridge is the standard choice. This differs from NAT, which uses a private internal IP range and translates traffic through the host's IP, and Transparent mode, which is often used for individual hosts where the container is directly connected to the physical network but can have complexities in virtualized environments. l2tunnel is specifically used for Microsoft Cloud Stack (Azure Stack HCI) and SDN scenarios, typically involving encapsulation, which is not the standard requirement for a general multi-container application deployment on a single server unless specified. Therefore, for a high-performance, direct-access network that bridges traffic at Layer 2, l2bridge is the verified architectural choice for Windows containers.
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.
You are planning the deployment of DNS to a new network.
You have three internal DNS servers as shown in the following table.
The contoso.local zone contains zone delegations for east.conloso.local and west.contoso.local. All the DNS servers use root hints.
You need to ensure that all the DNS servers can resolve the names of all the internal namespaces and internet hosts.
Solution: On Server2 and Server3, you configure a conditional forwarder for contoso.local.
Does this meet the goal?
The DNS chapters in Administering Windows Server Hybrid Core Infrastructure describe conditional forwarders as a way to direct queries for specific namespaces to authoritative DNS servers. The text notes: ''A conditional forwarder forwards queries for a designated DNS domain to specified DNS servers,'' which is used to ''integrate split or private namespaces across sites or forests.'' In this design, Server1 hosts contoso.local and delegates east and west to Server2 and Server3. By configuring Server2 and Server3 with a conditional forwarder for contoso.local pointing to Server1, any query for contoso.local (including child names like east.contoso.local or west.contoso.local when not answered locally) is sent to Server1. Server1, being authoritative for the parent, uses the existing delegations to return referrals/answers from the proper child zones. For Internet hosts, all three servers already use root hints, which the course material confirms remains valid alongside conditional forwarding. The documentation also stresses that ''authoritative data is answered locally first; forwarding applies only to names the server is not authoritative for,'' so Server2 continues to answer east locally while leveraging Server1 to reach parent and sibling zones. This configuration ensures that all servers can resolve all internal namespaces and Internet hosts.
Your network contains an Active Directory domain named contoso.com. The domain contains the computers shown in the following table.
On Server3, you create a Group Policy Object (GPO) named GP01 and link GPOI to contoso.com. GP01 includes a shortcut preference named Shortcut1 that has item-level targeting configured as shown in the following exhibit.
To which computer will Shortcut1 be applied?
Group Policy Preferences support Item-Level Targeting (ILT), allowing a preference item to apply only when the target computer meets specified criteria, such as operating system family and version. The AZ-800 study content notes that when a GPO is linked at the domain level, scope is all domain computers, but ILT on a specific preference item restricts that item to clients that match the ILT filter; non-matching clients still process the GPO but skip the filtered item. In the Targeting Editor shown, the condition is ''the operating system is Windows Server 2022 Family.'' Among the listed machines: Computer1 (Windows 11), Server1 (Windows Server 2016), Server2 (Windows Server 2019), and Server3 (Windows Server 2022). Only Server3 satisfies the ILT. Therefore, the shortcut preference Shortcut1 is applied only to Server3.
SIMULATION
Task 5
You have an application that is copied to a folder named C:\app on SRV1. C:\app also contains also a Dockerfile for the app.
On SRV1. you need to create a container image for the application by using the Dockerfile. The container image mutt be named app1.
Explore
To create a container image named app1 for your application using the Dockerfile in the C:\app directory on SRV1, follow these steps:
Step 1: Open PowerShell or Command Prompt First, open PowerShell or Command Prompt on SRV1.
Step 2: Navigate to the Application Directory Change to the directory where your application and Dockerfile are located:
cd C:\app
Step 3: Build the Container Image Use the docker build command to create the container image. The -t flag tags the image with the name app1:
docker build -t app1 .
The period . at the end of the command tells Docker to use the Dockerfile in the current directory.
Step 4: Verify the Image Creation After the build process completes, verify that the image app1 has been created successfully by listing all images:
docker images
You should see app1 in the list of images.
Step 5: Use the Image Now, you can use the image app1 to run containers or push it to a container registry if needed.
By following these steps, you'll have created a Docker container image named app1 using the Dockerfile located in C:\app on SRV11. Ensure that Docker is installed on SRV1 and that you have the necessary permissions to execute these commands.
SIMULATION
Task 2
You need to ensure that you can manage SRV1 remotely by using PowerShell
To manage SRV1 remotely using PowerShell, you'll need to set up PowerShell Remoting. Here's a step-by-step guide:
Step 1: Enable PowerShell Remoting on SRV1 On SRV1, run the following command to enable PowerShell Remoting:
Enable-PSRemoting -Force
This command configures the computer to receive PowerShell remote commands that are sent by using the WS-Management technology.
Step 2: Configure the TrustedHosts List (If Needed) If you're managing SRV1 from a computer that is not part of the same domain, you'll need to add the managing computer's name to the TrustedHosts list on SRV1:
Set-Item wsman:\localhost\Client\TrustedHosts -Value 'ManagingComputerName' -Concatenate -Force
Replace ''ManagingComputerName'' with the name of your managing computer.
Step 3: Start a Remote Session From your managing computer, start a remote session with SRV1 using the Enter-PSSession cmdlet:
Enter-PSSession -ComputerName SRV1 -Credential (Get-Credential)
This command prompts you for credentials and then starts a remote session with SRV1.
Step 4: Run Remote Commands Once the remote session is established, you can run any PowerShell command as if you were directly on SRV1. For example:
Get-Service
This command gets the status of services on SRV1.
Step 5: Exit the Remote Session When you're finished, exit the remote session:
Exit-PSSession
Note: Ensure that both the managing computer and SRV1 are properly configured to communicate over the network, and that any firewalls allow for the necessary ports (default is 5985 for HTTP and 5986 for HTTPS) to be open for WS-Management traffic12.
By following these steps, you should be able to manage SRV1 remotely using PowerShell. Make sure you have the appropriate administrative privileges to perform these actions.
- Select Question Types you want
- Set your Desired Pass Percentage
- Allocate Time (Hours : Minutes)
- Create Multiple Practice tests with Limited Questions
- Customer Support
Tiffany Garcia
5 days agoAnthony Lee
10 days agoFrank Young
1 month agoMelissa Ramirez
1 month agoJoseph Torres
1 month agoMelissa Roberts
1 month agoMichael Cook
1 month agoJeffrey Hernandez
1 month agoHeather Sanchez
30 days agoJenifer
2 months agoStephaine
2 months agoMiesha
3 months agoKallie
3 months agoMalcolm
3 months agoVirgilio
3 months agoLauna
4 months agoEmmanuel
4 months agoMaile
4 months agoMari
4 months agoMica
5 months agoStefanie
5 months agoBrinda
5 months agoFiliberto
5 months agoZena
6 months agoThaddeus
6 months agoZona
6 months agoAlyce
6 months agoAlishia
7 months agoCyril
7 months agoJustine
7 months agoJohanna
7 months agoBobbie
8 months agoBette
8 months agoJacquelyne
8 months agoSteffanie
8 months agoAvery
9 months agoJesus
9 months agoSherell
9 months agoRikki
9 months agoKasandra
9 months agoBernardine
9 months agoDorothea
11 months agoVicky
11 months agoLang
12 months agoNan
1 year agoStanton
1 year agoLavina
1 year agoIzetta
1 year agoShawna
1 year agoVallie
1 year agoAngelyn
1 year agoShaun
1 year agoBillye
1 year agoSharan
1 year agoAlberto
1 year agoTeddy
1 year agoBrande
1 year agoEvangelina
1 year agoJerry
1 year agoTitus
1 year agoJulene
2 years agoCharlene
2 years agoMalcolm
2 years agoWeldon
2 years agoSelma
2 years agoBuddy
2 years agoAlfred
2 years agoJesusita
2 years agoAnnabelle
2 years agoNell
2 years agoCammy
2 years agoZona
2 years agoPaulina
2 years agoBrock
2 years agoNohemi
2 years agoGlory
2 years agoRoselle
2 years agoStevie
2 years agoClaudia
2 years agoAlecia
2 years agoCecilia
2 years agoXochitl
2 years agoKenny
2 years ago