Karen is the Webmaster for her company. Management would like to make the company's intra net site more effective by providing links to internal HR forms for all employees to access. These forms are…

Question

Options

• AUpload the forms to the Web server and create local relative links to the files.
• BUpload the forms to the Web server and create local absolute links to the files.
• CUpload the forms to the Web server and create external relative links to the files.
• DUpload the forms to the Web server and create external absolute links to the files.

• A
  79% (38)
• B
  2% (1)
• C
  6% (3)
• D
  13% (6)

Explanation

Option A is correct because Karen must first move the HR forms onto the Web server (since linking directly to the file server is blocked for security reasons), and then use relative links - paths like ../forms/form1.pdf that are relative to the current page's location - which is the standard practice for linking to files hosted on the same server.

Why the distractors are wrong:

• B (local absolute links): Absolute links hardcode the full URL (e.g., https://intranet.company.com/forms/form1.pdf), which works but is unnecessarily brittle - if the domain or directory changes, every link breaks. Relative links are the correct choice for same-server files.
• C (external relative links): "External relative" is a contradiction in terms - external links point to a different server and must use a full absolute URL; you cannot use a relative path to reach an external resource.
• D (external absolute links): This describes linking to the file server directly (e.g., file://fileserver/forms/...), which is exactly what the security policy prohibits.

Memory tip: Think "same server = relative, different server = absolute." Since uploading the forms makes them local to the Web server, relative links are the natural, portable choice - and the word "local" in option A is your signal that the files now live on the same server.

No community discussion yet for this question.