XML and Web Technologies

XML stands for eXtensible Markup Language, where the 'X' represents 'eXtensible' indicating that users can define their own custom tags and markup structures. This extensibility is what distinguishes XML from fixed markup languages like HTML. Options A, B, and C are made-up expansions.

XML is a meta-language for defining markup languages (option B), meaning it provides rules for creating custom tag sets rather than having fixed tags. XML is indeed a restricted form of SGML (option C), designed to be simpler while retaining SGML's extensibility. Option A is false because XML's tag semantics and tag sets are not fixed.

XML requires all elements to have closing tags (A) and be properly nested (C). Attribute values must be quoted (D). However, XML tags are case-sensitive but not required to be lowercase (B is false) - 'Name' and 'name' are different tags, but uppercase is valid. These rules ensure well-formed XML documents.

XML comments are not part of the document's textual content - they are metadata. XML processors are NOT required to pass comments to applications, and applications typically cannot access them through standard DOM/SAX parsing APIs. This distinguishes comments from actual document data.

The XML version declaration must use the processing instruction syntax with both opening and closing question marks: . Option A incorrectly closes with />, which is only used for empty elements. Option C omits the required question marks. The declaration must appear at the very start of an XML document.

XML parsers preserve whitespace in documents by default unless explicitly configured to trim it. The XML specification treats whitespace as significant content, not something to be automatically truncated. This is different from HTML where whitespace is often normalized.

XML element names must follow strict naming rules. They cannot start with a number (7lastname is invalid) and cannot contain spaces (last name is invalid). Valid names like lastname and last_name follow the rules: starting with a letter or underscore, and containing only letters, digits, hyphens, underscores, or periods.

XML element names must follow specific rules: they cannot start with numbers or punctuation characters (statement A is true), and they cannot start with 'xml' in any case combination as this is reserved (statement B is true). Statement C is false because spaces are not allowed in XML names. Therefore, 'All the above' (D) is incorrect.

XML names cannot contain spaces - this violates XML naming rules. Spaces are not allowed in element or attribute names, though they are valid in content values. Names must start with a letter or underscore, and can contain letters, digits, hyphens, underscores, and periods.

XML attribute values must be quoted. The unquoted format in A is invalid. Both double quotes (B) and single quotes (C, D) are valid. D demonstrates single quotes wrapping a value containing double quotes, which is legal.

XML stands for eXtensible Markup Language. It was designed to be a flexible, extensible markup language unlike HTML which has fixed tags. The name reflects its core design philosophy.

XML stylesheets are referenced using a processing instruction with the format . This is the standard way to link an XSL stylesheet to an XML document for transformation or formatting.

In Windows Communication Foundation (WCF), the SessionMode enumeration defines the support for reliable sessions. Its valid values are Allowed (sessions allowed but not required), NotAllowed (sessions prohibited), and Required (sessions mandatory). Since all listed items are members of this enumeration, 'All' is the correct choice.

ServiceBehaviorAttribute in WCF controls service instance lifetime through the InstanceContextMode property. This property determines whether a single instance serves all clients (Single), each client gets its own instance (PerSession), or each call gets a new instance (PerCall).