Comprehensive Explanation

Adobe Experience Manager supports exposing structured component data through the Sling Model Exporter, which serializes Sling Model properties into JSON representations.

In an AEM Single Page Application (SPA) implementation, the frontend application consumes exported component data to render the user interface.

The .model.json selector provides access to the JSON representation generated by the Sling Model Exporter.

For example, a homepage located at /content/mysite/en/home.html can expose its exported model through:

/content/mysite/en/home.model.json

The developer can inspect this response to determine whether the custom component and its expected property are included in the exported model.

Option A correctly uses the .model.json selector.

Option B is incorrect because /sling.json is not the documented endpoint for the page's Sling Model Exporter representation.

Option C is incorrect because /sling-model.json does not follow the required selector structure.

If the property is absent, the developer should inspect the Sling Model's exported getters, annotations, implementation, component resource type, and the frontend component mapping.

The developer must also confirm that the relevant component is present in the page model and that the exported property is not explicitly excluded from JSON serialization.

This diagnostic method allows the frontend and backend implementations to be evaluated independently.

Official Adobe Reference: Sling Model Exporter — JSON Serialization; AEM SPA Editor and Model Exporter.