Pass the Sitecore Sitecore Content Cloud Sitecore-XM-Cloud-Developer Questions and answers with CertsForce

SitecoreExperience Edgeis a headless content delivery service that exposes content via GraphQL. For a newly created data template to be available inExperience Edge, it must be explicitly included in theGraphQL content schemaconfiguration. This is done by modifying the Sitecore configuration using apatch fileto include the parent path of the template.

Locate the Parent Path of the Template

The template must be within a content structure that is included in Experience Edge publishing.

Modify the Experience Edge Configuration Using a Patch File

Create a configuration patch file (e.g.,include.ExperienceEdge.config) toadd the template’s parent pathunder thecontentsection.

Example patch file:

Steps to Ensure the Template is Available in Experience Edge:

This ensures thatcontent based on the new template is published to Experience Edge.

Publish the Configuration Changes and Content

Ensure thetemplate and itemsare published.

The updated schema should be reflected in theGraphQL endpointof Experience Edge.

Why are the Other Options Incorrect?❌A. Create the template in the configured locations for Experience Edge (Feature, Foundation, Project, User Defined).

While placing templates in the correctHelix architecture layers(Feature, Foundation, Project) is a best practice, it does not automatically make them available in Experience Edge.

❌C. Use the Experience Edge Admin API to add the template to the schema.

TheAdmin API does not control content schema inclusion. Experience Edge follows Sitecore publishing rules, and templates must be included via theconfiguration patch file.

❌D. Create the template anywhere in the /sitecore/templates folder.

Simplycreating a template does not make it available in Experience Edge. It must be explicitly added to theExperience Edge content schema configuration.

Sitecore Experience Edge Configuration– Configuring Content in Experience Edge

Sitecore GraphQL Content Schema Setup– GraphQL Content Schema

Using Sitecore Patch Files– Sitecore Configuration Patching

References for Further Learning:

In Sitecore XM Cloud, to automatically populate the Title field of items created from a template with the name of the item, the developer should set the$nametoken in the Title field of the template’s standard values. This token is replaced with the actual item name when the item is created, ensuring that the Title field is automatically filled with the correct name.

References:The use of the$nametoken in standard values is supported by Sitecore and is documented in their developer resources.It is specifically mentioned that Sitecore replaces the$nametoken with the item’s name during creation1.

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 Documentation1:XM Cloud Documentation for Developers - Sitecore

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:

Dynamic placeholders inSitecore XM Cloud with Next.jsare used when a rendering can have multiple instances on a page, each needing auniqueplaceholder name to avoid conflicts.

To configure a rendering withdynamic placeholders, the following steps are required:

(A) Include theIDynamicPlaceholderbase template in the Rendering Parameters template

Sitecore provides theIDynamicPlaceholderbase template to enable dynamic placeholders.

When definingRendering Parameters, this template must beincludedto allow dynamic placeholder configuration.

This ensures Sitecore recognizes the placeholders as dynamic rather than static.

(B) Link the placeholder settings item to the rendering item

In Sitecore,placeholder settingsdefine the allowed components for a placeholder.

The rendering item should reference aPlaceholder Settings item, ensuring that only the allowed components can be added dynamically.

This step is crucial to avoid runtime issues when rendering dynamic placeholders.

(C) Define the placeholder key using a question mark (?) in the placeholder settings item → Incorrect

Placeholder settingsdo notuse a question mark (?) to define a dynamic placeholder key.

The?syntax was used in older Sitecore versions for dynamic placeholders, but inXM Cloud with Next.js, placeholders are handled differently usingGUID-based namingfor uniqueness.

(D) In the component TSX file, set a unique placeholder key value that has not yet been defined → Incorrect

Next.jsdoes not requiremanually setting a unique key.

Instead, Sitecoreautomatically generatesa unique key for each dynamic placeholder instance usingGUID-based naming.

In aNext.js JSS component, placeholders are defined using:

✅Correct Answers:❌Incorrect Answers:How Dynamic Placeholders Work in XM Cloud with Next.js:import { Placeholder } from '@sitecore-jss/sitecore-jss-nextjs';

const DynamicComponent = ({ rendering }) => {

return (

);

};

export default DynamicComponent;

The{rendering.uid}ensures each placeholder instance has aunique name, avoiding conflicts.

Sitecore XM Cloud Dynamic Placeholders– Using Dynamic Placeholders

Next.js with Sitecore JSS– Placeholder Configuration

Sitecore Headless Development– Best Practices for Rendering Placeholders

References:1.