Markup and Web Languages

In the XML declaration , the encoding attribute is optional (defaults to UTF-8). The version attribute is mandatory, but encoding can be omitted.

HTML5 provides both audio and video elements for media playback. The element handles sound files while the element handles video content with optional captions and tracks. Therefore the statement that HTML5 has only audio elements is false.

Although modern web browsers have exceptionally high compatibility with HTML5, none implement 100% of all HTML5 specifications, experimental features, and peripheral APIs. Therefore, the statement remains true, as full, comprehensive compliance across every detail has not been fully achieved by any single browser.

HTML5 standardizes support for three audio formats in the `` element: MP3, Wav, and Ogg. While AAC is supported by many modern browsers, MP3 and Wav are the officially recognized standard options listed here, whereas AIFF is not standard. Thus, MP3 and Wav are correct.

HTML5 officially supports three video formats for the `` element: MP4 (MPEG 4 with H.264 video and AAC audio), WebM (with VP8/VP9 video and Vorbis/Opus audio), and Ogg (with Theora video and Vorbis audio). The claim that HTML5 lacks video elements is false.

HTML5 became an official W3C Recommendation in October 2014. The statement is false because HTML5 is indeed a W3C recommendation - it completed the standardization process and is now a formal web standard.

The `` element is only a container for graphics and has no drawing capabilities of its own. It requires JavaScript to access the rendering context and perform drawing operations like rendering shapes, paths, text, or images. Therefore, the statement is true.

web_reg_find is the LoadRunner function used for text validation - it checks whether a specific text string exists in the server response. web_reg_save_param is for correlation, lr_get_attrib_string gets parameter attributes, lr_check_text doesn't exist in LoadRunner.

In Adobe Flex, the [Bindable] metadata tag is used to mark a variable or property as eligible for data binding. When a property is marked as bindable, it can be used as the source or destination in data binding expressions, and changes to the property will automatically update bound destinations.

A document view template is typically designed and associated with a specific object type or document type. It defines how that particular type of document should be displayed, what fields are visible, how they're arranged, and what actions are available. While you might be able to apply the same template to similar object types, the fundamental association is one-to-one between template and object type for proper rendering and data binding.

PHP server-side scripts are enclosed in delimiters, which tell the PHP processor to interpret the code between them as PHP. Option A incorrectly uses and ?>, option C shows HTML script tags used for JavaScript, and option D shows invalid syntax.

The PS Framework requires exactly one ps.xml configuration file per application to define page flows, task mappings, and controller associations. Having multiple configuration files would create ambiguity and conflicts in the framework's routing logic.

The PS Framework allows multiple pages to be defined under a single task in ps.xml, supporting complex workflows and navigation scenarios. Restricting to one page would severely limit the framework's ability to handle multi-page user interactions within a task.

JSP translation is the process where the web container converts JSP pages into Java Servlet source code. This happens automatically - the first time a JSP is accessed, it's translated to a Servlet, compiled to bytecode, and then executed. Subsequent requests use the compiled Servlet directly. Options A and B describe parsing or static content generation, not the translation process.