Markup and Web Languages

FieldChange PeopleCode executes immediately after a field value is modified (and passes validation). It is widely used to recalculate other fields on the page, dynamically alter the visual appearance of controls, or perform non-validation processing triggered by the user's action.

FieldEdit PeopleCode is specifically designed to validate values entered into a page field, triggering an error or warning if validation fails. Other events serve different roles: FieldChange handles post-validation logic, FieldDefault sets initial values, and FieldFormula houses reusable user functions.

The question asks which command CANNOT check for response presence. lr_eval_string evaluates a parameter's value but does not search or validate response content - it's a string substitution function. The other three (lr_xml_find, web_image_check, web_reg_find) are content verification functions that actively check for text, images, or XML elements in server responses.

web_reg_save_param extracts dynamic data from HTML pages to save in a parameter. In the XML-based Web Services protocol, lr_xml_get_values queries and extracts values from XML responses into parameters, making it the equivalent function. lr_save_string assigns a string directly, and lr_xml_find searches for a query match rather than saving values.

In Documentum Web Publisher, an Instruction File determines which modifications to an XML template should be applied to existing XML content files. Rules Files control general behavior, Folder Maps handle content placement, and Presentation Files manage styling. The Instruction File specifically guides template-to-content transformations.

A content URI follows the format: content://authority/data_path/id. The authority uniquely identifies the content provider, data_path specifies the type of data, and id (optional) points to a specific record. In the given format, A=authority, B=data_path, and C=id - NOT 'Data_Path' and 'Id Value' as stated. The statement incorrectly capitalizes and presents these as formal names rather than descriptions.

XML stands for eXtensible Markup Language. It was designed to store and transport data in a structured, both human and machine-readable format. The 'extensible' means users can define their own tags and document structures.

IIS 7.0 application pool settings are stored in XML format in the applicationHost.config file located at %windir%\system32\inetsrv\config. This XML-based configuration replaces the IIS 6.0 metabase and provides better human readability and easier programmatic manipulation.

MVC 2.0 includes 10 standard Html Helper methods including ActionLink, BeginForm, TextBox, DropDownList, CheckBox, RadioButton, ListBox, Password, Hidden, and TextArea. This is a specific factual question about the MVC 2.0 framework.

Data Annotations provide a declarative way to validate model properties. Required ensures a field isn't empty, Range validates numeric ranges, and StringLength enforces character limits. These are commonly used in MVC models for automatic server and client-side validation.

The three main types of XML parsers are DOM (Document Object Model) which loads the entire document as a tree, SAX (Simple API for XML) which is event-driven and processes sequentially, and StAX (Streaming API for XML) which uses a pull-based model. Other options are incorrect as they don't match the standard parser types.

SAX is a read-only, event-based parser that cannot modify XML documents. It only provides sequential access for reading. To modify XML, you would need DOM or other tree-based parsers that load and allow manipulation of the document structure.