Markup and Web Languages

PEGA HTML provides several directives for working with properties: Reference (for reading property values), Lookup ( for searching), With (for context), and Save (for persisting). All of these are valid HTML directives in PEGA for property manipulation.

Auto-generated HTML is available in Section rules and Flow Action rules. HTML Fragment and Harness rules are manually authored. HTML Property is not auto-generated in the same way - it's a specific rule type for property-level HTML.

Embedded pages in PRPC cannot be nested within other embedded pages due to architectural limitations. The system does not support hierarchical embedding of pages, which prevents potential circular references and maintains predictable page structure.

When the Auto-generated HTML checkbox is re-checked, PRPC regenerates the entire HTML section, replacing any custom code that was added while the checkbox was unchecked. This is by design - auto-generation takes precedence over custom modifications to maintain consistency.

Rule-Obj-Validate is the standard Pega rule for validating property values entered through HTML forms. It contains validation logic for individual properties or entire pages. Rule-Form-HTML (A) defines form structure, not validation. Options C and D are methods, not the primary validation mechanism.

Page.User.Identity is correct because it provides the identity information of the authenticated user, including the username. Page.User.IsInRole (B) checks role membership but doesn't return the name, and Page.User.Name (C) is not a valid property. The Identity object contains the Name property that holds the username.

Rule Resolution in Pega does NOT apply to Rule-HTML-Property rules. Rule Resolution is the mechanism that determines which rule to execute when multiple versions exist, but HTML Property rules are resolved by class inheritance and directory structure, not through the Rule Resolution process. Therefore, the statement is False.

Text files in Pega store static content like HTML style sheets, JavaScript code, or other static text that should bypass rule resolution. Fragments, streams, and harnesses are different rule types that serve other purposes - fragments are reusable UI components, streams are for data processing, and harnesses define the overall UI structure.

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.