Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

IBM Exam S1000-007 Topic 2 Question 16 Discussion

Actual exam question for IBM's S1000-007 exam
Question #: 16
Topic #: 2
[All S1000-007 Questions]

An administrator has a test server (my host) that uses local name resolution. The administrator arrives late one morning and finds that their co-worker was asked to make some changes to the IP address of the server.

The co-worker used SMIT from the console, but then when testing from the console, the following command fails:

ping my_host

Why did the ping fail?

Show Suggested Answer Hide Answer
Suggested Answer: B

When attempting to recover a corrupted file system, the administrator should first confirm that the file system is not mounted. If the file system is not mounted, then the administrator should run the fsck command with the -F (force) flag. This will force the fsck command to check the file system for errors and attempt to fix them. Reference: IBM AIX v7 Administrator Specialty Study Guide (page 8-23).


Contribute your Thoughts:

Hyun
18 days ago
D) They didn't reboot the server. Of course, because rebooting fixes everything, even if it's not the actual problem. It's the IT equivalent of 'have you tried turning it off and on again?'
upvoted 0 times
Lenna
13 hours ago
B) They used an incorrect gateway address.
upvoted 0 times
...
Nieves
3 days ago
A) They didn't update /etc/hosts after mktcpip was run.
upvoted 0 times
...
...
Nicolette
20 days ago
I bet the co-worker used 'ping my_host.local' instead of just 'ping my_host'. Classic mistake, but at least they're keeping up with the kids and their dot-local domains.
upvoted 0 times
...
Tiera
25 days ago
B) They used an incorrect gateway address. Really? Who cares about the gateway when it's a local server? Clearly, the /etc/hosts file is the key here.
upvoted 0 times
Renea
2 days ago
A) They didn't update /etc/hosts after mktcpip was run.
upvoted 0 times
...
...
Cecil
1 months ago
D) They didn't reboot the server. Come on, that's just too easy. Everyone knows you need to reboot after making network changes, especially on a test server.
upvoted 0 times
Daron
10 days ago
C) They didn't update the DNS entry.
upvoted 0 times
...
Gaston
23 days ago
B) They used an incorrect gateway address.
upvoted 0 times
...
Armando
25 days ago
A) They didn't update /etc/hosts after mktcpip was run.
upvoted 0 times
...
...
Keneth
1 months ago
A) They didn't update /etc/hosts after mktcpip was run. That's the obvious answer here. Local name resolution requires the /etc/hosts file to be updated, and if they didn't do that, the ping would fail.
upvoted 0 times
Virgie
4 days ago
C) Maybe the co-worker forgot to update the /etc/hosts file after making the changes. That's a common mistake.
upvoted 0 times
...
Mirta
18 days ago
B) Yes, you're right. Updating the /etc/hosts file is crucial for local name resolution to work properly.
upvoted 0 times
...
Alona
1 months ago
A) They didn't update /etc/hosts after mktcpip was run. That's the obvious answer here. Local name resolution requires the /etc/hosts file to be updated, and if they didn't do that, the ping would fail.
upvoted 0 times
...
...
Edward
2 months ago
I think they should also check if the DNS entry was updated. That could be the reason for the ping failure.
upvoted 0 times
...
Isaiah
2 months ago
I agree with Willow. Updating /etc/hosts is important for local name resolution.
upvoted 0 times
...
Willow
2 months ago
I think the ping failed because they didn't update /etc/hosts after mktcpip was run.
upvoted 0 times
...

Save Cancel