When a developer registers an external React component with Sitecore XM Cloud, it becomes integrated into the authoring experience. This registration makes the component appear in the Components library, allowing content authors to select and use it on pages (C). If the component is defined with editable parameters (props), the authoring interface provides fields for a content author to input values, enabling customization (B). The Components builder and the Pages editor are designed to be What You See Is What You Get (WYSIWYG) tools, so they render a visual preview of the component, showing authors how it will appear on the live site (D).

A. The registered component is scoped to only one environment.

Component definitions are part of the codebase and serialized content items, which are designed to be deployed across all environments (e.g., from development to production) as part of a standard workflow.

---

1. Sitecore XM Cloud Documentation, "The Components library": This document states, "The Components library contains all the components you can use to build your pages." This directly supports option C, as a registered component is added to this library for use.

2. Sitecore XM Cloud Documentation, "Walkthrough: Creating a new JSS component": In the section "Make the component's props editable in the XM Cloud Pages editor," it details the creation of a Parameters Template. This template defines fields that content authors can edit, directly supporting option B.

3. Sitecore XM Cloud Documentation, "The Pages editor": This page describes the visual, drag-and-drop interface for building pages. The screenshots and descriptions inherently demonstrate that components are rendered and previewed within the editor, supporting option D.

4. Sitecore XM Cloud Documentation, "XM Cloud environments": This document explains the multi-environment setup. It clarifies that code and content items are promoted between environments, stating, "Each environment has its own set of Sitecore instances... but they are all based on the same code base." This refutes the idea that a component registration would be scoped to a single environment (A).