Which representation shows Card Layout data where Case is an array and a separate Contact object?

Which representation shows Card Layout data where Case is an array and a separate Contact object?

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

Answer: (A)

Card Layout data is designed to model lists of related records as arrays and to keep related entities as distinct objects. When Case can have multiple records, you represent it as an array of case objects. The Contact should be its own object so you can access its fields like Name and Phone directly. The shown representation uses Case as an array with one case object and a separate Contact object that includes both Name and Phone, which matches the expected structure. The other options either flatten the contact as a primitive field instead of an object, omit required fields, or use Case as a single object instead of an array, which wouldn't align with the intended data shape.

Card Layout data is designed to model lists of related records as arrays and to keep related entities as distinct objects. When Case can have multiple records, you represent it as an array of case objects. The Contact should be its own object so you can access its fields like Name and Phone directly. The shown representation uses Case as an array with one case object and a separate Contact object that includes both Name and Phone, which matches the expected structure. The other options either flatten the contact as a primitive field instead of an object, omit required fields, or use Case as a single object instead of an array, which wouldn't align with the intended data shape.