Katie developed her corporation's intra net site using proprietary HTML language extensions based on the company's current browser. The company has recently updated its systems to include the use of…

The correct answer is C. Update the site using a single language standard consistently, such as HTML5 or XHTML. Option C is correct because using a recognized, vendor-neutral standard like HTML5 or XHTML ensures that content renders predictably across all compliant browsers - any browser that follows the standard will interpret the markup the same way, eliminating the rendering…

HTML5 Coding

Question

Katie developed her corporation's intra net site using proprietary HTML language extensions based on the company's current browser. The company has recently updated its systems to include the use of a new browser. Now the intra net site that Katie developed no longer renders its content consistently. What should Katie do to ensure that this site's content renders consistently regardless of the browser used?

Options

ARevise the site to include workarounds and hacks for the new browser.
BRevise the site's markup language in only those areas that are not rendering properly.
CUpdate the site using a single language standard consistently, such as HTML5 or XHTML.
DUpdate the site using the proprietary language extensions required by the new browser's rendering engine.

How the community answered

(31 responses)

A
13% (4)
B
3% (1)
C
81% (25)
D
3% (1)

Explanation

Option C is correct because using a recognized, vendor-neutral standard like HTML5 or XHTML ensures that content renders predictably across all compliant browsers - any browser that follows the standard will interpret the markup the same way, eliminating the rendering inconsistency Katie is experiencing.

Option A is wrong because browser-specific hacks and workarounds are fragile, hard to maintain, and will break again when the next browser update arrives - they treat symptoms, not the cause.
Option B is wrong because patching only the broken areas still leaves proprietary extensions throughout the site, meaning future browser changes will cause the same problem again.
Option D is wrong for the same core reason as Option A: swapping one proprietary dependency for another just recreates the original problem with a different vendor.

Memory tip: Think "standards = stability." Proprietary extensions tie you to one vendor's rendering engine; open standards travel with any browser. Whenever a question involves cross-browser consistency, the answer will always point toward an established, universal standard rather than a vendor-specific fix.

Topics

#Cross-browser compatibility#Web standards compliance#HTML5/XHTML standards#Proprietary markup

Community Discussion

Mei-Ling H.Mar 19, 2026

C is correct. Proprietary extensions tie you to one specific browser, so switching browsers breaks rendering, the fix is to rewrite using a real open standard like HTML5 or XHTML that all browsers are designed to support, not to chase each browser with its own proprietary hacks (A or D) or patch only the broken parts while leaving proprietary code everywhere else (B).

Renata O.Feb 27, 2026

Honestly, my first instinct was B, because patching only the broken sections feels like the faster fix and keeps you from touching code that already works. But that thinking falls apart the moment you remember WHY the problem happened in the first place. Katie built the site on proprietary extensions tied to one specific browser, and that is exactly the kind of shortcut that creates this mess. Swapping one set of proprietary extensions for another, which is what D suggests, just restarts the same cycle, and A is really just a band-aid on top of a bad foundation. C is the right call because a recognized standard like HTML5 gives you a stable, browser-agnostic contract that the rendering engine is expected to honor, so your content behaves consistently whether the company switches browsers again next year or not.

Imani T.Mar 13, 2026

C is the right call here, proprietary extensions are what got Katie into this mess in the first place, so swapping one vendor lock-in for another (option D) just kicks the can down the road. Did you know that using a proper standard like HTML5 also helps when the company adds mobile devices or accessibility tools down the line, not just when browsers change?

Full 1D0-61B Practice