Skylar has been asked by the HR Department to create a Web page for the company's intra net site that compares the company's four different medical insurance plans. To accomplish this effectively in…

Question

Options

• Ause document structure tags to lay out the page and use a table to organize the medical insurance
• Buse JavaScript to lay out the page and use a table within the page to organize the medical insurance
• Cuse tables to lay out the page and use the <pre> tag inside the table to organize the medical insurance
• Duse CSS to lay out the page and use the <pre> element to organize the medical insurance

• A
  93% (25)
• B
  4% (1)
• C
  4% (1)

Explanation

Option A is correct because HTML5 best practice separates concerns: semantic document structure tags (like <header>, <main>, <section>) define the page layout, while <table> is the appropriate element for tabular/comparative data - exactly what comparing four insurance plans requires.

Option B is wrong because JavaScript is a scripting language used for behavior and interactivity, not page layout; using it to "lay out" a page misuses its purpose entirely. Option C reverses HTML5 best practice - tables are for data, not layout, and <pre> (preformatted text) is for preserving whitespace in code or plain text, not for organizing structured comparison data. Option D is half-right (CSS is indeed used for styling/layout), but <pre> is still the wrong tool for organizing insurance plan data; a <table> is semantically correct for side-by-side comparisons.

Memory tip: Think "right tool for the right job" - structure tags = page skeleton, tables = comparison grids. If the data has rows and columns (like a plan comparison), reach for <table>, not <pre>.

No community discussion yet for this question.