\/\/\/\/\/\/\/\/\/\/
Answer: No.
The first element allow any number of X or any number of Y *but* if there is a single X there cannot by any Y and viceversa.
The second element allows any number of X and Y in *any* combination.
a. used only in DTDs;
b. used both in DTDs and document instances;
c. always parsed entities;
d. always unparsed entities;
\/\/\/\/\/\/\/\/\/\/
Answers: a, c
a. QName;
b. normalizedString;
c. string;
d. token;
e. language;
f. anyType;
\/\/\/\/\/\/\/\/\/\/
Answer: f.
a. minOccurs;
b. unbounded;
c. minOccurs + 1;
d. this is an error; if minOccurs is specified then maxOccurs must be specified also;
\/\/\/\/\/\/\/\/\/\/
Answer: a.
In this case maxOccurs attribute will have the same value as minOccurs attribute.
\/\/\/\/\/\/\/\/\/\/
Answer: yes.
\/\/\/\/\/\/\/\/\/\/
Answer: no.
\/\/\/\/\/\/\/\/\/\/
Answer: no.
a. prohibited;
b. optional;
c. required;
\/\/\/\/\/\/\/\/\/\/
Answer: b.
A default atribute *must* be optional if it is specified thru XML Schema.
a. an element;
b. an attribute;
c. none;
\/\/\/\/\/\/\/\/\/\/
Answer: a,b.
Both an element and an attribute can be declared as a direct child of a schema element and in this case they can be referenced by another elements using the "ref" attribute.
\/\/\/\/\/\/\/\/\/\/
No. All the attributes must be defined after the sequence:
\/\/\/\/\/\/\/\/\/\/
No. The "ANY" element is more restrictive: it only allows elements that were previously declared in the DTD while the "anyType" element allows even elements that were not previously declared.
\/\/\/\/\/\/\/\/\/\/
Answer: yes.
\/\/\/\/\/\/\/\/\/\/
No. It is illegal to specify the type of an element twice:
a. type="xsd:string";
b. complexType;
The element would be valid like this:
a. attribute nodes;
b. PI nodes;
c. document element nodes;
d. text nodes;
e. root nodes;
\/\/\/\/\/\/\/\/\/\/
Answer: c,e
A root node is a virtual node of the whole document. I said "virtual" because the root node is never actually written in an xml file but its presence is always assumed. The root node is the parent of the document element node.
PIs, attributes and text never have child nodes.
Consider the following xml fragment:
The element BlockA has a child text node that has the value "Some text". Text nodes are nameless and they cannot have child nodes.
\/\/\/\/\/\/\/\/\/\/
No. Always entity references are expanded before XPath expressions are computed.
a. child;
b. parent;
c. self;
d. preceding;
\/\/\/\/\/\/\/\/\/\/
Answer: a.
\/\/\/\/\/\/\/\/\/\/
Answer: true.
\/\/\/\/\/\/\/\/\/\/
No. Even if the parent node of the text element is the enclosing element, the reverse is not true.
a. comma (",");
b. whitespace (" ");
c. dash ("-");
d. underscore ("_");
\/\/\/\/\/\/\/\/\/\/
Answer: b.
Only whitespace can be used as a separator.
\/\/\/\/\/\/\/\/\/\/
Answer: no.
I wish you success in your certification effort.
If you wish to add something feel free to use the forums.