Download Microsoft.70-743.Pass4Sure.2018-09-13.46q.tqb
| Vendor: | Microsoft |
| Exam Code: | 70-743 |
| Exam Name: | Upgrading Your Skills to MCSA: Windows Server 2016 |
| Date: | Sep 13, 2018 |
| File Size: | 3 MB |
Demo Questions
Question 1
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?
- On VM1, run docker network connect.
- On Server1, run docker network connect.
- On VM1, run Get-VMNetworkAdapter –VMName VM1 | Set-VMNetworkAdapter –MacAddressSpoofing On.
- On Server1, run Get-VMNetworkAdapter –VMName VM1 | Set-VMNetworkAdapter – MacAddressSpoofing On.
Correct answer: D
Explanation:
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 OnThe command needs to be run on the Hyper-V host. References: https://msdn.microsoft.com/en-us/virtualization/windowscontainers/management/container_networking 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
Question 2
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?
- Edit the configuration.json file.
- Run the Set-ServiceWindows PowerShell cmdlet.
- Edit the daemon.json file.
- Run the New-NetFirewallRule cmdlet
Correct answer: C
Explanation:
Configure Docker with Configuration File The preferred method for configuring the Docker Engine on Windows is using a configuration 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 on port 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 Configure Docker with Configuration File
The preferred method for configuring the Docker Engine on Windows is using a configuration 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 on port 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
Question 3
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 even log, VM1 should be automatically rebooted and moved to another cluster node.
Which tool should you use?
- Resource Monitor
- Failover Cluster Manager
- Server Manager
- Hyper-V Manager
Correct answer: B
Explanation:
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:Right click on the Virtual Machine role on which you want to configure monitoring Select “More Actions” and then the “Configure Monitoring” options You will then see a list of services that can be configured for monitoring using the Failover Cluster Manager. References: https://blogs.msdn.microsoft.com/clustering/2012/04/18/how-to-configure-vm-monitoring-in-windows-server-2012/ 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:
- Right click on the Virtual Machine role on which you want to configure monitoring
- Select “More Actions” and then the “Configure Monitoring” options
- You will then see a list of services that can be configured for monitoring using the Failover Cluster Manager.
References: https://blogs.msdn.microsoft.com/clustering/2012/04/18/how-to-configure-vm-monitoring-in-windows-server-2012/
