JSON / XML SCHEMA MODELLING — Learn free

Self-check

Questions 1–10 of 10

1. What is JSON / XML Schema Modelling?
Question 1A. The practice of defining structured schemas for semi-structured formats such as JSON and XMLB. The practice of normalising documents into relational tablesC. The practice of storing behaviour with data in objectsD. The practice of partitioning documents by keyE. The practice of replaying document changes as events
2. What is the primary goal of JSON / XML Schema Modelling?
Question 2A. Optimising database storageB. Providing a clear and enforceable contract for APIs, integration workflows and document-based systemsC. Supporting complex analytical joinsD. Eliminating redundancy through normal formsE. Enabling relationship traversal
3. Which rule might a Loan schema define for the Status field?
Question 3A. It must be a numeric value greater than zeroB. It must be a required string identifierC. It must be one of a predefined set of valuesD. It must be a nested objectE. It must be unique across all loans
4. In the loan approval example, why might a bank use both JSON and XML?
Question 4A. Because JSON is required by regulators and XML by mobile appsB. Because XML is faster to parse than JSONC. Because JSON cannot represent nested objectsD. Because JSON serves mobile applications and partner integrations while a regulatory authority requires XML submissionsE. Because XML is needed for caching
5. In the JSON loan representation, which fields are nested objects?
Question 5A. LoanID and StatusB. LoanAmount and InterestRateC. Repayments and BranchD. LoanID and LoanAmountE. Customer and Officer
6. How does the XML representation of the loan relate to the JSON representation?
Question 6A. It preserves the same logical structure using nested tags under a root Loan elementB. It flattens all fields into attributes of a single tagC. It stores the loan as a comma-separated stringD. It omits the Customer and Officer informationE. It uses a different set of field names
7. Which of the following is NOT listed as a strength of JSON and XML schemas?
Question 7A. Human readability and wide platform supportB. Optimisation for complex joins and analytical workloadsC. Self-describing documents and structured validationD. Effectiveness for integration between distributed systemsE. Consistent interpretation of data by all participants
8. What limitation does JSON have on its own regarding data types?
Question 8A. It cannot store numbersB. It cannot represent arraysC. It lacks strict typing unless paired with a formal JSON SchemaD. It requires a root element for every documentE. It cannot be read by humans
9. What trade-off is associated with XML?
Question 9A. It cannot express nestingB. It is not supported by regulatorsC. It lacks any validation mechanismD. It can be verbose and computationally heavier to processE. It cannot be used for legacy integration
10. Why do normalisation forms not apply to JSON / XML Schema Modelling?
Question 10A. Because these formats have no data typesB. Because these formats are always stored in key–value databasesC. Because these formats cannot contain redundancyD. Because these formats are governed by 6NF insteadE. Because these formats are hierarchical and document-centric rather than relational