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 #1
Which of the following statements accurately describes the purpose of Headless variants in Sitecore XM Cloud?
- A . Headless variants define how a rendering appears and what content it displays.
- B . Headless variants determine the order in which renderings are displayed on a webpage.
- C . Headless variants enable the creation of custom rendering items for components from scratch.
- D . Headless variants allow renderings to be edited and customized in the Content Editor.
Correct Answer: A
A
Explanation:
According to the Sitecore XM Cloud Documentation for Developers1, headless variants are a way to create different versions of a rendering that can be used in different contexts or scenarios. A headless variant defines the layout, style, and content of a rendering using HTML, CSS, and JavaScript. You can create headless variants for your components in the Components builder and use them in your XM Cloud Pages. Headless variants allow you to reuse the same component with different appearances and contents without creating multiple renderings2.
2: Create a headless variant for a component | Sitecore Documentation 1: XM Cloud Documentation for Developers – Sitecore
A
Explanation:
According to the Sitecore XM Cloud Documentation for Developers1, headless variants are a way to create different versions of a rendering that can be used in different contexts or scenarios. A headless variant defines the layout, style, and content of a rendering using HTML, CSS, and JavaScript. You can create headless variants for your components in the Components builder and use them in your XM Cloud Pages. Headless variants allow you to reuse the same component with different appearances and contents without creating multiple renderings2.
2: Create a headless variant for a component | Sitecore Documentation 1: XM Cloud Documentation for Developers – Sitecore
Question #2
A developer is updating the security access rights for a new role in the Security Editor.
Which of the following permissions are they able to manage? Select all that apply.
- A . Write
- B . Debug
- C . Access
- D . Read
- E . Inheritance
Correct Answer: A, D, E
A, D, E
Explanation:
According to the Sitecore XM Cloud Documentation for Developers1, the Security Editor is a tool that allows you to assign access rights to your security accounts, such as users and roles. You can grant or deny the following access rights to individual items in the content tree2: Write C grants or denies the right to edit the item and its fields.
Read C grants or denies the right to view the item and its fields.
Inheritance C grants or denies the right to inherit the access rights from the parent item.
The other access rights, such as Debug, Access, Rename, Create, Delete, and Administer, are not available in the Security Editor, but can be assigned using other tools, such as the Access Viewer or the User Manager13.
1: XM Cloud Documentation for Developers – Sitecore 3: The security tools | Sitecore Documentation
2: The access rights | Sitecore Documentation
A, D, E
Explanation:
According to the Sitecore XM Cloud Documentation for Developers1, the Security Editor is a tool that allows you to assign access rights to your security accounts, such as users and roles. You can grant or deny the following access rights to individual items in the content tree2: Write C grants or denies the right to edit the item and its fields.
Read C grants or denies the right to view the item and its fields.
Inheritance C grants or denies the right to inherit the access rights from the parent item.
The other access rights, such as Debug, Access, Rename, Create, Delete, and Administer, are not available in the Security Editor, but can be assigned using other tools, such as the Access Viewer or the User Manager13.
1: XM Cloud Documentation for Developers – Sitecore 3: The security tools | Sitecore Documentation
2: The access rights | Sitecore Documentation
Question #3
Users in XM Cloud Pages want to modify and add specific components at a given point on the page.
What would a developer do to allow the users to accomplish this task?
- A . Enable the correct placeholder settings of the components to be modified to include the page template used for the content item users are editing.
- B . Include a placeholder as part of the layout markup and create a corresponding placeholder settings item with the appropriate allowed components.
- C . Set the standard values for the page template to include component modification options and make sure the template used by the page inherits appropriately.
- D . Enable the insert options of the components to be included forthe page template and set the appropriate allowed components.
Correct Answer: B
B
Explanation:
According to the Sitecore XM Cloud Documentation for Developers1, a placeholder is a named location on a page where components can be inserted. A placeholder can have one or more components assigned to it, and the content author can add, remove, or reorder the components in the XM Cloud Pages editor. To create a placeholder for a page, you need to follow these steps2:
In the Content Editor, create or select a rendering item that defines the metadata and parameters for your component.
In the rendering item, in the Data section, in the Layout field, enter the HTML markup for your component. Include a placeholder tag with a unique name, such as <sc-placeholder key="my-placeholder" />.
In the Content Editor, create or select a placeholder settings item that defines the allowed components for your placeholder. You can also clone an existing placeholder settings item and modify it as needed.
In the placeholder settings item, in the Data section, in the Key field, enter the same name as the placeholder tag, such as my-placeholder.
In the placeholder settings item, in the Data section, in the Allowed Controls field, select the components that you want to allow in the placeholder. You can also use the Edit button to open the Allowed Controls dialog box and select the components from a tree view.
Register the component and the placeholder settings in the Components builder and add them to the Components library.
In the XM Cloud Pages editor, drag and drop the component to the page and use the placeholder to insert other components as needed.
2: Create a placeholder for a component | Sitecore Documentation 1: XM Cloud Documentation for Developers – Sitecore
B
Explanation:
According to the Sitecore XM Cloud Documentation for Developers1, a placeholder is a named location on a page where components can be inserted. A placeholder can have one or more components assigned to it, and the content author can add, remove, or reorder the components in the XM Cloud Pages editor. To create a placeholder for a page, you need to follow these steps2:
In the Content Editor, create or select a rendering item that defines the metadata and parameters for your component.
In the rendering item, in the Data section, in the Layout field, enter the HTML markup for your component. Include a placeholder tag with a unique name, such as <sc-placeholder key="my-placeholder" />.
In the Content Editor, create or select a placeholder settings item that defines the allowed components for your placeholder. You can also clone an existing placeholder settings item and modify it as needed.
In the placeholder settings item, in the Data section, in the Key field, enter the same name as the placeholder tag, such as my-placeholder.
In the placeholder settings item, in the Data section, in the Allowed Controls field, select the components that you want to allow in the placeholder. You can also use the Edit button to open the Allowed Controls dialog box and select the components from a tree view.
Register the component and the placeholder settings in the Components builder and add them to the Components library.
In the XM Cloud Pages editor, drag and drop the component to the page and use the placeholder to insert other components as needed.
2: Create a placeholder for a component | Sitecore Documentation 1: XM Cloud Documentation for Developers – Sitecore
Question #4
A developer can reference an external code base that includes components so they can be used in the Components builder interface.
Which of the following are possible results of adding React components to the Components builder? Select all that apply.
- A . The registered component is scoped to only one environment.
- B . A content author can enter values for the defined input parameters.
- C . The registered component is part of the Components library.
- D . The registered component can be previewed in the Component builder.
Correct Answer: B, C, D
B, C, D
Explanation:
According to the Sitecore XM Cloud Documentation for Developers1, the Components builder is a tool that allows you to create and manage components for your XM Cloud Pages. You can use the Components builder to register React components from an external code base, such as a GitHub repository or a local folder. When you add a React component to the Components builder, the following results are possible:
B) A content author can enter values for the defined input parameters. When you register a React component, you can define input parameters that allow the content author to customize the component’s appearance and behavior. For example, you can define a text parameter that lets the content author enter the title of the component. The input parameters are displayed in the Properties panel of the XM Cloud Pages editor2.
C) The registered component is part of the Components library. When you register a React component, it becomes available in the Components library, which is a collection of components that you can use in your XM Cloud Pages. You can access the Components library from the Components builder or the XM Cloud Pages editor. You can also organize your components into categories and subcategories in the Components library3.
D) The registered component can be previewed in the Component builder. When you register a React component, you can preview how it looks and behaves in the Component builder. You can also edit the component’s code, input parameters, and metadata in the Component builder4.
The following result is not possible:
A) The registered component is scoped to only one environment. When you register a React component, it is available in all the environments of your XM Cloud project. You cannot limit the component’s availability to a specific environment. However, you can control the component’s visibility and accessibility by using the Publish and Archive actions in the Component builder4.
2: Register a React component | Sitecore Documentation 3: Manage the Components library |
Sitecore Documentation 4: Manage a component in the Component builder | Sitecore
Documentation 1: XM Cloud Documentation for Developers – Sitecore
B, C, D
Explanation:
According to the Sitecore XM Cloud Documentation for Developers1, the Components builder is a tool that allows you to create and manage components for your XM Cloud Pages. You can use the Components builder to register React components from an external code base, such as a GitHub repository or a local folder. When you add a React component to the Components builder, the following results are possible:
B) A content author can enter values for the defined input parameters. When you register a React component, you can define input parameters that allow the content author to customize the component’s appearance and behavior. For example, you can define a text parameter that lets the content author enter the title of the component. The input parameters are displayed in the Properties panel of the XM Cloud Pages editor2.
C) The registered component is part of the Components library. When you register a React component, it becomes available in the Components library, which is a collection of components that you can use in your XM Cloud Pages. You can access the Components library from the Components builder or the XM Cloud Pages editor. You can also organize your components into categories and subcategories in the Components library3.
D) The registered component can be previewed in the Component builder. When you register a React component, you can preview how it looks and behaves in the Component builder. You can also edit the component’s code, input parameters, and metadata in the Component builder4.
The following result is not possible:
A) The registered component is scoped to only one environment. When you register a React component, it is available in all the environments of your XM Cloud project. You cannot limit the component’s availability to a specific environment. However, you can control the component’s visibility and accessibility by using the Publish and Archive actions in the Component builder4.
2: Register a React component | Sitecore Documentation 3: Manage the Components library |
Sitecore Documentation 4: Manage a component in the Component builder | Sitecore
Documentation 1: XM Cloud Documentation for Developers – Sitecore
Question #5
What is the sitecore.json file in a development solution?
- A . The environment variables file for the Sitecore Docker deployment
- B . The configuration file for the Sitecore development tooling
- C . The solution integration file needed for deploying code changes to the environment
- D . A custom configuration file defining a solution for headless environments
Correct Answer: C
C
Explanation:
The sitecore.json file is located in the root folder of the solution and it comes with the XM Cloud
Foundation Head starter kit1. In here we can configure what *.module.json files should be considered for serialization configuration, the plugins with it’s particular versions and some general settings for the serialization1.
Reference: Setup Sitecore Content Serialization
Sitecore Content Serialization structural overview
C
Explanation:
The sitecore.json file is located in the root folder of the solution and it comes with the XM Cloud
Foundation Head starter kit1. In here we can configure what *.module.json files should be considered for serialization configuration, the plugins with it’s particular versions and some general settings for the serialization1.
Reference: Setup Sitecore Content Serialization
Sitecore Content Serialization structural overview
Question #6
A developer wants to deploy to XM Cloud, but the project is not using a source code provider that has an out-of-the-box connector for XM Cloud.
How can they deploy the site to XM Cloud?
- A . Use the Sitecore Cloud CLI to create a project and deployment.
- B . Create a Sitecore Update Package using SCS to include items and files.
- C . Use Vercel to connect to their source code provider and deploy.
- D . Create a custom connector to be used with the XM Cloud Deploy app.
Correct Answer: A
A
Explanation:
According to the Sitecore XM Cloud Documentation for Developers1, the Sitecore Cloud CLI is a command-line tool that allows you to perform operations against local or remote XM Cloud instances. You can use the Sitecore Cloud CLI to deploy your existing XM Cloud-compatible Sitecore XM solution in the cloud, regardless of the source code provider you are using. To deploy your solution to XM Cloud using the Sitecore Cloud CLI, you need to follow these steps2: Install the Sitecore Cloud CLI on your workstation.
Authorize the Sitecore Cloud CLI with your Sitecore Cloud Portal organization.
Create a project in the XM Cloud Deploy app using the Sitecore Cloud CLI.
Connect your local environment to the project using the Sitecore Cloud CLI.
Push your serialized items to the project using the Sitecore Cloud CLI.
Deploy your solution to an XM Cloud environment using the Sitecore Cloud CLI.
2: Walkthrough: Creating an XM Cloud project using the Sitecore CLI 1: XM Cloud Documentation for Developers – Sitecore
A
Explanation:
According to the Sitecore XM Cloud Documentation for Developers1, the Sitecore Cloud CLI is a command-line tool that allows you to perform operations against local or remote XM Cloud instances. You can use the Sitecore Cloud CLI to deploy your existing XM Cloud-compatible Sitecore XM solution in the cloud, regardless of the source code provider you are using. To deploy your solution to XM Cloud using the Sitecore Cloud CLI, you need to follow these steps2: Install the Sitecore Cloud CLI on your workstation.
Authorize the Sitecore Cloud CLI with your Sitecore Cloud Portal organization.
Create a project in the XM Cloud Deploy app using the Sitecore Cloud CLI.
Connect your local environment to the project using the Sitecore Cloud CLI.
Push your serialized items to the project using the Sitecore Cloud CLI.
Deploy your solution to an XM Cloud environment using the Sitecore Cloud CLI.
2: Walkthrough: Creating an XM Cloud project using the Sitecore CLI 1: XM Cloud Documentation for Developers – Sitecore
Question #7
Which of the following are ways to create an XM Cloud environment?
- A . Environments are automatically created during the deployment; it is not required to create environments explicitly.
- B . Defining the environment at .env file from the source code (laC) and re-deploying it.
- C . The CLI, the Deploy app, or Rest API.
- D . The only way to create a cloud environment is from the Sitecore Cloud Portal Ul.
Correct Answer: C
C
Explanation:
According to the Sitecore XM Cloud Documentation for Developers1, there are three ways to create an XM Cloud environment:
Using the Sitecore CLI, which is a command-line tool that allows you to perform operations against local or remote XM Cloud instances. You can use the Sitecore CLI to create a project and an environment using the sitecore project create and sitecore environment create commands2. Using the XM Cloud Deploy app, which is a web application that allows you to create and manage projects, environments, and deployments. You can use the XM Cloud Deploy app to create a project and an environment using the user interface3.
Using the XM Cloud Deploy API, which is a RESTful API that allows you to programmatically interact with the XM Cloud Deploy app. You can use the XM Cloud Deploy API to create a project and an environment using HTTP requests4.
2: Walkthrough: Creating an XM Cloud project using the Sitecore CLI 3: Create a project in the Deploy
app 4: [XM Cloud Deploy API Reference] 1: XM Cloud Documentation for Developers – Sitecore
C
Explanation:
According to the Sitecore XM Cloud Documentation for Developers1, there are three ways to create an XM Cloud environment:
Using the Sitecore CLI, which is a command-line tool that allows you to perform operations against local or remote XM Cloud instances. You can use the Sitecore CLI to create a project and an environment using the sitecore project create and sitecore environment create commands2. Using the XM Cloud Deploy app, which is a web application that allows you to create and manage projects, environments, and deployments. You can use the XM Cloud Deploy app to create a project and an environment using the user interface3.
Using the XM Cloud Deploy API, which is a RESTful API that allows you to programmatically interact with the XM Cloud Deploy app. You can use the XM Cloud Deploy API to create a project and an environment using HTTP requests4.
2: Walkthrough: Creating an XM Cloud project using the Sitecore CLI 3: Create a project in the Deploy
app 4: [XM Cloud Deploy API Reference] 1: XM Cloud Documentation for Developers – Sitecore
Question #8
A developer tried to exclude fields in a Sitecore Content Serialization package.
Which file should they use to specify the excluded fields?
- A . user.json
- B . sitecore.config
- C . sitecore.json
- D . xmcloud.build.json
Correct Answer: C
C
Explanation:
The excluded fields feature is available from CLI 4.0 or later1. This way, you can reduce the size of your Sitecore Content Serialization package and avoid unnecessary serialization of fields that are not relevant for your deployment scenario1.
Reference: Sitecore Content Serialization structural overview
Configure excluded fields
C
Explanation:
The excluded fields feature is available from CLI 4.0 or later1. This way, you can reduce the size of your Sitecore Content Serialization package and avoid unnecessary serialization of fields that are not relevant for your deployment scenario1.
Reference: Sitecore Content Serialization structural overview
Configure excluded fields
Question #9
Which of the following statements are true about the Sitecore Headless Services in XM Cloud? (Choose two)
- A . They allow developers to use a completely headless architecture.
- B . They replace traditional ASP.NET web forms.
- C . They support both GraphQL and RESTful APIs.
- D . They require the Sitecore Desktop experience for content management.
Correct Answer: A, C
Question #10
What does the default scope for a serialization include if the scope parameter is not defined?
- A . DescendantsOnly
- B . Singleitem
- C . ItemAndDescendants
- D . ItemAndChildren
Correct Answer: C
C
Explanation:
The default scope for a serialization in Sitecore Content Serialization (SCS) includes all the content items under the specified path and all their descendants1. You can configure what and how content items are included and excluded from serialization in a module file such as Project.module.json1. You can also use rules to configure the serialization of content item trees with different scopes1.
Reference: Sitecore Content Serialization structural overview
The default serialization format
C
Explanation:
The default scope for a serialization in Sitecore Content Serialization (SCS) includes all the content items under the specified path and all their descendants1. You can configure what and how content items are included and excluded from serialization in a module file such as Project.module.json1. You can also use rules to configure the serialization of content item trees with different scopes1.
Reference: Sitecore Content Serialization structural overview
The default serialization format