When a developer designates a Sitecore template field multilist type, what should they do next?
Answer : C
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.
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?
Answer : D
What is the sitecore.json file in a development solution?
Answer : C
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.
Setup Sitecore Content Serialization
Sitecore Content Serialization structural overview
Which of the following statements accurately describes the purpose of Headless variants in Sitecore XM Cloud?
Answer : A
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
To connect Sitecore Pages to your local XM Cloud instance, which steps are involved?
Answer : B
According to the Sitecore XM Cloud Documentation for Developers1, after setting up your local XM Cloud development environment, Sitecore Pages is not connected to your locally running XM Cloud instance. You can connect your local XM Cloud application to Sitecore Pages by setting a local storage key in your browser. This allows you to use Sitecore Pages to edit content and layouts on your local front-end application. To connect Sitecore Pages to your local XM Cloud instance, you need to follow these steps2:
In your browser, navigate to the Sitecore Pages application.
Open the developer tools console of your browser and find the local storage section. The location differs between browsers:
For Chrome and Edge, open the Application panel. In the Storage section, expand the Local Storage section.
For Firefox, open the Storage panel, and expand the Local Storage section.
In the Local Storage panel, click the entry for Sitecore Pages 9 to reveal the local storage entries.
Create a new entry by adding a new row with the following values:
Key: Sitecore.Pages.LocalXmCloudUrl.
Value: the URL of your local XM Cloud instance. For example, 10.
Refresh the 9 page to see your local front-end application.
2: Connect Sitecore Pages to your local XM Cloud instance 1: XM Cloud Documentation for Developers - Sitecore
A developer changed the CSS grid system after a site was created. Which of the following can happen due to references to the previous grid system?
Answer : A
Changing the CSS grid system after a site has been created can lead to broken layouts due to references to the previous grid system. This is because grid systems have specific rules, classes, and options that are not automatically updated or compatible with the new system, requiring manual changes to ensure the layout functions correctly.
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.
Answer : A, B, D
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.