S90-02A · Question #83
XML can be used to structure data passed between REST services, but REST introduces rules that limit the extent to which XML elements and attributes can be nested. Select the correct answer.
The correct answer is B. False. B is correct because REST is an architectural style, not a data format protocol - it imposes no rules whatsoever on how XML (or any payload format) is structured internally. REST constraints cover things like statelessness, uniform interface, and client-server separation, none…
Question
XML can be used to structure data passed between REST services, but REST introduces rules that limit the extent to which XML elements and attributes can be nested. Select the correct answer.
Options
- ATrue
- BFalse
How the community answered
(19 responses)- A11% (2)
- B89% (17)
Explanation
B is correct because REST is an architectural style, not a data format protocol - it imposes no rules whatsoever on how XML (or any payload format) is structured internally. REST constraints cover things like statelessness, uniform interface, and client-server separation, none of which touch element/attribute nesting depth.
A is wrong because it accepts the false premise that REST regulates payload structure; REST is entirely agnostic about how deeply you nest your XML, leaving that entirely to the application or schema (e.g., XSD) you define.
Memory tip: Think of REST as a "traffic law" (how you drive between destinations) and XML as "how you pack your suitcase" - traffic laws say nothing about suitcase organization. REST governs the exchange pattern, not the content structure.
Topics
Community Discussion
No community discussion yet for this question.