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 two servers that run Windows Server 2016. You have a server named Server1 that runs Windows Server 2016.
Server1 has the Hyper-V server role and Docker installed.
You pull the Microsoft/iis Docker image to Server1.
You need to view the available space in the Microsoft/iis Docker image.
Solution: You run the following commands. docker run --name container1 --isolation hyperv --d Microsoft/iis docker exec --i container1 cmd.exe dir Does this meet the goal?
You have a failover cluster named Cluster1.
A virtual machine named VM1 is a highly available virtual machine that runs on Cluster1. A custom application named App1 runs on VM1.
You need to configure monitoring on VM1. If App1 adds an error entry to the Application event log, VM1 should be automatically rebooted and moved to another cluster node.
Which tool should you use?
Do you have a large number of virtualized workloads in your cluster? Have you been looking for a solution that allows you to detect if any of the virtualized workloads in your cluster are behaving abnormally? Would you like the cluster service to take recovery actions when these workloads are in an unhealthy state? In Windows Server 2012/2016, there is a great new feature, in Failover Clustering called ''VM Monitoring'', which does exactly that -- it allows you monitor the health state of applications that are running within a virtual machine and then reports that to the host level so that it can take recovery actions.
VM Monitoring can be easily configured using the Failover Cluster Manager through the following steps:
References:
You have a server named Server1 that runs Windows Server 2016. You install the Docker daemon on Server1.
You need to configure the Docker daemon to accept connections only on TCP port 64500.
What should you do?
Configure Docker with Configuration File
The preferred method for configuring the Docker Engine on Windows is using aconfiguration file. The configuration file can be found at 'c:\ProgramData\docker\config\daemon.json'.
Only the desired configuration changes need to be added to the configuration file. For example, this sample configures the Docker Engine to accept incoming connections onport 64500. All other configuration options will use default values.
{
"hosts": ["tcp://0.0.0.0:64500"]
}
References:
https://msdn.microsoft.com/en-us/virtualization/windowscontainers/docker/configure_docker_daemon
You have a Hyper-V host named Server1 that runs Windows Server 2016.
Server1 has a virtual machine named VM1. VM1 is configured to run the Docker daemon.
On VM1, you have a container network that uses transparent mode.
You need to ensure that containers that run on VM1 can obtain IP addresses from DHCP.
What should you do?
If the container host is virtualized, and you wish to use DHCP for IP assignment, you must enable MACAddressSpoofing.
PS C:\> Get-VMNetworkAdapter -VMName ContainerHostVM | Set-VMNetworkAdapter -MacAddressSpoofing On
The command needs to be run on the Hyper-V host.
References:
https://msdn.microsoft.com/en-us/virtualization/windowscontainers/management/container_networking
You have a server named Server1 that runs Windows Server 2016.
You plan to deploy Internet Information Services (IIS) in a Windows container.
You need to prepare Server1 for the planned deployment.
Which three actions should you perform? Each correct answer presents part of the solution.
Step 1 (A): The container feature needs to be enabled before working with Windows containers. To do so run the following command in an elevated PowerShell session.
Enable-WindowsOptionalFeature -Online -FeatureName containers --All
Step 2 (B): Docker is required in order to work with Windows containers.
Note: First install the OneGet PowerShell module.
Install-Module -Name DockerMsftProvider -Repository PSGallery -Force
Next you use OneGet to install the latest version of Docker.
Install-Package -Name docker -ProviderName DockerMsftProvider
Step 3 (C): Install Base Container Images
Windows containers are deployed from templates or images. Before a container can be deployed, a container base OS image needs to be downloaded. The following commands will download the Nano Server base image.
Pull the Nano Server base image.
docker pull microsoft/nanoserver
Currently there are no comments in this discussion, be the first to comment!