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
  76% (52)
• B
  6% (4)
• C
  13% (9)
• D
  4% (3)

Explanation

Option A is correct because Karen uploads the forms to the same web server (making them "local" files), then uses relative links - paths that navigate relative to the current page's location (e.g., ../forms/leave-request.pdf). This avoids the security restriction on the file server entirely while keeping links simple and portable.

Option B is wrong because local absolute links include the full domain/root path (e.g., https://intranet.company.com/forms/doc.pdf). If the server address ever changes, every hardcoded link breaks - relative links are more maintainable for internal content.

Options C and D are wrong because "external" means the file lives on a different server. Since Karen uploaded the forms to the web server, the files are no longer external - calling them external links is a category mismatch regardless of relative or absolute path style.

Memory tip: Think "Local = same Location (the web server), Relative = Route from where you are." Once you move the files to the web server, they're local; and relative links are always preferred for same-server files because they survive server renames and restructuring.

No community discussion yet for this question.