Which JSON sample demonstrates a card layout with Case data as an array and a separate Contact object?

Which JSON sample demonstrates a card layout with Case data as an array and a separate Contact object?

• A. { "Case":[ { "Number":"3244", "Subject":"Cannot tack our order" }, { "Number":"3244", "Subject":"Cannot tack our order" } ], "Contact":{"Name":"Lanne Tomlin", "Phone":"324242324" } }
• B. { "Case":[ { "Number":"3244", "Subject":"Cannot tack our order" }, { "Number":"3244", "Subject":"Cannot tack our order" } ], "ContactName":"Lanne Tomlin" }
• C. { "Case":[ { "Number":"3244", "Subject":"Cannot tack our order" } ], "ContactName":"Lanne Tomlin" }
• D. { "Case":[ { "Number":"3244" } ], "Contacts": { "Name":"Lanne" } }

Answer: (A)

Modeling repeated items as an array of objects while keeping related, distinct data in its own object is what this sample shows. The Case field is an array, with each element representing a card-like item that has its own properties (Number and Subject). This lets you display multiple cases in a list or grid. Separately, the Contact data is its own object under the Contact key, containing Name and Phone. This separation mirrors a card layout where case items are grouped together, and contact details live in their own block. The first option fits this structure precisely: a Case array with two items, each having Number and Subject, and a separate Contact object with Name and Phone. The other options fail the criteria in small but important ways: one uses a simple string for the contact name instead of a nested object; another uses a different key name or omits Subject or misnames the container, so the data structure doesn’t reflect a separate Contact object or a proper Case array.

Modeling repeated items as an array of objects while keeping related, distinct data in its own object is what this sample shows. The Case field is an array, with each element representing a card-like item that has its own properties (Number and Subject). This lets you display multiple cases in a list or grid. Separately, the Contact data is its own object under the Contact key, containing Name and Phone. This separation mirrors a card layout where case items are grouped together, and contact details live in their own block.

The first option fits this structure precisely: a Case array with two items, each having Number and Subject, and a separate Contact object with Name and Phone. The other options fail the criteria in small but important ways: one uses a simple string for the contact name instead of a nested object; another uses a different key name or omits Subject or misnames the container, so the data structure doesn’t reflect a separate Contact object or a proper Case array.