I was thinking A and D. Usually I include what the issue is and what I already tried, so support doesn't repeat steps. Maybe C is more about detailed conditions, but to me actions taken (D) feels just as important at first. Not 100 percent on this, anyone else pick D?
HOTSPOT You want to list the IPv4 addresses associated with the host name www.companypro.net. Complete the command by selecting the correct option from each drop-down list.
HOTSPOT An app on a user's computer is having problems downloading dat a. The app uses the following URL to download data: https://www.companypro.net:7100/api You need to use Wireshark to capture packets sent to and received from that URL. Which Wireshark filter options would you use to filter the results? Complete the command by selecting the correct option from each drop-down list. Note: You will receive partial credit for each correct selection.
I don't think you'd want "https" as the protocol here, since Wireshark works at the TCP level for ports like 7100. The trap is assuming protocol = https, but it's actually just tcp with port 7100. Anyone disagree?
I was thinking you'd pick protocol https since the URL uses HTTPS, and port 7100. It makes sense because https is on that port, right? I might be missing something with how Wireshark filters work though. Open to corrections here.
HOTSPOT Computers in a small office are unable to access companypro.net. You run the ipconfig command on one of the computers. The results are shown in the exhibit. You need to determine if you can reach the router. 
Had something like this in a mock, just need to ping the default gateway to check router reachability.
Pretty sure that's it. Sometimes people pick hostname or DNS but for reachability the gateway IP avoids that trap.
That’s the default gateway shown in ipconfig, so it checks if you can talk to the router directly. Not 100% if another IP could work but this is standard for most troubleshooting.
Do you have to use the actual IP (192.168.0.1) from the ipconfig output or could you try pinging just 'router' if it's in DNS? I think pinging the default gateway IP is safer, hostname can fail if DNS is down. Anyone else see a reason to pick a different command?
DRAG DROP Move the MFA factors from the list on the left to their correct examples on the right. You may use each factor once, more than once, or not at all. Note: You will receive partial credit for each correct selection.
Seen this style in Cisco practice too. Should be:
Entering a one-time code: Possession
Holding phone to face: Inference (biometrics)
User name + password: Knowledge
This lines up with what the official guide says.
Entering a one-time code: Possession, Holding phone to face: Inference, Username & password: Knowledge. This matches how MFA splits between something you have, are, or know. Pretty sure this is right but open to other opinions.
DRAG DROP Move each protocol from the list on the left to its correct example on the right.
Pretty straightforward if you know how each protocol functions. DHCP is for dynamic IP assignment, DNS does name resolution, and ping uses ICMP for reachability tests. I think this matches real-world use and what I've seen on other practice sets, but open to comments if anyone spots a catch.
DRAG DROP Examine the connections shown in the following image. Move the cable types on the right to the appropriate connection description on the left. You may use each cable type more than once or not at all. 
Switch S1 to Router R1: Straight-through UTP, R2 to R3 (underground): Fiber Optic, R1 to R2: Crossover UTP, S3 to Server0: Straight-through UTP. That's standard cabling logic for these setups, I think-unless they're hinting at something tricky. Agree?





