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 have a server named Server1 that runs Windows Server 2022 and has the DHCP Server role. Server1 contains a single DHCP scope named Scope1.
You deploy five printers to the network.
You need to ensure that the printers are always assigned the same IP address.
Solution: You configure the DHCP scope options for Scope1.
Does this meet the requirement?
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.
SIMULATION
Task 4
You need to run a container that uses the mcrmicrosoft.com/windows/servercofe/iis image on SRV1. Port 80 on the container must be published to port 5001 on SRV1 and the container must run in the background
To run a container on SRV1 using the mcrmicrosoft.com/windows/servercofe/iis image, publish port 80 on the container to port 5001 on SRV1, and ensure it runs in the background, you can follow these steps:
Step 1: Pull the IIS Image First, pull the correct IIS image from the Microsoft Container Registry:
docker pull mcr.microsoft.com/windows/servercore/iis
Step 2: Run the Container Next, run the container with the required port mapping and ensure it runs in the background using the -d flag:
docker run -d -p 5001:80 --name iis_container mcr.microsoft.com/windows/servercore/iis
This command will start a container named iis_container using the IIS image, map port 80 inside the container to port 5001 on SRV1, and run the container in detached mode.
Step 3: Verify the Container is Running To verify that the container is running and the port is published, use the following command:
docker ps
This will list all running containers and show the port mappings.
Step 4: Access the IIS Server You can now access the IIS server running in the container by navigating to http://<SRV1_IP>:5001 in a web browser, where <SRV1_IP> is the IP address of SRV1.
By following these steps, you should be able to run the IIS container on SRV1 with the specified port mapping and have it running in the background. Please replace mcrmicrosoft.com/windows/servercofe/iis with the correct image name mcr.microsoft.com/windows/servercore/iis as shown in the commands above.
SIMULATION
Task 10
You need to configure Hyper-V to ensure that running virtual machines can be moved between SRV1 and SRV2 without downtime.
You do NOT need to move any virtual machines at this time.
One possible solution to configure Hyper-V to ensure that running virtual machines can be moved between SRV1 and SRV2 without downtime is to use Live Migration. Live Migration is a feature of Hyper-V that allows you to move a running virtual machine from one host to another without any noticeable interruption of service. To set up Live Migration between SRV1 and SRV2, you need to perform the following steps:
On both SRV1 and SRV2, openHyper-V Managerfrom theAdministrative Toolsmenu or by typingvirtmgmt.mscin the Run box.
In the left pane, right-click on the name of the server and selectHyper-V Settings.
In theHyper-V Settingsdialog box, selectLive Migrationsin the navigation pane.
Check the boxEnable incoming and outgoing live migrations.
UnderAdvanced Features, you can optionally enable theUse any available network for live migrationoption, which allows Hyper-V to use any available network adapter on the source and destination servers for live migration. If you do not enable this option, you need to specify one or more network adapters to be used for live migration by clicking on theAddbutton and selecting the network adapter from the list. You can also change the order of preference by using theMove UpandMove Downbuttons.
ClickOKto apply the settings.
Now, you have configured Hyper-V to enable live migration between SRV1 and SRV2. You can use Hyper-V Manager or Windows PowerShell to initiate a live migration of a running virtual machine from one server to another.
SIMULATION
Task 12
You need to create a Group Policy Object (GPO) named GPO1 that only applies to a group named MemberServers.
To create a GPO named GPO1 that only applies to a group named MemberServers, you can follow these steps:
On a domain controller or a computer that has the Remote Server Administration Tools (RSAT) installed, openGroup Policy Managementfrom theAdministrative Toolsmenu or by typinggpmc.mscin the Run box.
In the left pane, expand your domain and right-click onGroup Policy Objects. SelectNewto create a new GPO.
In theNew GPOdialog box, enterGPO1as theNameof the new GPO and clickOK. You can also optionally select a source GPO to copy the settings from.
Close theGroup Policy Management Editorand return to theGroup Policy Managementconsole. Right-click on the new GPO and selectScope. Here, you can specify the scope of management for the GPO, such as the links, security filtering, and WMI filtering.
Under theSecurity Filteringsection, click onAuthenticated Usersand then click onRemove. This will remove the default permission granted to all authenticated users and computers to apply the GPO.
Click onAddand then type the name of the group that you want to apply the GPO to, such asMemberServers. ClickOKto add the group to the security filter. You can also click onAdvancedto browse the list of groups available in the domain.
To link the GPO to an organizational unit (OU) or a domain, right-click on the OU or the domain in the left pane and selectLink an Existing GPO. Select the GPO that you created, such asGPO1, and clickOK. You can also change the order of preference by using theMove UpandMove Downbuttons.
Shawna
2 hours agoVallie
14 days agoAngelyn
23 days agoShaun
30 days agoBillye
1 months agoSharan
2 months agoAlberto
2 months agoTeddy
2 months agoBrande
2 months agoEvangelina
3 months agoJerry
3 months agoTitus
3 months agoJulene
3 months agoCharlene
3 months agoMalcolm
4 months agoWeldon
4 months agoSelma
4 months agoBuddy
4 months agoAlfred
4 months agoJesusita
5 months agoAnnabelle
5 months agoNell
5 months agoCammy
5 months agoZona
5 months agoPaulina
6 months agoBrock
6 months agoNohemi
6 months agoGlory
6 months agoRoselle
6 months agoStevie
7 months agoClaudia
7 months agoAlecia
8 months agoCecilia
9 months agoXochitl
9 months agoKenny
10 months ago