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.
You have an Azure subscription that contains the storage accounts shown in the following table.

In the West US Azure region, you create a storage sync service named SyncA.
You plan to create a sync group named GroupA.
What is the maximum number of cloud endpoints you can use with GroupA?
The Azure File Sync section of the Administering Windows Server Hybrid Core Infrastructure materials states that a sync group defines the topology for synchronization and ''contains one cloud endpoint and one or more server endpoints.'' A cloud endpoint is an Azure file share associated with a Storage Sync Service. The guidance also notes that ''the Storage Sync Service and the storage account (file share) must reside in the same Azure region'' and that ''a single Azure file share can be the cloud endpoint for only one sync group.'' In the scenario, SyncA is in West US, so only file shares in West US (for example, storage1\share1 or storage2\share2) are eligible. However, regardless of how many eligible shares exist, the exam guide is explicit: each sync group supports a maximum of one cloud endpoint. Additional endpoints in the group must be server endpoints on Windows Server volumes. Therefore, the maximum number of cloud endpoints you can use with GroupA is 1, which directly reflects the product's architecture and the documented exam objective requirements.
You have an Active Directory Domain Services (AD DS) domain. The domain contains a member server named Server1 that runs Windows Server.
You need to ensure that you can manage password policies for the domain from Serve1.
Which command should you run first on Server1?
In Windows Server hybrid environments, domain password policy and fine-grained password policy (PSO) administration is performed with the Active Directory administration tools. The AZ-800 study domain states that to ''manage AD DS, including users, groups, OUs, Group Policy, and fine-grained password policies from a member server, you must first install the Remote Server Administration Tools (RSAT) for Active Directory.'' The RSAT AD DS package (RSAT-AD-Tools) installs Active Directory Users and Computers (ADUC), Active Directory Administrative Center (ADAC) (which includes the Password Settings container UI), and Windows PowerShell for Active Directory (the ActiveDirectory module). The guidance further clarifies: ''ADAC exposes Password Settings Objects (PSOs) and lets administrators create, link, and manage fine-grained password and lockout policies without signing in to a domain controller.'' Therefore, on Server1 the first required command is: Install-WindowsFeature RSAT-AD-Tools. Options for only PowerShell, DHCP, or WINS features do not provide ADAC/ADUC and cannot manage PSOs or domain password policies from a member server.
SIMULATION
Task 9
You need to replicate a read-only copy of a DNS zone named contosoxom to SRV2.
Objective:
Create a read-only copy of the DNS zone contoso.com on SRV2.
Step-by-Step Guide: Using a Secondary Zone
Step 1: Log in to SRV2
Log in to SRV2 (where you want to host the secondary zone) using an account with local administrative privileges.
Step 2: Open DNS Manager
Press Windows + R, type dnsmgmt.msc, and press Enter.
Step 3: Create a Secondary Zone
In the DNS Manager, expand the server node for SRV2.
Right-click Forward Lookup Zones and select New Zone.
The New Zone Wizard opens.
Step 4: Configure the Secondary Zone
Zone Type:
Select Secondary zone and click Next.
Zone Name:
Type contoso.com and click Next.
Master DNS Servers:
Enter the IP address of the master DNS server that hosts the primary zone (e.g., SRV1's IP).
Click Next.
Finish:
Review the settings and click Finish.
Step 5: Allow Zone Transfers on the Primary Server
On SRV1 (or the DNS server hosting the primary zone):
Open DNS Manager.
Right-click the contoso.com zone and select Properties.
Go to the Zone Transfers tab.
Check Allow zone transfers.
Specify SRV2's IP address (or allow to any server if needed).
Step 6: Verify Zone Replication
On SRV2, refresh the Forward Lookup Zones in DNS Manager.
The contoso.com zone should now appear as a Secondary zone.
Check the Zone Transfer status to ensure it successfully replicated.
Currently there are no comments in this discussion, be the first to comment!
Jenifer
18 days agoStephaine
25 days agoMiesha
1 month agoKallie
1 month agoMalcolm
2 months agoVirgilio
2 months agoLauna
2 months agoEmmanuel
2 months agoMaile
3 months agoMari
3 months agoMica
3 months agoStefanie
3 months agoBrinda
4 months agoFiliberto
4 months agoZena
4 months agoThaddeus
4 months agoZona
5 months agoAlyce
5 months agoAlishia
5 months agoCyril
5 months agoJustine
6 months agoJohanna
6 months agoBobbie
6 months agoBette
6 months agoJacquelyne
7 months agoSteffanie
7 months agoAvery
7 months agoJesus
7 months agoSherell
7 months agoRikki
8 months agoKasandra
8 months agoBernardine
8 months agoDorothea
10 months agoVicky
10 months agoLang
10 months agoNan
11 months agoStanton
12 months agoLavina
12 months 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
1 year agoCharlene
1 year agoMalcolm
1 year agoWeldon
1 year agoSelma
1 year agoBuddy
1 year agoAlfred
1 year agoJesusita
1 year 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