XK0-005 · Question #269
A Linux administrator recently reprovisioned a new corporate web server to replace a legacy one. To minimize the impact on the company's users, the administrator modified the network and DNS…
The correct answer is B. Remove the entry for the web server from the known_hosts file on the local machine. The impact on the company's users has ALREADY been minimised by matching the network and DNS settings of the new server to those of the old one, and that is all that is required for a seamless transition into its role as the new corporate web server. I.E. the staff are all…
Question
A Linux administrator recently reprovisioned a new corporate web server to replace a legacy one. To minimize the impact on the company's users, the administrator modified the network and DNS settings of the new server to be the same as the legacy server. When attempting to log in to the new server remotely over SSH, the following error message is displayed:
WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! Which of the following should the administrator do to resolve the issue?
Options
- ARestart the network services on both the remote server and the local machine.
- BRemove the entry for the web server from the known_hosts file on the local machine.
- CUpdate the /etc/hosts file on the remote server and local machine.
- DAdd the administrator's public key to the authorized_keys on the remote server.
How the community answered
(53 responses)- A4% (2)
- B79% (42)
- C11% (6)
- D6% (3)
Explanation
The impact on the company's users has ALREADY been minimised by matching the network and DNS settings of the new server to those of the old one, and that is all that is required for a seamless transition into its role as the new corporate web server. I.E. the staff are all accessing this server over HTTP or HTTPS, not SSH and therefore won't see this error - it's only the admin SSHing into it who sees it.
Topics
Community Discussion
No community discussion yet for this question.