The subnet 255.255.255.128 is a /25 with 128 hosts, and you're trying to ping 192.168.8.129, which would be out of the scope. So I would think ( A ) would be the correct answer. Let me know your thoughts.
I'm going to correct myself after reviewing this question again. It can't be IP, because if you changed the IP to reach the server, the gateway would then fall out of the subnet, so it has to be mask. Unless, you know, you don't care at all about going to another subnet, but in this context, mask just seems more correct.
Instructor answer: Technically, both answers could be right.
If the subnet mask is the same as the file server, then the easiest solution would be to change the IPv4 address to match the same subnet as the file server. And if the subnet does not match the file server then yes, changing the subnet mask to 255.255.255.0 would also fix the error assuming that is the correct subnet that the file server is on also.
The question is which one is configured wrongly on a user's PC and since the question doesn't specify which subnet the file server is on, it truly could be either one.
255.255.255.128 is a /25 (borrowing 1 bit in the last octet for subnetting, giving you 2 subnets with 128 hosts per subnet ** 126 usable hosts after subtracting the network and broadcast addresses ** )
The PC and the Gateway are in the same subnet, but the file server has an address of 192.168.8.129.
The PC of (192.168.8.105) and the Gateway of (192.168.8.1) are in the (192.168.8.0 - 192.168.8.127) subnet range.
The File Server is in the (192.168.8.128 - 192.168.8.255) subnet range
It really depends on if the pc is intended to be in that subnet, but if you change the ipv4 address to satisfy the range. You'll have to change the router as well. Correct me if I'm wrong though.
In my reasoning, B makes more sense.
If everything else were to be configured with the same settings, that would mean that that is the intended subnet mask, the pc is simply assigned to the wrong subnet, and changing the IP address for one inside the right subnet would resolved the issue... But I might be wrong. Please correct me if that's the case.
Nvm, if it was in the wrong subnet, the default gateway would have to be changed too, and since they're only asking for a single response, it has to be A. My bad lol
The incorrect configuration on the PC is B. IPv4 address.
The PC’s IPv4 address and the file server’s IP address are not in the same subnet, given the subnet mask of 255.255.255.128. The PC’s IPv4 address is 192.168.8.105, which falls into the 192.168.8.0/25 subnet (192.168.8.0 to 192.168.8.127). However, the file server’s IP address is 192.168.8.129, which falls into the 192.168.8.128/25 subnet (192.168.8.128 to 192.168.8.255). Therefore, the PC and the file server are in different subnets, which is why the PC cannot reach the file server. The PC’s IPv4 address needs to be changed to an address within the 192.168.8.128/25 subnet to communicate with the file server.
Everything you said was correct about subnetting, but if you choose "B" and change the IPv4 address, the PC won't be in the same subnet as the Gateway. Answer is "A"
I'm going for A. the file server and the PC are on different subnets if you use the subnet listed below so I guess I would go with the subnet is preventing access.
How do we know that the subnet mask is wrong? Maybe that's how they subnetted their network, with a .128 subnet. There is nothing wrong here aside from the server and the pc being on different subnets. This question should ask "What is preventing the pc from reaching the server?" then the answer would be the IP address or that they are on different subnets.
upvoted 2 times
...
This section is not available anymore. Please use the main Exam Page.N10-008 Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
geocis
Highly Voted 1Â year, 6Â months agoETQ
7Â months agoETQ
6Â months, 3Â weeks agocaloke1
Highly Voted 1Â year, 8Â months agocure2night
Most Recent 1Â year agoMysticMac
1Â year, 3Â months agoPopeyes_Chicken
1Â year, 3Â months agoOneThrive
1Â year, 4Â months agoOneThrive
1Â year, 4Â months ago[Removed]
1Â year, 4Â months agoMysticMac
1Â year, 3Â months ago3Ycam
1Â year, 4Â months agokarokeksa
1Â year, 5Â months agomr_reyes
1Â year, 7Â months ago