[Jan-2026] Free Sitecore-XM-Cloud-Developer Exam Questions Sitecore-XM-Cloud-Developer Actual Free Exam Questions
Verified Sitecore-XM-Cloud-Developer dumps and 52 unique questions
NEW QUESTION # 22
In the content tree, an administrator-level user cannot see the Layouts or Templates nodes. Which of the following would explain the missing nodes?
- A. The Layouts and Templates folders need to be created by a developer.
- B. The "Hidden items" check box has been unselected on the View tab of the ribbon.
- C. A layout has not been assigned for the content tree in the Content Editor.
- D. A template has not been established for the Content Editor.
Answer: B
Explanation:
In Sitecore XM Cloud, if an administrator-level user cannot see the Layouts or Templates nodes in the content tree, it is likely because the "Hidden items" option is not selected in the Content Editor's View tab. These nodes are typically marked as hidden to streamline the interface for users.
References:This solution is consistent with common practices in Sitecore content management, as indicated by community discussions and troubleshooting guides that address similar issues with hidden items in the content tree1.
NEW QUESTION # 23
A developer needs to configure a rendering in order to use dynamic placeholders. Which of the following steps is required? Select all that apply.
- A. In the component TSX file, set a unique placeholder key value that has not yet been defined.
- B. Link the placeholder settings item to the rendering item.
- C. Include the IDynamicPlaceholder base template in the Rendering Parameters template.
- D. Define the placeholder key using a question mark (?) in the placeholder settings item.
Answer: B,C,D
Explanation:
To configure a rendering for the use of dynamic placeholders in Sitecore XM Cloud, the following steps are required:
Include the IDynamicPlaceholder base templatein the Rendering Parameters template to enable dynamic assignment of IDs to the placeholder key.
Link the placeholder settings itemto the rendering item to ensure that the dynamic placeholders are correctly associated with the rendering.
Define the placeholder key using a wildcardin the placeholder settings item, which allows for the generation of unique placeholder keys for every component on the page.
References:The Sitecore XM Cloud documentation provides a walkthrough on configuring components to use dynamic placeholders, detailing the steps required to set up dynamic placeholders1.This includes adding theIsRenderingsWithDynamicPlaceholdersproperty to the component item, including theIDynamicPlaceholderbase template in the Rendering Parameters template, defining the placeholder key using a wildcard, and linking the placeholder settings item to the component1.
NEW QUESTION # 24
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. 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.
- B. Add language in /sitecore/system/languages, right click the site root, and go to scripts -> Add Site language.
- C. Add language in /sitecore/system/languages. Then, on the content item, change the language dropdown to the new language and add a new version.
- D. Install a language pack on the Content Management instance and then add the language in
/sitecore/system/languages.
Answer: B
NEW QUESTION # 25
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 custom connector to be used with the XM Cloud Deploy app.
- C. Create a Sitecore Update Package using SCS to include items and files.
- D. Use Vercel to connect to their source code provider and deploy.
Answer: 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 CLI1:XM Cloud Documentation for Developers - Sitecore
NEW QUESTION # 26
What does the default scope for a serialization include if the scope parameter is not defined?
- A. ItemAndChildren
- B. ItemAndDescendants
- C. DescendantsOnly
- D. Singleitem
Answer: B
Explanation:
The default scope for a serialization in Sitecore Content Serialization (SCS) includesall the content itemsunder the specified path andall 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.
References:
Sitecore Content Serialization structural overview
The default serialization format
NEW QUESTION # 27
A developer needs to log in to the XM Cloud Deploy app to create a project using a starter template but requires the correct permissions. Which of the following should happen?
- A. Only the Organization Owner can update their role in the Sitecore Cloud Portal.
- B. Only the Organization Owner can update their role using the XM Cloud Deploy app.
- C. An Organization Admin or Organization Owner must update their role.
- D. An Organization Admin or Organization Owner must update their role using the XM Cloud Deploy app.
Answer: C
Explanation:
According to the Sitecore XM Cloud Documentation for Developers1, to use the XM Cloud Deploy app, you must be an Organization Admin or Organization Owner in your Sitecore Cloud Portal organization.An Organization Admin or Organization Owner can grant a team member access to the XM Cloud Deploy app by changing their organization role to Admin2. This can be done in the Sitecore Cloud Portal, not in the XM Cloud Deploy app.
2:Invite team members to your Sitecore Cloud Portal organization1:XM Cloud Documentation for Developers
- Sitecore
NEW QUESTION # 28
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 can be previewed in the Component builder.
- B. The registered component is scoped to only one environment.
- C. A content author can enter values for the defined input parameters.
- D. The registered component is part of the Components library.
Answer: A,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 controlthe component's visibility and accessibility by using the Publish and Archive actions in the Component builder4.
2:Register a React component | Sitecore Documentation3:Manage the Components library | Sitecore Documentation4:Manage a component in the Component builder | Sitecore Documentation1:XM Cloud Documentation for Developers - Sitecore
NEW QUESTION # 29
When a developer designates a Sitecore template field multilist type, what should they do next?
- A. Set the multilist list item's data source.
- B. Add the list items to the multilist item.
- C. Add standard values to the item.
- D. Add a multilist field to the template.
Answer: A
Explanation:
After designating a Sitecore template field as a multilist type, the next step is to set the data source for the multilist. This involves specifying the location within the content tree from which the list items will be drawn.
The data source defines the scope of items that can be selected and displayed in the multilist.
References:The Sitecore XM Cloud documentation provides guidance on configuring selection fields, including multilists.It details how to control the list of items by setting the Source property, which determines the items that appear in the selection list1.Additionally, developers can use the Sitecore.Data.Fields.MultilistField class to manage the items in a multilist field, including setting the data source2.
NEW QUESTION # 30
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. rendering host application deployed for each site.
- B. Create a single site collection and site for all brands and countries and also manage theirresources manually.
- C. A single rendering host application using the JSS multisite feature.
- D. Use separate instances of XM Cloud for each brand and country to maintain separation.
Answer: 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.
References: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.
NEW QUESTION # 31
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. Enable the insert options of the components to be included forthe page template and set the appropriate allowed components.
- C. Include a placeholder as part of the layout markup and create a corresponding placeholder settings item with the appropriate allowed components.
- D. Set the standard values for the page template to include component modification options and make sure the template used by the page inherits appropriately.
Answer: C
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 asmy-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 Documentation1:XM Cloud Documentation for Developers
- Sitecore
NEW QUESTION # 32
Where can a developer create and edit data templates?
- A. Content Editor or Pages
- B. Pages or Explorer
- C. Content Editor
- D. Explorer or Portal
Answer: A
Explanation:
According to the Sitecore XM Cloud Documentation for Developers1, you create and edit data templates in theTemplate Manageror theTemplate Builderin theContent 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.
NEW QUESTION # 33
A developer tried to exclude fields in a Sitecore Content Serialization package. Which file should they use to specify the excluded fields?
- A. xmcloud.build.json
- B. sitecore.json
- C. user.json
- D. sitecore.config
Answer: B
Explanation:
The excluded fields feature is available fromCLI 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.
References:
Sitecore Content Serialization structural overview
Configure excluded fields
NEW QUESTION # 34
A developer has set up a local XM Cloud development environment and would like to connect Sitecore Pages to their locally running XM Cloud instance. However, after following the necessary steps, they're facing issues with the connection. Of the options below, what is the most likely potential reason for this issue?
- A. The environment variable "SITECORE_Pages_CORS_Allowed_Origins" is not correctly configured to include pages.sitecorecloud.io.
- B. The value of the local storage entry ''Sitecore.Pages.LocaIXmCloudUrl" should be set to https://pages.
sitecorecloud.io. - C. The value of the local storage entry "Sitecore.PagesXmCloud" should be setto enabled.
- D. The browser developer tools console does not support the local storage functionality required for this connection.
Answer: A
Explanation:
When connectingSitecore Pages(the visual page editor in XM Cloud) to alocal XM Cloud development environment, the connection may fail due toCORS (Cross-Origin Resource Sharing) restrictions.
* Sitecore Pagesis hosted onhttps://pages.sitecorecloud.io, which loads content from the developer's local Sitecore instance.
* Thelocal Sitecore instance must allow requests frompages.sitecorecloud.io, or the connection will fail due toCORS policy restrictions.
* To fix this, the developer must ensure that theenvironment variable
SITECORE_Pages_CORS_Allowed_Originsis correctly setto includehttps://pages.sitecorecloud.io.
* In a localDocker-based XM Cloud setup, this can be configured indocker-compose.override.ymllike this:
#Correct answer: D (The environment variableSITECORE_Pages_CORS_Allowed_Originsis not correctly configured to include pages.sitecorecloud.io.)environment:
- SITECORE_Pages_CORS_Allowed_Origins=https://pages.sitecorecloud.io
* If running Sitecore locally without Docker, this setting should be added to theappsettings.jsonfile or set as a system environment variable.
* (A) The value of the local storage entry'Sitecore.Pages.LocaIXmCloudUrl'should be set to
https://pages.sitecorecloud.io# Incorrect
* Thecorrect keyis'Sitecore.Pages.LocalXmCloudUrl', but it should point tothe local Sitecore instance, nothttps://pages.sitecorecloud.io.
* Example:
#Why Other Options Are Incorrect:localStorage.setItem('Sitecore.Pages.LocalXmCloudUrl',
'https://xmcloud.localhost');
* This step helps Sitecore Pages find the local instance, butCORS issues must still be resolved separately.
* (B) The browser developer tools console does not support the local storage functionality required for this connection # Incorrect
* Browserdeveloper tools do supportlocal storage.
* If local storage were an issue, developers couldmanually add entriesvia the console.
* Example:
localStorage.getItem('Sitecore.Pages.LocalXmCloudUrl'); // Should return 'https://xmcloud.localhost'
* (C) The value of the local storage entry"Sitecore.PagesXmCloud"should be set to"enabled"# Incorrect
* There isno such required settingnamed"Sitecore.PagesXmCloud".
* The required setting is'Sitecore.Pages.LocalXmCloudUrl', which must be set tothe local instance URLinstead.
* Ensure CORS settings are correctly configured:
* Addhttps://pages.sitecorecloud.ioto theSITECORE_Pages_CORS_Allowed_Origins environment variable.
* Manually set the local Sitecore URL in browser storage:
* Open Developer Tools (F12in Chrome).
* Run:
Best Practices for Connecting Sitecore Pages to a Local XM Cloud InstancelocalStorage.setItem('Sitecore.
Pages.LocalXmCloudUrl', 'https://xmcloud.localhost');
* Verify network requests:
* Check for CORS-related errors in the browserConsole (F12 > Console tab).
* Checkfailed requests in the Network tab.
* Sitecore Pages Integration with Local Development- Troubleshooting Sitecore Pages
* CORS Configuration in XM Cloud- Allowing Origins for Sitecore Pages
References:
NEW QUESTION # 35
Why should a developer assign security to roles instead of users when setting up security on a site?
- A. Security can be managed more efficiently as the rights and permissions apply to a group of users.
- B. Role-based security allows multiple users to have the same username.
- C. Individual users with a role can set and configure their own item security permissions.
- D. Security roles can assign individual rights and permissions to be configured by users.
Answer: A
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.
NEW QUESTION # 36
The XM Cloud Pages editor comes with a set of devices (for example, Desktop Regular and Mobile) with predefined settings. Which of the following fields must a developer specify to add and configure an additional device?
- A. Device width, visibility, responsive breakpoints
- B. Device height, visibility, an icon to represent the device
- C. Device height, visibility, responsive breakpoints
- D. Device width, visibility, an icon to represent the device
Answer: D
Explanation:
When adding and configuring an additional device in the XM Cloud Pages editor, a developer must specify the device width in pixels, the visibility options (Disabled, Fixed, Optional), and an icon to represent the device. These settings are crucial for simulating how content will appear on different devices within the Pages editor.
References:The Sitecore XM Cloud documentation provides detailed instructions on adding and configuring devices in the Pages editor, including specifying the device width, visibility options, and selecting an icon1.
NEW QUESTION # 37
A developer is tasked with creating an item using the Sitecore Authoring and ManagementGraphQL API.
Which of the following GraphQL mutations is the correct way to create a new item?
- A. createOrUpdateltem
- B. create Templateltem
- C. updateltem
- D. createltem
Answer: D
Explanation:
InSitecore XM Cloud, the correct GraphQL mutation to create a new item using theAuthoring and Management GraphQL APIiscreateItem. This mutation allows developers to programmatically create content items within Sitecore while specifying the required parent item, template, and field values.
Correct Mutation Examplemutation {
createItem(
parent: "/sitecore/content/Home",
name: "NewPage",
template: "Sample/Sample Item",
fields: [
{ name: "Title", value: "My New Page" },
{ name: "Text", value: "This is a sample text content." }
]
) {
item {
id
name
path
}
}
}
* parent# The path or ID of the parent item where the new item should be created.
* name# The name of the new item.
* template# The template that defines the structure of the item.
* fields# The array of field values assigned to the new item.
* A.createOrUpdateItem# This mutation does not exist in Sitecore GraphQL API.
* B.createTemplateItem# This is an incorrect name; Sitecore does not provide such a mutation.
* D.updateItem# This mutation is used to update an existing item, not create a new one.
* Sitecore GraphQL API for Authoring and Management
* GraphQL Mutation to Create an Item
* Sitecore XM Cloud Developer Documentation
Explanation of Parameters:Why Other Options Are Incorrect?Relevant XM Cloud Documentation References:
NEW QUESTION # 38
What information can be found in the deployment logs?
- A. Content Management and Content Delivery deployment logs
- B. Provisioning, Deployment, and Publishing information
- C. Content Management instance and Rendering Hosting logs
- D. Provisioning, Build, Deployment, and Post Action information
Answer: 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- 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- the process of compiling the source code, running tests, and generating the deployment package.
Deployment- the process of deploying the package to the environment and applying any configuration changes.
Post Action- the process of performing any additional tasks after the deployment, such as publishing, indexing, or clearing caches.
1:XM Cloud Documentation for Developers - Sitecore
NEW QUESTION # 39
......
Sitecore Sitecore-XM-Cloud-Developer Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
| Topic 4 |
|
Latest 100% Passing Guarantee - Brilliant Sitecore-XM-Cloud-Developer Exam Questions PDF: https://www.itpass4sure.com/Sitecore-XM-Cloud-Developer-practice-exam.html
Sitecore-XM-Cloud-Developer Dumps for Pass Guaranteed - Pass Sitecore-XM-Cloud-Developer Exam: https://drive.google.com/open?id=1xYu6MzBrnoIs4j6kj9d3TMRsVWN4ayzn
