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 plan information.

• A
  88% (21)
• C
  8% (2)
• D
  4% (1)

Explanation

Option A is correct because HTML5 best practices dictate using semantic document structure elements (<header>, <main>, <section>, etc.) for page layout, while tables are specifically designed for displaying tabular/comparative data - exactly what comparing four insurance plans requires.

• B is wrong because JavaScript is a scripting language for behavior/interactivity, not page layout. Layout is HTML and CSS's job.
• C is wrong because using tables for layout is an outdated HTML4-era practice explicitly discouraged in HTML5; tables should only be used for tabular data, not structure.
• D is wrong because while CSS is correct for styling/layout, the <pre> element preserves whitespace and renders in a monospace font - it's meant for code or preformatted text, not organized plan comparisons.

Memory tip: Think "right tool for the right job" - structure tags build the skeleton, CSS styles it, JavaScript adds behavior, and tables hold data that belongs in rows and columns. Insurance plan comparisons are classic table data, so A pairs the two correct tools together.

No community discussion yet for this question.