Sitecore Sitecore XM Cloud Developer Practice Exams
Last updated on Oct 21,2026- Exam Code: Sitecore XM Cloud Developer
- Exam Name: Sitecore XM Cloud Developer Certification Exam
- Certification Provider: Sitecore
- Latest update: Oct 21,2026
Question #21
A multinational clothing company wants to create a structured online presence for its various brands and countries. They want to ensure that the different brands and countries have their own dedicated content within the same Sitecore instance.
Which approach should they take to achieve this using XM Cloud’s content architecture?
- A . Use separate instances of XM Cloud for each brand and country to maintain separation.
- B . Create a single site collection and site for all brands and countries and also manage their resources manually.
- C . Create individual site collections for each brand and a site for each country.
- D . Create a separate site for each brand and use a language per country.
Correct Answer: C
C
Explanation:
XM Cloud’s content architecture supports the creation of individual site collections for each brand, with separate sites for each country. This approach allows a multinational company to maintain a structured online presence, ensuring dedicated content for different brands and countries within the same Sitecore instance.
Reference: The Sitecore XM Cloud documentation outlines the ability to create headless site collections and sites, supporting multiple brands for a single company or multiple languages or
locations for a single brand1. This is part of the SXA content architecture, which includes site collections and sites, allowing for multiple sites on a single instance of Sitecore1.
C
Explanation:
XM Cloud’s content architecture supports the creation of individual site collections for each brand, with separate sites for each country. This approach allows a multinational company to maintain a structured online presence, ensuring dedicated content for different brands and countries within the same Sitecore instance.
Reference: The Sitecore XM Cloud documentation outlines the ability to create headless site collections and sites, supporting multiple brands for a single company or multiple languages or
locations for a single brand1. This is part of the SXA content architecture, which includes site collections and sites, allowing for multiple sites on a single instance of Sitecore1.
Question #22
When utilizing the GraphQL API to create a new item in Sitecore XM Cloud, which mutation is correct?
- A . updateItem
- B . createOrReplaceItem
- C . createItem
- D . newItem
Correct Answer: C
Question #23
A developer wants to create a new component to display content from a data source.
Of the options listed below, what are the optimal steps to do this?
- A . Create or reuse a SXA Module, insert a new rendering, and use the JSS CLI to scaffold out a new component.
- B . Create the new component in the Next.js application and import it to XM Cloud.
- C . Create or reuse a SXA Module, clone an existing component that uses a data source item, and create the React component based on the original cloned component.
- D . Create or reuse a SXA Module, clone an existing component that uses a context item, and create the React component based on the original cloned component.
Correct Answer: C
C
Explanation:
According to the Sitecore XM Cloud Documentation for Developers1, a data source item is a content item that provides the content for a component. A data source item can have fields, such as text, image, or link, that can be edited by the content author in the XM Cloud Pages editor. To create a new component that displays content from a data source item, you need to follow these steps2: Create or reuse a SXA Module, which is a folder that contains the renderings, data templates, and media items for your components.
Insert a new rendering item in the SXA Module, which defines the metadata and parameters for your component. You can also clone an existing rendering item that uses a data source item and modify it as needed.
Use the JSS CLI to scaffold out a new React component in your Next.js application, which defines the layout, style, and logic for your component. You can also copy and paste an existing React component that uses a data source item and modify it as needed.
Register the React component in the Components builder and add it to the Components library.
In the XM Cloud Pages editor, drag and drop the component to the page and select or create a data source item for the component. You can also edit the data source item’s fields in the Properties
panel.
2: Create a component that uses a data source item | Sitecore Documentation 1: XM Cloud Documentation for Developers – Sitecore
C
Explanation:
According to the Sitecore XM Cloud Documentation for Developers1, a data source item is a content item that provides the content for a component. A data source item can have fields, such as text, image, or link, that can be edited by the content author in the XM Cloud Pages editor. To create a new component that displays content from a data source item, you need to follow these steps2: Create or reuse a SXA Module, which is a folder that contains the renderings, data templates, and media items for your components.
Insert a new rendering item in the SXA Module, which defines the metadata and parameters for your component. You can also clone an existing rendering item that uses a data source item and modify it as needed.
Use the JSS CLI to scaffold out a new React component in your Next.js application, which defines the layout, style, and logic for your component. You can also copy and paste an existing React component that uses a data source item and modify it as needed.
Register the React component in the Components builder and add it to the Components library.
In the XM Cloud Pages editor, drag and drop the component to the page and select or create a data source item for the component. You can also edit the data source item’s fields in the Properties
panel.
2: Create a component that uses a data source item | Sitecore Documentation 1: XM Cloud Documentation for Developers – Sitecore
Question #24
Which of these options best describes the purpose of the following query to the Experience Edge GraphQL schema?
query {
layout(site: "experienceedge", routePath: "/", language: "en") {
item {
homeltemPath: path
contentRoot: parent {
id
path
}
}
}
}
- A . To get an item by ID
- B . To get the root item of a site
- C . To get the item layout for a URL
- D . To get information about a specific content site
Correct Answer: C
C
Explanation:
The query to the Experience Edge GraphQL schema is designed to retrieve the layout information for a specific URL, which in this case is the root path (“/”) of a site named “experienceedge”. This allows developers to access the Layout Service JSON for the item, which is essential for rendering the page in a headless setup.
Reference: The Sitecore XM Cloud documentation describes the Experience Edge schema as a read-only GraphQL schema that supports common front-end use cases for headless Sitecore development, including querying an item’s layout by site and route path1.
C
Explanation:
The query to the Experience Edge GraphQL schema is designed to retrieve the layout information for a specific URL, which in this case is the root path (“/”) of a site named “experienceedge”. This allows developers to access the Layout Service JSON for the item, which is essential for rendering the page in a headless setup.
Reference: The Sitecore XM Cloud documentation describes the Experience Edge schema as a read-only GraphQL schema that supports common front-end use cases for headless Sitecore development, including querying an item’s layout by site and route path1.
Question #25
A developer is working on managing environments within the XM Cloud Deploy app. They have created a new environment for the project and linked it to a specific repository branch. However, they realize that they need to change the linked repository branch due to new developments in the project.
Which steps should they follow to achieve this?
- A . Delete the current environment and create a new one with the desired repository branch.
- B . Unlink the current repository branch and then relink the desired branch to the environment through the project’s "Options" menu.
- C . Link the desired branch to the environment directly from the repository settings. The XM Cloud Deploy app will automatically update the linked branch.
- D . Go to the project page, click the environment, choose "Options," and then "Edit environment details." In the dialog, select the desired branch from the "’Link to branch" drop-down menu and save the changes.
Correct Answer: D
D
Explanation:
According to the Sitecore XM Cloud Documentation for Developers1, you can link an environment to a specific branch of your repository in the XM Cloud Deploy app. This allows you to deploy different versions of your code to different environments. To change the linked branch for an existing environment, you need to follow these steps2:
On the navigation pane of the XM Cloud Deploy app, click Projects.
On the Projects page, click the project that contains the environment where you want to change the linked branch.
On the project page, click the environment where you want to change the linked branch.
On the environment page, click Options, then click Edit environment details.
In the Edit environment details dialog, select the desired branch from the Link to branch drop-down menu.
Click Save to confirm your changes.
2: Manage an environment in the XM Cloud Deploy app | Sitecore Documentation 1: XM Cloud Documentation for Developers – Sitecore
D
Explanation:
According to the Sitecore XM Cloud Documentation for Developers1, you can link an environment to a specific branch of your repository in the XM Cloud Deploy app. This allows you to deploy different versions of your code to different environments. To change the linked branch for an existing environment, you need to follow these steps2:
On the navigation pane of the XM Cloud Deploy app, click Projects.
On the Projects page, click the project that contains the environment where you want to change the linked branch.
On the project page, click the environment where you want to change the linked branch.
On the environment page, click Options, then click Edit environment details.
In the Edit environment details dialog, select the desired branch from the Link to branch drop-down menu.
Click Save to confirm your changes.
2: Manage an environment in the XM Cloud Deploy app | Sitecore Documentation 1: XM Cloud Documentation for Developers – Sitecore
Question #26
What is the primary role of the Experience Edge for XM Connector in Sitecore XM Cloud?
- A . To render pages dynamically
- B . To publish a static snapshot of the Layout Service output
- C . To interact directly with the xDB
- D . To manage digital marketing assets
Correct Answer: B
Question #27
When deploying to XM Cloud, how are Sitecore Content Serialization (SCS) serialized items created in the Content Management (CM) instance?
- A . The XM Cloud deploy process uses the SCS CLI to do a push once the CM instance is active.
- B . The XM Cloud deploy process creates an Items as Resources (IAR) file and layers this into the CM instance.
- C . A build pipeline must be created to use the SCS CLI push commands to push content after the XM Cloud Deploy app finishes.
- D . The XM Cloud deploy process uses serialized item batches through REST APIs at the XM Cloud CM to speed up serialization.
Correct Answer: D
D
Explanation:
The Sitecore Content Serialization (SCS) system serializes content items in and out of a Sitecore instance using YAML files1. When deploying to XM Cloud, the XM Cloud deploy process uses serialized item batches through REST APIs at the XM Cloud CM to speed up serialization2. This way, you can serialize large amounts of content items without affecting the performance of the Content Management (CM) instance2.
Reference: Sitecore Content Serialization structural overview
Sitecore Content Serialization in XM Cloud
D
Explanation:
The Sitecore Content Serialization (SCS) system serializes content items in and out of a Sitecore instance using YAML files1. When deploying to XM Cloud, the XM Cloud deploy process uses serialized item batches through REST APIs at the XM Cloud CM to speed up serialization2. This way, you can serialize large amounts of content items without affecting the performance of the Content Management (CM) instance2.
Reference: Sitecore Content Serialization structural overview
Sitecore Content Serialization in XM Cloud
Question #28
A developer needs to remove a site collection folder.
Which script should they run from the Content Editor?
- A . Remove Site Collection
- B . Remove Folder
- C . Remove Site Folder
- D . Remove Site Collection Folder
Correct Answer: D
D
Explanation:
To remove a site collection folder in Sitecore XM Cloud, the developer should run the “Remove Site Collection Folder” script from the Content Editor. This script is specifically designed to remove site collection folders and all associated items, ensuring a clean removal process.
Reference: The Sitecore XM Cloud documentation provides instructions on how to remove site collections, site collection folders, sites, and site folders using scripts available in the Content Editor1.
D
Explanation:
To remove a site collection folder in Sitecore XM Cloud, the developer should run the “Remove Site Collection Folder” script from the Content Editor. This script is specifically designed to remove site collection folders and all associated items, ensuring a clean removal process.
Reference: The Sitecore XM Cloud documentation provides instructions on how to remove site collections, site collection folders, sites, and site folders using scripts available in the Content Editor1.
Question #29
A developer is working with Sitecore’s Authoring and Management API to manage their Sitecore content using GraphQL. They want to explore and interact with the API using the GraphQL integrated development environment (IDE).
Which of the following statements is correct about using the GraphQL IDE?
- A . A developer needs to be in the sitecoreAdmin role to access the GraphQL IDE.
- B . A developer needs to be in the sitecoreSitecore Client Users role to access the GraphQL IDE.
- C . The GraphQL IDE provides read-only access to the API.
- D . The GraphQL IDE is only available for non-production environments to ensure secure interactions.
Correct Answer: B
B
Explanation:
Access to the GraphQL IDE for exploring and managing Sitecore content via the Authoring and Management API requires a developer to have the sitecoreSitecore Client Users role. This role grants the necessary permissions to use the IDE for various operations, not just read-only access.
Reference: The Sitecore XM Cloud documentation specifies the role requirements for using the GraphQL IDE1. It also provides guidance on setting up and authoring content with the GraphQL playgrounds, which are part of the IDE2.
B
Explanation:
Access to the GraphQL IDE for exploring and managing Sitecore content via the Authoring and Management API requires a developer to have the sitecoreSitecore Client Users role. This role grants the necessary permissions to use the IDE for various operations, not just read-only access.
Reference: The Sitecore XM Cloud documentation specifies the role requirements for using the GraphQL IDE1. It also provides guidance on setting up and authoring content with the GraphQL playgrounds, which are part of the IDE2.
Question #30
A developer creates a new data template for a page.
How do they ensure that the new template is available through Experience Edge?
- A . Create the template in the configured locations for Experience Edge (Feature, Foundation, Project, User Defined).
- B . Add the parent path of the template to the Experience Edge config using a patch file.
- C . Use the Experience Edge Admin API to add the template to the schema.
- D . Create the template anywhere in the /sitecore/templates folder.
Correct Answer: A
A
Explanation:
To ensure that a new data template is available through Experience Edge, it must be created in the configured locations that are recognized by the Experience Edge schema. These locations are typically structured under Feature, Foundation, Project, and User Defined paths within the Sitecore templates directory.
Reference: The Experience Edge schema documentation specifies that GraphQL types are generated only for templates under the configured paths for Feature, Foundation, Project, and User Defined, which aligns with the Helix content structure principles1.
A
Explanation:
To ensure that a new data template is available through Experience Edge, it must be created in the configured locations that are recognized by the Experience Edge schema. These locations are typically structured under Feature, Foundation, Project, and User Defined paths within the Sitecore templates directory.
Reference: The Experience Edge schema documentation specifies that GraphQL types are generated only for templates under the configured paths for Feature, Foundation, Project, and User Defined, which aligns with the Helix content structure principles1.