Which sample is a valid Expected Output JSON for sending current weather data to an OmniScriptCard Layout?

Which sample is a valid Expected Output JSON for sending current weather data to an OmniScriptCard Layout?

• A. { "Current:TempF": 53.1, "Current:CityState": "Baltimore, MD", "Current:TempF": 14.6 }
• B. { "Current": { "TempF": 53.1, "CityState": "Baltimore, MD", "TempC": 14.6 } }
• C. { "Current": { "TempF": 53.1, "CityState": "Baltimore, MD", "TempF": 15.3 } }
• D. <root> ... </root>

Answer: (B)

The concept being tested is using a nested JSON structure that the OmniScriptCard Layout expects, with a top-level object named Current that contains the weather fields. The card reads values as Current.TempF, Current.CityState, and Current.TempC, so grouping these under a Current object ensures the data is accessible in the layout. The valid example places TempF, CityState, and TempC inside a single Current object, which matches the data model the card binds to and avoids any ambiguity from flattened keys or duplicate entries. Other options fail because they don’t provide the required nested Current object. Flattened keys like Current:TempF don’t map cleanly to the layout’s bindings, duplicate keys (such as two TempF fields) introduce ambiguity, and an XML-like <root> structure isn’t JSON at all.

The concept being tested is using a nested JSON structure that the OmniScriptCard Layout expects, with a top-level object named Current that contains the weather fields. The card reads values as Current.TempF, Current.CityState, and Current.TempC, so grouping these under a Current object ensures the data is accessible in the layout.

The valid example places TempF, CityState, and TempC inside a single Current object, which matches the data model the card binds to and avoids any ambiguity from flattened keys or duplicate entries.

Other options fail because they don’t provide the required nested Current object. Flattened keys like Current:TempF don’t map cleanly to the layout’s bindings, duplicate keys (such as two TempF fields) introduce ambiguity, and an XML-like structure isn’t JSON at all.