Markup and Web Languages

DTD defines XML structure and constraints. Attributes specify element properties. Constraints define valid values and relationships. Element types declare allowed elements and their hierarchy. DTD doesn't contain actual data instances or specific data type definitions.

AJAX stands for Asynchronous JavaScript and XML. It describes a technique for making asynchronous HTTP requests from the browser to exchange data and update parts of a web page without requiring a full page reload. Despite the name containing XML, modern AJAX often uses JSON instead.

AJAX is based on JavaScript for client-side logic and XML for data exchange (traditionally). The core technology is the XMLHttpRequest object, which JavaScript uses to make asynchronous HTTP requests. While modern AJAX often uses JSON instead of XML, the name reflects the original design.

AJAX has several disadvantages: search engines cannot easily index dynamically loaded content (SEO issue), browser back/forward buttons don't work with AJAX page updates by default, and historically there were browser compatibility concerns. Since all three listed options describe genuine disadvantages, 'All the above' is correct.

In JSP tag libraries, the prefix attribute serves as a namespace identifier. When you declare a tag library with <%@ taglib uri="..." prefix="..." %>, the prefix defines the short name you'll use to reference tags from that library in the JSP page. You then use this prefix before tag names, like . The prefix itself doesn't define the tag name or point to the TLD location - it's simply used as a namespace qualifier before tag names to distinguish them from tags in other libraries or standard JSP elements.

In a JSP tag library descriptor (TLD), the required elements within a tag element are 'name' and 'tag-class'. The 'name' element defines the unique tag name within the library, and 'tag-class' specifies the fully-qualified Java class that implements the tag handler. Other elements like 'description', 'validator', and 'display-name' are optional and provide additional metadata or validation logic, but are not required for the tag to function.

The include directive <%@ include file="..." %> performs static inclusion at translation time, merging the content as if it were part of the original JSP. Option A is incorrect because any extension works (jspf is just convention). Option B describes the include action , not directive. Option C is wrong because directive content shares the same scope and CAN access local variables.

Text File rules in Pega are specifically designed to store static content like HTML style sheets (CSS files) and JavaScript code. Unlike most Pega rules, Text File rules are not subject to rule resolution - the system does not search through multiple RuleSets or versions to find them. Fragments, Streams, and Harness rules are all subject to standard rule resolution mechanisms.

Web.Config is an XML-based configuration file used in ASP.NET applications to store application settings, connection strings, and framework configurations. It follows standard XML syntax and structure.

Web.Config is an XML-based configuration file used in ASP.NET applications. It contains application settings, connection strings, and framework configurations in a structured XML format.

In HTML, heading tags range from H1 to H6, where H1 is the largest and most important heading, and H6 is the smallest. Therefore, H1 makes the largest headline.

In HTML, most of the visible content of a web page should be placed between the tags. The section contains metadata and title, sets the page title, and is not a standard HTML container.