— Exhibit —
— Exhibit —
The virtual machine Fileserver01 shown in the exhibit can not ping anything on the Internet.
Why is Fileserver01 unable to connect to the Internet?
A.
Fileserver01 does not have a reachable IP address.
B.
Fileserver01 is not on the Production network.
C.
The virtual nic for Fileserver01 has a speed or duplex mismatch.
D.
The vSwitch1 virtual switch does not have an attached vmnic adapter.
Explanation:
A
0
1
How can you see that?? I think it’s B since it’s not on the production network.
0
0
A sounds like the best option. Fileserver01 is not “attached” to the network meaning it does not have a reachable IP address. It doesn’t matter if it is not connected to the “Production” network since we don’t know anything about the “production” network. It is connected to the “VM Network” group but is not attached.
1
0
Guys, a correct answer cannot be given simply because it’s a wrong screenshot !! It is exactly the same WRONG “Exhibit” shown in this Exam Dump in Question 248.
Just another example of how one has to be cautious when using these dumps…
One obvious evidence is that the same uplink vmnic (here “vmnic0”) cannot be connected to multiple v-switches. It’s like connecting a single physical NIC in your PC to several switches, – just pure nonsense ! 😉
0
0
Agree with andp75. You can’t have 2 seperate vswitches connected to the SAME vmnic as is shown in the faulty graphic.
0
0
A would be the correct answer if it was the correct screenshot. 172 on vSwitch0 network isnt meant to reach the outside world
0
0
To Casper: non-public 172.16.x.x subnet in this example is actually used for the Management vmk0 network and has nothing to do with the VM Network although theoretically both can be on the same subnet but it would go against all best practices and is neither the case in real life scenarios nor the conclusion that can be made from this graphics.
However, believe it or not, despite the obvious ERROR in the screenshot re: use of the same uplink vmnic to connect two different switches, I did get this question on the exam !! I’m going to write about this and a few other blunders to VMware Education…
0
0
Did this dump work for you in the exam?? did you pass it??
0
0
Using the options at hand, despite the screenshot.. we know fileserver01 cannot ping.
A – True, would definitely cause problem (blueprint material)
B – True, but not enough info given to tell definitively
C – Unknown, could be screenshot but doubtful (is this even on the blueprint?)
D – False, it does have attached vnmic (albeit same as vS0 = impossible).
Based on question, A is best answer and most relevant to problem described.
0
0
Fuck you all, especially these VMware bastards!
0
0
A : Fileserver01 does not have a reachable IP address.
0
0
The VM was POWERED OFF on the picture – had this on my exam today. This here is a wrong screenshot
0
0