Question #1
A developer is working with Sitecore’s Authoring and Management API to manage their Sitecore content using GraphQL. They want to explore and interact with the API using the GraphQL integrated development environment (IDE).
Which of the following statements is correct about using the GraphQL IDE?
- A . A developer needs to be in the sitecoreAdmin role to access the GraphQL IDE.
- B . A developer needs to be in the sitecoreSitecore Client Users role to access the GraphQL IDE.
- C . The GraphQL IDE provides read-only access to the API.
- D . The GraphQL IDE is only available for non-production environments to ensure secure interactions.
Correct Answer: B
B
Explanation:
Access to the GraphQL IDE for exploring and managing Sitecore content via the Authoring and Management API requires a developer to have the sitecoreSitecore Client Users role. This role grants the necessary permissions to use the IDE for various operations, not just read-only access.
Reference: The Sitecore XM Cloud documentation specifies the role requirements for using the GraphQL IDE1. It also provides guidance on setting up and authoring content with the GraphQL playgrounds, which are part of the IDE2.
B
Explanation:
Access to the GraphQL IDE for exploring and managing Sitecore content via the Authoring and Management API requires a developer to have the sitecoreSitecore Client Users role. This role grants the necessary permissions to use the IDE for various operations, not just read-only access.
Reference: The Sitecore XM Cloud documentation specifies the role requirements for using the GraphQL IDE1. It also provides guidance on setting up and authoring content with the GraphQL playgrounds, which are part of the IDE2.
Question #2
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 #3
A developer wants to create a webhook that sends an HTTP request to a specified endpoint when the workflow moves to the approved state.
What type of webhook should they use?
- A . Submit handler
- B . Event handler
- C . Submit action
- D . Validation action
Correct Answer: C
C
Explanation:
In Sitecore XM Cloud, a webhook submit action is used to send an HTTP request to a specified endpoint when an item changes workflow state or a workflow command runs. Therefore, for a developer wanting to create a webhook that triggers when the workflow moves to the approved state, a webhook submit action would be the appropriate choice.
Reference: This information is confirmed by the Sitecore XM Cloud documentation, which details the different types of webhooks available and their specific uses, including the webhook submit action for workflow state changes1.
C
Explanation:
In Sitecore XM Cloud, a webhook submit action is used to send an HTTP request to a specified endpoint when an item changes workflow state or a workflow command runs. Therefore, for a developer wanting to create a webhook that triggers when the workflow moves to the approved state, a webhook submit action would be the appropriate choice.
Reference: This information is confirmed by the Sitecore XM Cloud documentation, which details the different types of webhooks available and their specific uses, including the webhook submit action for workflow state changes1.
Question #4
When an item is published, the Experience Edge for XM Connector publishes a static snapshot of the Layout Service output of that item.
If a change is made to a data source item that is referenced on the page, how is that content made visible on the website?
- A . A developer must publish the data source item.
- B . A developer must publish the related page items.
- C . A developer must publish to the web database.
- D . A developer must reconnect to the Experience Edge Connector module.
Correct Answer: A
A
Explanation:
When a change is made to a data source item in Sitecore XM Cloud, the updated content becomes visible on the website after the data source item itself is published. This is because the Experience Edge for XM Connector publishes a static snapshot of the Layout Service output, and any changes to the data source items require republishing to reflect on the website.
Reference: The Sitecore XM Cloud documentation explains that the Experience Edge for XM Connector uses a static publishing model, meaning that dynamic content structures are flattened at publishing time. Therefore, if a data source item changes, it must be republished for the changes to take effect on the website12.
A
Explanation:
When a change is made to a data source item in Sitecore XM Cloud, the updated content becomes visible on the website after the data source item itself is published. This is because the Experience Edge for XM Connector publishes a static snapshot of the Layout Service output, and any changes to the data source items require republishing to reflect on the website.
Reference: The Sitecore XM Cloud documentation explains that the Experience Edge for XM Connector uses a static publishing model, meaning that dynamic content structures are flattened at publishing time. Therefore, if a data source item changes, it must be republished for the changes to take effect on the website12.
Question #5
Which of these options best describes the purpose of the following query to the Experience Edge GraphQL schema?
query {
layout(site: "experienceedge", routePath: "/", language: "en") {
item {
homeltemPath: path
contentRoot: parent {
id
path
}
}
}
}
- A . To get an item by ID
- B . To get the root item of a site
- C . To get the item layout for a URL
- D . To get information about a specific content site
Correct Answer: C
C
Explanation:
The query to the Experience Edge GraphQL schema is designed to retrieve the layout information for a specific URL, which in this case is the root path (“/”) of a site named “experienceedge”. This allows developers to access the Layout Service JSON for the item, which is essential for rendering the page in a headless setup.
Reference: The Sitecore XM Cloud documentation describes the Experience Edge schema as a read-only GraphQL schema that supports common front-end use cases for headless Sitecore development, including querying an item’s layout by site and route path1.
C
Explanation:
The query to the Experience Edge GraphQL schema is designed to retrieve the layout information for a specific URL, which in this case is the root path (“/”) of a site named “experienceedge”. This allows developers to access the Layout Service JSON for the item, which is essential for rendering the page in a headless setup.
Reference: The Sitecore XM Cloud documentation describes the Experience Edge schema as a read-only GraphQL schema that supports common front-end use cases for headless Sitecore development, including querying an item’s layout by site and route path1.
Question #6
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 . A template has not been established for the Content Editor.
- B . A layout has not been assigned for the content tree in the Content Editor.
- C . The Layouts and Templates folders need to be created by a developer.
- D . The "Hidden items" check box has been unselected on the View tab of the ribbon.
Correct Answer: D
D
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.
Reference: 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.
D
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.
Reference: 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.
Question #7
Which of the following is part of the out-of-the-box technology stack for XM Cloud?
- A . jQuery
- B . Python
- C . Svelte Kit
- D . React
Correct Answer: D
D
Explanation:
XM Cloud includes a modern technology stack that supports various frameworks and libraries for development. React is part of this stack, as it is commonly used in conjunction with Sitecore’s headless services and JSS (JavaScript Services) for building dynamic user interfaces.
Reference: The Sitecore XM Cloud documentation mentions the use of modern frameworks and libraries, including React, as part of its technology stack1. This aligns with the industry’s move towards more flexible and modular front-end development practices.
D
Explanation:
XM Cloud includes a modern technology stack that supports various frameworks and libraries for development. React is part of this stack, as it is commonly used in conjunction with Sitecore’s headless services and JSS (JavaScript Services) for building dynamic user interfaces.
Reference: The Sitecore XM Cloud documentation mentions the use of modern frameworks and libraries, including React, as part of its technology stack1. This aligns with the industry’s move towards more flexible and modular front-end development practices.
Question #8
A multinational clothing company wants to create a structured online presence for its various brands and countries. They want to ensure that the different brands and countries have their own dedicated content within the same Sitecore instance.
Which approach should they take to achieve this using XM Cloud’s content architecture?
- A . Use separate instances of XM Cloud for each brand and country to maintain separation.
- B . Create a single site collection and site for all brands and countries and also manage their resources manually.
- C . Create individual site collections for each brand and a site for each country.
- D . Create a separate site for each brand and use a language per country.
Correct Answer: C
C
Explanation:
XM Cloud’s content architecture supports the creation of individual site collections for each brand, with separate sites for each country. This approach allows a multinational company to maintain a structured online presence, ensuring dedicated content for different brands and countries within the same Sitecore instance.
Reference: The Sitecore XM Cloud documentation outlines the ability to create headless site collections and sites, supporting multiple brands for a single company or multiple languages or
locations for a single brand1. This is part of the SXA content architecture, which includes site collections and sites, allowing for multiple sites on a single instance of Sitecore1.
C
Explanation:
XM Cloud’s content architecture supports the creation of individual site collections for each brand, with separate sites for each country. This approach allows a multinational company to maintain a structured online presence, ensuring dedicated content for different brands and countries within the same Sitecore instance.
Reference: The Sitecore XM Cloud documentation outlines the ability to create headless site collections and sites, supporting multiple brands for a single company or multiple languages or
locations for a single brand1. This is part of the SXA content architecture, which includes site collections and sites, allowing for multiple sites on a single instance of Sitecore1.
Question #9
A developer needs to remove a site collection folder.
Which script should they run from the Content Editor?
- A . Remove Site Collection
- B . Remove Folder
- C . Remove Site Folder
- D . Remove Site Collection Folder
Correct Answer: D
D
Explanation:
To remove a site collection folder in Sitecore XM Cloud, the developer should run the “Remove Site Collection Folder” script from the Content Editor. This script is specifically designed to remove site collection folders and all associated items, ensuring a clean removal process.
Reference: The Sitecore XM Cloud documentation provides instructions on how to remove site collections, site collection folders, sites, and site folders using scripts available in the Content Editor1.
D
Explanation:
To remove a site collection folder in Sitecore XM Cloud, the developer should run the “Remove Site Collection Folder” script from the Content Editor. This script is specifically designed to remove site collection folders and all associated items, ensuring a clean removal process.
Reference: The Sitecore XM Cloud documentation provides instructions on how to remove site collections, site collection folders, sites, and site folders using scripts available in the Content Editor1.
Question #10
When a developer deploys to XM Cloud, which resources are included in the provisioning step?
- A . Content Management instance, Editing Host, and Experience Edge
- B . Content Management instance and Experience Edge
- C . Content Management instance and Vercel application
- D . Content Management instance and Content Delivery instance
Correct Answer: A
A
Explanation:
During the provisioning step of a deployment to XM Cloud, the resources that are included are the Content Management instance, Editing Host, and Experience Edge. These components are essential for managing content, providing an editing interface, and delivering content to end-users, respectively.
Reference: The Sitecore XM Cloud documentation details the deployment process and the resources that are provisioned during deployment, which includes the Content Management instance, Editing Host, and Experience Edge1.
A
Explanation:
During the provisioning step of a deployment to XM Cloud, the resources that are included are the Content Management instance, Editing Host, and Experience Edge. These components are essential for managing content, providing an editing interface, and delivering content to end-users, respectively.
Reference: The Sitecore XM Cloud documentation details the deployment process and the resources that are provisioned during deployment, which includes the Content Management instance, Editing Host, and Experience Edge1.
Question #11
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 #12
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 height, visibility, an icon to represent the device
- B . Device height, visibility, responsive breakpoints
- C . Device width, visibility, an icon to represent the device
- D . Device width, visibility, responsive breakpoints
Correct Answer: C
C
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.
Reference: 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.
C
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.
Reference: 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.
Question #13
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 #14
How can a developer differentiate between XM Cloud Components and Headless SXA Components?
- A . XM Cloud Components offer drag-and-drop construction of pages. Headless SXA Components require manual coding and can only be added to a page by a developer.
- B . XM Cloud Components are a low/no code builder for creating components that can consume data from multiple data sources. Headless SXA components require code that consumes data from the same data sources.
- C . In XM Cloud Components, the Styles library ensures visual consistency across components. Headless SXA Components emphasize dynamic content mapping.
- D . XM Cloud Components provide responsive designs for different device types. Headless SXA Components are exclusively focused on static layouts.
Correct Answer: B
B
Explanation:
XM Cloud Components provide a low-code or no-code solution for building components, allowing for the consumption of data from various sources without extensive coding. On the other hand, Headless SXA Components are designed for developers to code and consume data, typically from the same data sources, offering a more hands-on approach to component creation.
Reference: The distinction between XM Cloud Components and Headless SXA Components is outlined in the Sitecore XM Cloud documentation, which describes the capabilities and intended use cases for each type of component12.
B
Explanation:
XM Cloud Components provide a low-code or no-code solution for building components, allowing for the consumption of data from various sources without extensive coding. On the other hand, Headless SXA Components are designed for developers to code and consume data, typically from the same data sources, offering a more hands-on approach to component creation.
Reference: The distinction between XM Cloud Components and Headless SXA Components is outlined in the Sitecore XM Cloud documentation, which describes the capabilities and intended use cases for each type of component12.
Question #15
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?
- A . The changes break the layout of the site.
- B . The Grid Setup item and its dependencies were automatically updated.
- C . A new custom theme with a grid definition item was created.
- D . The new grid was automatically added as one of the grid options.
Correct Answer: A
A
Explanation:
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.
Reference: The Sitecore XM Cloud documentation provides insights into the implications of changing the grid system, emphasizing the need for manual updates to avoid breaking the site layout1.
A
Explanation:
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.
Reference: The Sitecore XM Cloud documentation provides insights into the implications of changing the grid system, emphasizing the need for manual updates to avoid breaking the site layout1.
Question #16
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 . Include the IDynamicPlaceholder base template in the Rendering Parameters template.
- B . Link the placeholder settings item to the rendering item.
- C . Define the placeholder key using a question mark (?) in the placeholder settings item.
- D . In the component TSX file, set a unique placeholder key value that has not yet been defined.
Correct Answer: A, B, C
A, B, C
Explanation:
To configure a rendering for the use of dynamic placeholders in Sitecore XM Cloud, the following steps are required:
Include the IDynamicPlaceholder base template in the Rendering Parameters template to enable dynamic assignment of IDs to the placeholder key.
Link the placeholder settings item to the rendering item to ensure that the dynamic placeholders are correctly associated with the rendering.
Define the placeholder key using a wildcard in the placeholder settings item, which allows for the generation of unique placeholder keys for every component on the page.
Reference: 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 the IsRenderingsWithDynamicPlaceholders property to the component item, including the IDynamicPlaceholder base template in the Rendering Parameters template, defining the placeholder key using a wildcard, and linking the placeholder settings item to the component1.
A, B, C
Explanation:
To configure a rendering for the use of dynamic placeholders in Sitecore XM Cloud, the following steps are required:
Include the IDynamicPlaceholder base template in the Rendering Parameters template to enable dynamic assignment of IDs to the placeholder key.
Link the placeholder settings item to the rendering item to ensure that the dynamic placeholders are correctly associated with the rendering.
Define the placeholder key using a wildcard in the placeholder settings item, which allows for the generation of unique placeholder keys for every component on the page.
Reference: 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 the IsRenderingsWithDynamicPlaceholders property to the component item, including the IDynamicPlaceholder base template in the Rendering Parameters template, defining the placeholder key using a wildcard, and linking the placeholder settings item to the component1.
Question #17
A developer creates templates and adds standard values; items created from the templates should automatically have the Title field populated with the name of the item.
What should they do to ensure this occurs?
- A . Set $name token in the new item’s content Title field.
- B . Add sname token to the template’s standard values Title field.
- C . Set_name token in the new item’s content Title field.
- D . Add_name token to the template’s standard values Title field.
Correct Answer: A
A
Explanation:
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 $name token 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.
Reference: The use of the $name token in standard values is supported by Sitecore and is documented in their developer resources. It is specifically mentioned that Sitecore replaces the $name token with the item’s name during creation1.
A
Explanation:
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 $name token 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.
Reference: The use of the $name token in standard values is supported by Sitecore and is documented in their developer resources. It is specifically mentioned that Sitecore replaces the $name token with the item’s name during creation1.
Question #18
A developer creates a new data template for a page.
How do they ensure that the new template is available through Experience Edge?
- A . Create the template in the configured locations for Experience Edge (Feature, Foundation, Project, User Defined).
- B . Add the parent path of the template to the Experience Edge config using a patch file.
- C . Use the Experience Edge Admin API to add the template to the schema.
- D . Create the template anywhere in the /sitecore/templates folder.
Correct Answer: A
A
Explanation:
To ensure that a new data template is available through Experience Edge, it must be created in the configured locations that are recognized by the Experience Edge schema. These locations are typically structured under Feature, Foundation, Project, and User Defined paths within the Sitecore templates directory.
Reference: The Experience Edge schema documentation specifies that GraphQL types are generated only for templates under the configured paths for Feature, Foundation, Project, and User Defined, which aligns with the Helix content structure principles1.
A
Explanation:
To ensure that a new data template is available through Experience Edge, it must be created in the configured locations that are recognized by the Experience Edge schema. These locations are typically structured under Feature, Foundation, Project, and User Defined paths within the Sitecore templates directory.
Reference: The Experience Edge schema documentation specifies that GraphQL types are generated only for templates under the configured paths for Feature, Foundation, Project, and User Defined, which aligns with the Helix content structure principles1.
Question #19
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 #20
When a developer designates a Sitecore template field multilist type, what should they do next?
- A . Add standard values to the item.
- B . Add the list items to the multilist item.
- C . Set the multilist list item’s data source.
- D . Add a multilist field to the template.
Correct Answer: C
C
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.
Reference: 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.
C
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.
Reference: 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.