Markup and Web Languages

CSS uses curly brackets { } to contain style declarations for selectors. HTML uses angle brackets < > for tags, while parentheses ( ) are used in CSS for functions like calc(), url(), or rgb().

AJAX stands for Asynchronous JavaScript and XML, a technique for creating interactive web applications that update without reloading the page. While option B uses 'java-script' (should be 'JavaScript' as one word), it correctly identifies Asynchronous, the JavaScript component, and XML. Options A and D incorrectly use 'java' instead of JavaScript, and option C uses 'Asymmetric' which is wrong.

XML stands for eXtensible Markup Language. Option B correctly identifies this full form (capitalization varies). The key word is 'extensible' meaning it can be expanded with custom tags, unlike HTML which has fixed tags. Option A incorrectly uses 'Extensive' and C/D use wrong prefixes.

JavaScript is the common name for the language, but the official specification maintained by ECMA International is called ECMAScript. The language is standardized under this name to ensure consistency across different implementations (browsers, Node.js, etc.).

HTML uses the tag to embed JavaScript code. Other tags like <javascript>, <java>, <insert>, or <language> are not valid HTML elements.

HTML stands for Hypertext Markup Language, the standard markup language for creating web pages. The key is that it's 'Markup Language' not 'Temporal', 'Transfer', or 'Transport'. HTTP (Hypertext Transfer Protocol) is different: that's the communication protocol. The double space in option D appears to be a formatting artifact.

AJAX stands for Asynchronous JavaScript and XML. It's a web development technique that allows web applications to send and receive data from a server asynchronously without interfering with the display and behavior of the existing page, making web applications more responsive and dynamic.

XML stands for eXtensible Markup Language, not eXtensive. The name reflects its core design principle - it allows users to define their own custom markup tags, making it 'extensible' rather than being an extensive set of predefined tags.

The correct HTML element for creating a hyperlink is with the 'href' attribute specifying the destination URL. Option D correctly shows example. Options A and C incorrectly use 'url' and 'name' attributes which don't exist for hyperlinks, while B is missing the href attribute entirely.

JavaScript code is placed inside the `` element in HTML. This element can appear in the head or body section. The other options (<js>, <javascript>, <scripting>) are not valid HTML elements and will not execute JavaScript code.

The MAYSCRIPT attribute is an HTML attribute (not a JavaScript feature) used in tags to explicitly grant Java applets permission to access JavaScript objects and functions. This is a security feature - applets cannot access JavaScript unless this attribute is present. CODE, PARAM, and CODEBASE are other applet attributes.

External scripts are referenced via the src attribute in tags and are never displayed on the page. Browsers that don't understand JavaScript simply ignore the entire <script> element. Comment hiding was only needed for inline scripts to prevent code from displaying as text content, not for external script files.

When JavaScript is disabled in the browser, no JavaScript code can execute, including event handlers. This is typically a browser setting that users can configure. The presence of stylesheets, local execution, or other events being processed does not prevent JavaScript execution.

External JavaScript files (.js) contain only JavaScript code without any HTML tags. The script tag with the src attribute is placed in the HTML document to load the external file. If you include script tags in an external .js file, it would cause JavaScript syntax errors.

Adding 'return false' to the onsubmit handler in the FORM tag prevents the default form submission behavior when the user presses Enter. This allows custom JavaScript processing to handle the form data instead. The other options - hidden input, trapping return key, or instructing users - don't address the core issue of form submission behavior.