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 #41
A developer needs to create a site for a company and must define the data structures in Sitecore to create items and content.
What should the developer use to define the data structures?
- A . Templates
- B . Rendering parameters
- C . Renderings
- D . Components data sources
Correct Answer: A
A
Explanation:
According to the Sitecore XM Cloud Documentation for Developers1, templates are the fundamental concept in Sitecore that determine the structure and behavior of content items. Templates define the fields, sections, and parameters that make up each item. Templates also enable inheritance, which allows items to share common fields and properties from their base templates. There are different types of templates in Sitecore, such as data templates, branch templates, and command templates2. To create the data structures for a site, the developer should use data templates, which define the fields used to control how data is entered. Data templates form the framework around which items are built. Sitecore associates a data template with every item in the content tree. The field types determine the editing controls shown to the user and they contain the raw values that are stored in the database2.
The other options are not correct:
Rendering parameters are custom properties for a component that can be changed by the content author in the XM Cloud Pages editor. Rendering parameters allow the content author to customize the appearance and behavior of the component, but they do not define the data structure of the content item3.
Renderings are items that define the metadata and parameters for a component. Renderings link a component to a data template, a headless variant, and a rendering parameter template. Renderings are used to create and manage components in the Components builder, but they do not define the data structure of the content item4.
Component data sources are content items that provide the content for a component. Component data sources can have fields, such as text, image, or link, that can be edited by the content author in the XM Cloud Pages editor. Component data sources are based on data templates, but they are not templates themselves4.
2: Data definition and template overview | Sitecore Documentation 3: Create a component with
rendering parameters | Sitecore Documentation 4: Create a component that uses a data source item
| Sitecore Documentation 1: XM Cloud Documentation for Developers – Sitecore
A
Explanation:
According to the Sitecore XM Cloud Documentation for Developers1, templates are the fundamental concept in Sitecore that determine the structure and behavior of content items. Templates define the fields, sections, and parameters that make up each item. Templates also enable inheritance, which allows items to share common fields and properties from their base templates. There are different types of templates in Sitecore, such as data templates, branch templates, and command templates2. To create the data structures for a site, the developer should use data templates, which define the fields used to control how data is entered. Data templates form the framework around which items are built. Sitecore associates a data template with every item in the content tree. The field types determine the editing controls shown to the user and they contain the raw values that are stored in the database2.
The other options are not correct:
Rendering parameters are custom properties for a component that can be changed by the content author in the XM Cloud Pages editor. Rendering parameters allow the content author to customize the appearance and behavior of the component, but they do not define the data structure of the content item3.
Renderings are items that define the metadata and parameters for a component. Renderings link a component to a data template, a headless variant, and a rendering parameter template. Renderings are used to create and manage components in the Components builder, but they do not define the data structure of the content item4.
Component data sources are content items that provide the content for a component. Component data sources can have fields, such as text, image, or link, that can be edited by the content author in the XM Cloud Pages editor. Component data sources are based on data templates, but they are not templates themselves4.
2: Data definition and template overview | Sitecore Documentation 3: Create a component with
rendering parameters | Sitecore Documentation 4: Create a component that uses a data source item
| Sitecore Documentation 1: XM Cloud Documentation for Developers – Sitecore
Question #42
What information can be found in the deployment logs?
- A . Content Management and Content Delivery deployment logs
- B . Content Management instance and Rendering Hosting logs
- C . Provisioning, Deployment, and Publishing information
- D . Provisioning, Build, Deployment, and Post Action information
Correct Answer: D
D
Explanation:
According to the Sitecore XM Cloud Documentation for Developers1, the deployment log displays the progress, status, warnings, and errors of an XM Cloud deployment. From the deployment log, you can also cancel a running deployment, rerun a failed deployment, promote the deployment to another environment, download logs, or open the XM Cloud Dashboard. The logs include information about:
Provisioning C the process of creating and configuring the resources required for the environment, such as the Content Management and Content Delivery instances, the database, the storage, and the network.
Build C the process of compiling the source code, running tests, and generating the deployment package.
Deployment C the process of deploying the package to the environment and applying any configuration changes.
Post Action C the process of performing any additional tasks after the deployment, such as publishing, indexing, or clearing caches.
1: XM Cloud Documentation for Developers – Sitecore
D
Explanation:
According to the Sitecore XM Cloud Documentation for Developers1, the deployment log displays the progress, status, warnings, and errors of an XM Cloud deployment. From the deployment log, you can also cancel a running deployment, rerun a failed deployment, promote the deployment to another environment, download logs, or open the XM Cloud Dashboard. The logs include information about:
Provisioning C the process of creating and configuring the resources required for the environment, such as the Content Management and Content Delivery instances, the database, the storage, and the network.
Build C the process of compiling the source code, running tests, and generating the deployment package.
Deployment C the process of deploying the package to the environment and applying any configuration changes.
Post Action C the process of performing any additional tasks after the deployment, such as publishing, indexing, or clearing caches.
1: XM Cloud Documentation for Developers – Sitecore
Question #43
A developer is tasked with creating an item using the Sitecore Authoring and Management GraphQL API.
Which of the following GraphQL mutations is the correct way to create a new item?
- A . createOrUpdateltem
- B . create Templateltem
- C . createltem
- D . updateltem
Correct Answer: C
C
Explanation:
The correct GraphQL mutation to create a new item in Sitecore XM Cloud is createItem. This mutation allows developers to specify the necessary details such as the item’s name, template ID, parent ID, language, and fields to create a new content item within the Sitecore content tree.
Reference: The usage of the createItem mutation is documented in the Sitecore XM Cloud Developer’s Guide, which provides examples and explanations for authoring operations, including item creation1. Additionally, the Sitecore Stack Exchange provides insights into the available mutations for item management, confirming the use of createItem for creating new items2.
C
Explanation:
The correct GraphQL mutation to create a new item in Sitecore XM Cloud is createItem. This mutation allows developers to specify the necessary details such as the item’s name, template ID, parent ID, language, and fields to create a new content item within the Sitecore content tree.
Reference: The usage of the createItem mutation is documented in the Sitecore XM Cloud Developer’s Guide, which provides examples and explanations for authoring operations, including item creation1. Additionally, the Sitecore Stack Exchange provides insights into the available mutations for item management, confirming the use of createItem for creating new items2.
Question #44
A developer wants to add a new language to a headless SXA site.
Which steps are required to add a new language in XM Cloud?
- A . Install a language pack on the Content Management instance and then add the language in /sitecore/system/languages.
- B . Add language in /sitecore/system/languages. Then, on the content item, change the language dropdown to the new language and add a new version.
- C . Add language in /sitecore/system/languages, right click the site root, and go to scripts -> Add Site language.
- D . They must enter the country code in the Language field. Then, on the content item, change the language dropdown to the new language and add a new version.
Correct Answer: C
C
Explanation:
C
Explanation:
Question #45
A developer is using the Content Editor to set placeholder restrictions on a placeholder called headless-footer.
Because these restrictions have been set on the placeholder settings within /sitecore/Layout/Placeholder Settings, which of the following statements is correct?
- A . The restrictions apply for all placeholders called headless-footer within a single site in the XM
Cloud Content Management instance. - B . The restrictions apply for all placeholders called headless-footer on every page of every site that is in the XM Cloud Content Management instance.
- C . The restrictions only apply for a placeholder called headless-footer on a designated page.
- D . The restrictions only apply for subsequently created versions of a placeholder called headless-footer.
Correct Answer: B
B
Explanation:
According to the Sitecore XM Cloud Documentation for Developers1, in the Content Editor, you can set placeholder restrictions for your layout placeholders. These restrictions are applied on all pages in the site. For example, if you add restrictions for a footer, these apply for all footers on every page of the site. In this way, you can control the content that content authors can place in layout placeholders. To add a placeholder setting for a site, you need to create a placeholder item in the Layout/Placeholder Settings folder and enter the placeholder key and the allowed components2.
The other options are not correct:
A) The restrictions apply for all placeholders called headless-footer within a single site in the XM Cloud Content Management instance. This option is too narrow, as the placeholder restrictions apply to all sites that use the same placeholder key, not just one site.
C) The restrictions only apply for a placeholder called headless-footer on a designated page. This option is too specific, as the placeholder restrictions apply to all pages that use the same placeholder key, not just one page. However, you can create placeholder restrictions on specific pages in the Experience Editor, if you want to override the default settings3.
D) The restrictions only apply for subsequently created versions of a placeholder called headless-footer. This option is incorrect, as the placeholder restrictions apply to all versions of the placeholder, not just the new ones.
2: Set placeholder restrictions | Sitecore Documentation 3: Set placeholder restrictions | Sitecore
Documentation 1: XM Cloud Documentation for Developers – Sitecore
B
Explanation:
According to the Sitecore XM Cloud Documentation for Developers1, in the Content Editor, you can set placeholder restrictions for your layout placeholders. These restrictions are applied on all pages in the site. For example, if you add restrictions for a footer, these apply for all footers on every page of the site. In this way, you can control the content that content authors can place in layout placeholders. To add a placeholder setting for a site, you need to create a placeholder item in the Layout/Placeholder Settings folder and enter the placeholder key and the allowed components2.
The other options are not correct:
A) The restrictions apply for all placeholders called headless-footer within a single site in the XM Cloud Content Management instance. This option is too narrow, as the placeholder restrictions apply to all sites that use the same placeholder key, not just one site.
C) The restrictions only apply for a placeholder called headless-footer on a designated page. This option is too specific, as the placeholder restrictions apply to all pages that use the same placeholder key, not just one page. However, you can create placeholder restrictions on specific pages in the Experience Editor, if you want to override the default settings3.
D) The restrictions only apply for subsequently created versions of a placeholder called headless-footer. This option is incorrect, as the placeholder restrictions apply to all versions of the placeholder, not just the new ones.
2: Set placeholder restrictions | Sitecore Documentation 3: Set placeholder restrictions | Sitecore
Documentation 1: XM Cloud Documentation for Developers – Sitecore
Question #46
Which of the following tasks are performed by the publishing pipeline to create an accurate snapshot of the content available for publishing from the Content Management instance? Select all that apply.
- A . Calculating additional entities to publish
- B . Calculating dependencies
- C . Archiving expired content
- D . Resolving dependencies
Correct Answer: A, B, D
A, B, D
Explanation:
The publishing pipeline in Sitecore XM Cloud performs several tasks to ensure an accurate snapshot of content is available for publishing from the Content Management instance. These tasks include calculating additional entities to publish, calculating dependencies, and resolving dependencies. These steps are crucial for maintaining the integrity and consistency of the published content.
Reference: The Sitecore XM Cloud documentation outlines the publishing pipeline process, which includes the calculation and resolution of entities and dependencies as part of creating a publishing manifest1.
A, B, D
Explanation:
The publishing pipeline in Sitecore XM Cloud performs several tasks to ensure an accurate snapshot of content is available for publishing from the Content Management instance. These tasks include calculating additional entities to publish, calculating dependencies, and resolving dependencies. These steps are crucial for maintaining the integrity and consistency of the published content.
Reference: The Sitecore XM Cloud documentation outlines the publishing pipeline process, which includes the calculation and resolution of entities and dependencies as part of creating a publishing manifest1.
Question #47
Why should a developer assign security to roles instead of users when setting up security on a site?
- A . Security roles can assign individual rights and permissions to be configured by users.
- B . Role-based security allows multiple users to have the same username.
- C . Security can be managed more efficiently as the rights and permissions apply to a group of users.
- D . Individual users with a role can set and configure their own item security permissions.
Correct Answer: C
C
Explanation:
According to the Sitecore XM Cloud Documentation for Developers1, security roles define how different users access different types of records in Sitecore. To control access to data and resources, you can create or modify security roles and change the security roles that are assigned to your users. A user can have multiple security roles. Security role privileges are cumulative. Users are granted the privileges that are available in each role that’s assigned to them2.
This makes it easier for you to manage your security system because you do not necessarily have to assign access rights for each item in your content tree. Instead, you only need to assign and manage the access rights on the parent items and then specify whether their descendants can inherit these access rights3.
C
Explanation:
According to the Sitecore XM Cloud Documentation for Developers1, security roles define how different users access different types of records in Sitecore. To control access to data and resources, you can create or modify security roles and change the security roles that are assigned to your users. A user can have multiple security roles. Security role privileges are cumulative. Users are granted the privileges that are available in each role that’s assigned to them2.
This makes it easier for you to manage your security system because you do not necessarily have to assign access rights for each item in your content tree. Instead, you only need to assign and manage the access rights on the parent items and then specify whether their descendants can inherit these access rights3.
Question #48
A multinational clothing company wants to create regional sites for its online presence. Each site would follow the same branding but have unique content per region. The content architecture requires a site per region. Of the options presented below, which is the most efficient approach to deploy the rendering host?
- A . Use separate instances of XM Cloud for each brand and country to maintain separation.
- B . rendering host application deployed for each site.
- C . A single rendering host application using the JSS multisite feature.
- D . Create a single site collection and site for all brands and countries and also manage their resources manually.
Correct Answer: C
C
Explanation:
For a multinational clothing company looking to create regional sites with the same branding but unique content per region, the most efficient approach is to use a single rendering host application that leverages the JSS multisite feature. This allows for the management of multiple sites within a single instance, facilitating shared resources and centralized updates while still allowing for regional customization.
Reference: The Sitecore XM Cloud documentation suggests using a single rendering host application for multiple sites, which can be achieved through configurations and the JSS multisite feature, as detailed in the editing and rendering hosts section1. This approach aligns with the recommended practices for deploying and managing content in XM Cloud environments2.
C
Explanation:
For a multinational clothing company looking to create regional sites with the same branding but unique content per region, the most efficient approach is to use a single rendering host application that leverages the JSS multisite feature. This allows for the management of multiple sites within a single instance, facilitating shared resources and centralized updates while still allowing for regional customization.
Reference: The Sitecore XM Cloud documentation suggests using a single rendering host application for multiple sites, which can be achieved through configurations and the JSS multisite feature, as detailed in the editing and rendering hosts section1. This approach aligns with the recommended practices for deploying and managing content in XM Cloud environments2.
Question #49
Where can a developer create and edit data templates?
- A . Pages or Explorer
- B . Explorer or Portal
- C . Content Editor or Pages
- D . Content Editor
Correct Answer: C
C
Explanation:
According to the Sitecore XM Cloud Documentation for Developers1, you create and edit data templates in the Template Manager or the Template Builder in the Content Editor, which provide the same functionality with the only difference being the root item of the content tree that is shown in the user interface. In the Template Manager, the root item of the content tree is /Sitecore/Templates.
You can also create additional data templates to be used in XM Cloud Pages2, which are web pages that can be customized with layouts and content.
C
Explanation:
According to the Sitecore XM Cloud Documentation for Developers1, you create and edit data templates in the Template Manager or the Template Builder in the Content Editor, which provide the same functionality with the only difference being the root item of the content tree that is shown in the user interface. In the Template Manager, the root item of the content tree is /Sitecore/Templates.
You can also create additional data templates to be used in XM Cloud Pages2, which are web pages that can be customized with layouts and content.
Question #50
A developer needs to clear the Experience Edge cache to resolve a publishing issue.
How can that be done?
- A . Use the Experience Edge Admin API to delete the content.
- B . Go to https://sitecore/admin/cache.aspx and clear the cache.
- C . Submit a support ticket to restart the Experience Edge tenant.
- D . Use the Experience Edge Admin API to clear the cache for the tenant.
Correct Answer: D
D
Explanation:
To clear the Experience Edge cache and resolve publishing issues, a developer can use the Experience Edge Admin API. This API provides a specific endpoint to clear the entire cache for a tenant, which is the recommended method for directly addressing cache-related problems without deleting content or restarting services.
Reference: The Sitecore XM Cloud documentation for developers provides information on the Admin API, including the ClearCacheForTenant endpoint, which is used to clear the cache1. This action is part of the administration capabilities offered by the API to manage the Experience Edge service effectively2.
D
Explanation:
To clear the Experience Edge cache and resolve publishing issues, a developer can use the Experience Edge Admin API. This API provides a specific endpoint to clear the entire cache for a tenant, which is the recommended method for directly addressing cache-related problems without deleting content or restarting services.
Reference: The Sitecore XM Cloud documentation for developers provides information on the Admin API, including the ClearCacheForTenant endpoint, which is used to clear the cache1. This action is part of the administration capabilities offered by the API to manage the Experience Edge service effectively2.