220-1102 Practice Question: A technician is deploying a new virtual machine…

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Bridge the VM directly to the physical network adapter

  Why it's wrong here

  Bridging directly connects the virtual machine to the physical network adapter, making it appear as a separate, distinct host on the corporate network. The VM would obtain an IP address from the corporate DHCP server, granting it full access to all network resources and exposing it to all network traffic. This configuration completely defeats any isolation requirements, as the VM becomes indistinguishable from a physical machine on the network.

• ✓

  Use a virtual switch set to host-only mode and configure port forwarding for HTTPS

  Why this is correct

  Host-only mode creates a private virtual network between the VM and the host machine, completely isolating the VM from the external corporate network. This ensures the VM cannot be directly accessed or discovered by other devices on the corporate network. Configuring port forwarding specifically for HTTPS (port 443) on the host allows only this designated traffic to pass from the host to the isolated VM, precisely meeting the requirement for secure, controlled inbound access while maintaining maximum isolation.

• ✗

  Attach the VM to a NAT network without any port forwarding

  Why it's wrong here

  Attaching the VM to a NAT network allows it to share the host's IP address for outbound connections, enabling internet access while providing a degree of isolation from the corporate network. However, without explicit port forwarding rules configured on the host, external devices on the corporate network cannot initiate inbound connections to the VM. This means the required HTTPS traffic from the corporate network would be blocked, preventing the VM from receiving necessary services.

• ✗

  Assign the VM an IP from the corporate DHCP scope

  Why it's wrong here

  Assigning the VM an IP address directly from the corporate DHCP scope effectively places the virtual machine directly onto the corporate network as if it were a physical device. This configuration bypasses all forms of network isolation, making the VM fully discoverable and accessible to all other machines on the corporate network. Such direct exposure violates the fundamental security requirement for isolating the virtual machine from the broader corporate environment.

Go deeper

Related to this question