1D0-720 · Question #106
Which statement accurately reflects a feature of HTML5?
The correct answer is B. HTML5 allows for native drag-and-drop capabilities. HTML5 introduced native drag-and-drop support through the Drag and Drop API, allowing elements to be dragged and dropped without any JavaScript libraries or plugins - making B correct. Option A is wrong because JavaScript remains essential to HTML5; the two work together, not…
Question
Which statement accurately reflects a feature of HTML5?
Options
- AHTML5 eliminates the need for JavaScript.
- BHTML5 allows for native drag-and-drop capabilities.
- CHTML5 does not support multimedia elements like audio and video.
- DHTML5 is only compatible with the latest versions of web browsers.
How the community answered
(64 responses)- A2% (1)
- B91% (58)
- C5% (3)
- D3% (2)
Explanation
HTML5 introduced native drag-and-drop support through the Drag and Drop API, allowing elements to be dragged and dropped without any JavaScript libraries or plugins - making B correct. Option A is wrong because JavaScript remains essential to HTML5; the two work together, not as replacements. Option C is the opposite of reality - native <audio> and <video> elements are among HTML5's most celebrated features, eliminating the old Flash dependency. Option D is incorrect because HTML5 was designed with broad backward compatibility in mind and is supported across all modern and many older browsers.
Memory tip: Think of HTML5 as the "native powers" update - it gave browsers native drag-and-drop, native audio/video, and native canvas drawing. If a choice says HTML5 removes a capability or requires something external, it's almost certainly wrong.
Topics
Community Discussion
8
Carlos M.Oct 29, 2025B is correct. HTML5 added native drag-and-drop support via the Drag and Drop API, along with audio/video elements, canvas, local storage, and a ton of other built-in features, all without needing plugins or extra libraries.
Fatima Z.Nov 5, 2025A tries to trip you up because HTML5 DID absorb some jobs JavaScript used to handle solo, but "eliminates the need" is exam poison, so lock in B and picture HTML5 as a bouncer letting drag-and-drop walk right through the velvet rope, no JavaScript bodyguard required for that one trick.
Hiroshi T.Nov 6, 2025Worth noting that HTML5 drag-and-drop still requires JavaScript event handlers for dragstart, dragover, and drop per the WHATWG HTML Living Standard, so the velvet rope analogy holds for the attribute itself but the bouncer still calls JavaScript to actually move anyone inside.
Brenda K.Nov 2, 2025I almost picked A because people always hype how HTML5 "does everything now," but the moment I remembered you still write JavaScript for interactivity, that one died fast. B locks in clean, drag-and-drop is literally baked into the spec with the draggable attribute and the dragstart and drop events, no library required, and that is a tested fact on this exam.
Carlos M.Nov 3, 2025Solid call, just remember you still need to preventDefault() on the dragover event or the drop will never fire, that trips people up on the actual implementation questions.
Hiroshi T.Oct 16, 2025Saw this exact concept show up on mine and I almost overthought it, but the W3C HTML5 spec is clear that drag-and-drop is a native API introduced in HTML5, so B is the only defensible choice. The other options are flat-out contradicted by the spec, since HTML5 actually added audio and video elements, never removed JavaScript, and was designed with broad browser compatibility in mind.
Samuel O.Nov 14, 2025C has to be the right call here, because I remember reading that HTML5 was designed as a structural markup language and the multimedia stuff always depended on third-party plugins like Flash or Silverlight, not native browser support. Twenty years in AV systems integration and that was always the story, you needed a plugin layer to handle any real media playback in a browser.
Carlos M.Nov 14, 2025Samuel, HTML5 actually introduced native audio and video support directly in browsers through the audio and video elements, no plugins required, which was a major reason Flash eventually died off. That native multimedia support is exactly what makes B the correct answer here.