Markup and Web Languages

Parameter entities are a feature of DTD (Document Type Definition) syntax and can only appear within DTD files. They are defined with % and used for modular DTD construction. XML files themselves cannot contain parameter entity declarations - only general entities. XSL files use a different syntax altogether.

XML stands for eXtensible Markup Language. It was designed to be both human-readable and machine-readable, allowing users to define their own tags (hence 'extensible'). The other options are made-up acronyms that have never been associated with XML.

The root element is mandatory in every JRXML file as it defines the entire report structure and contains all other sections. All other tags like header, title, and detail are optional child elements within this root.

Compiling a JRXML source file (.jrxml) in JasperReports produces a compiled Jasper file (.jasper), which contains the serialized report template. The JRPrint file is only generated after filling the report with data, making the distractors incorrect.

JRXML files are source XML files containing the report template structure and layout definition. They serve as the blueprint that gets compiled into .jasper files and do not contain actual report data.

The contentType attribute of the page directive defines the MIME type of the HTTP response. While the option contains a minor syntax typo (missing the @ character in the directive prefix), it correctly identifies contentType as the appropriate attribute, whereas type, mimetype, and language are invalid attributes.

Scripting elements can be disabled at the application level using the element in the deployment descriptor (web.xml). They cannot be disabled programmatically via page directive - the isScriptingEnabled attribute does not exist for this purpose.

Under the JSP specification, tag files must end with either .tag or .tagx extensions. Distractors are incorrect because tag files are restricted to /WEB-INF/tags/ or /META-INF/tags/ inside JARs, can indeed be packaged in JAR files, and do not strictly require a TLD for mapping.

Form-based authentication requires a specific HTML form with action j_security_check, username field j_username, and password field j_password. The container requires this exact HTML structure to handle the authentication process. Basic, Digest, and Client Certificate authentication use HTTP headers or SSL certificates - they don't require application-provided HTML forms with specific action attributes.

The JSP page directive syntax is <%@ page attributeName="value" %>. This is the standard JSP 1.2 and later syntax for declaring page directives. Multiple attributes can be included in a single directive, or multiple directives can be used. The statement shown is syntactically correct.

XML Schema (XSD) was developed and is maintained by the World Wide Web Consortium (W3C), the same organization that standardizes XML, HTML, and other web technologies. It is not developed by SWIFT (a financial messaging network), Sun (now Oracle, a tech company), or SAP (enterprise software).

XML Schema serves two key purposes: document generation (creating valid XML instances from the schema definition) and code generation (generating programming language classes or data bindings from the schema). Tools use schemas to produce XML documents or generate code in languages like Java, C#, or Python that conform to the schema structure.

The correct XML declaration is . This is the standard first line in any XML document, including XML Schema documents. Option A is missing the closing question mark, Option B has incorrect syntax with encoding attribute malformed, and Option C uses instead of the processing instruction syntax xml.

The Show-Page method is the standard PEGA function for displaying pages including XML-formatted content. It renders the specified HTML or XML stream to the user interface. The other options (Show-XML, Apply-Parse-XML, Display-XML) are not valid standard PEGA methods for this purpose.

In Pega, HTML properties (now known as Control rules) are used to format and customize how property values are displayed or entered on a user interface, allowing developers to customize presentation and behavior.