Rules Inspector is the debugging tool that shows HTML structure and embedded properties in the UI. Clipboard shows data pages, DB Trace is for database performance, and Tracer is for execution flow - none of these show HTML/properties like Rules Inspector does.

Parse XML rules in PRPC are categorized under Integration-Mapping rules, which handle data transformation and mapping between external systems and PRPC. They are not Technical, Property, or any other rule category.

XSS vulnerabilities occur when web applications output unvalidated user input to HTML without proper encoding. This can happen in any language (Java, ASP.Net, Perl, PHP, Python, etc.) - it's a web application vulnerability, not language-specific.

WSDL (Web Services Description Language) describes the service interface, SOAP (Simple Object Access Protocol) is the messaging protocol, and SAML (Security Assertion Markup Language) handles authentication/authorization in web services. Together these form a comprehensive web services stack: messaging (SOAP), description (WSDL), and security (SAML). WADL is for REST services, not SOAP.

HTML comments can reveal sensitive information like server versions, file paths, developer names, or debug instructions that help attackers. Comments are sent to the client and visible in view source. Good practice (A) would be removing them before production deployment.

The security API provides default codecs for both JavaScript and VBScript to protect against cross-site scripting (XSS) attacks. These are the two most common client-side scripting languages that require encoding to prevent injection vulnerabilities.

isSafeHTML validates whether HTML content is safe from XSS attacks by checking for dangerous tags and attributes. encodeForHTML converts special characters like < and > to their HTML entity equivalents (<, >), preventing them from being interpreted as code. Together they provide comprehensive XSS protection.

Security APIs commonly support scripting languages like JavaScript and VBScript for dynamic content execution and security validation. Option C correctly identifies both as standard supported codecs in many security frameworks.

To prevent XSS, TCS SAPI uses both isSafeHTML() to validate input and encodeForHTML() to encode it. Validation alone is insufficient - encoding is necessary to neutralize malicious scripts. The correct option A includes both prevention methods.

The security API includes default scripting codecs for both JavaScript (JavaScriptCodec) and VBScript (VBScriptCodec). These codecs encode user-supplied data specifically for execution within client-side script contexts, preventing cross-site scripting (XSS) attacks by neutralising script-specific characters before output rendering.

The TCS SAPI provides isSafeHTML() and encodeForHTML() methods to prevent Cross Site Scripting (XSS) attacks. The isSafeHTML() method validates HTML content against a context to ensure it's safe, while encodeForHTML() encodes potentially dangerous characters to prevent script injection. Using these methods together provides comprehensive XSS protection.

HTML stands for Hyper Text Markup Language. It's the standard markup language for creating web pages. Option A is incorrect, and B incorrectly states 'Hyperlinks' instead of 'Hyper Text'.

HTML uses

through

tags for headings, with

being the largest and most important. The tag contains metadata, not headings. There is no tag in HTML, and

is the smallest heading.

The
tag is the correct HTML element for line breaks. There is no or tag in HTML. The self-closing form with space before slash is XHTML-compatible practice.

Background color in HTML should be set using CSS within the style attribute. is correct inline CSS syntax. The tag doesn't exist in HTML. The background attribute is deprecated.