Sitecore XM Cloud Developer Valid Practice Questions
Sitecore XM Cloud Developer Valid Practice Questions
What's Inside:
Important Note:
For full access to the complete question bank and topic-wise explanations, visit:
CertQuestionsBank.com
FB page: https://www.facebook.com/certquestionsbank
Share some Sitecore XM Cloud Developer exam online questions
below.
1.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.
Answer: 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
4.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. An Organization Admin or Organization Owner must update their role.
B. An Organization Admin or Organization Owner must update their role using the XM Cloud Deploy
app.
C. Only the Organization Owner can update their role in the Sitecore Cloud Portal.
D. Only the Organization Owner can update their role using the XM Cloud Deploy app.
Answer: A
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 organization 1: XM Cloud Documentation for
Developers - Sitecore
5.A developer is working on managing environments within the XM Cloud Deploy app. They have
created a new environment for the project and linked it to a specific repository branch. However, they
realize that they need to change the linked repository branch due to new developments in the project.
Which steps should they follow to achieve this?
A. Delete the current environment and create a new one with the desired repository branch.
B. Unlink the current repository branch and then relink the desired branch to the environment through
the project's "Options" menu.
C. Link the desired branch to the environment directly from the repository settings. The XM Cloud
Deploy app will automatically update the linked branch.
D. Go to the project page, click the environment, choose "Options," and then "Edit environment
details." In the dialog, select the desired branch from the "'Link to branch" drop-down menu and save
the changes.
Answer: D
Explanation:
According to the Sitecore XM Cloud Documentation for Developers1, you can link an environment to
a specific branch of your repository in the XM Cloud Deploy app. This allows you to deploy different
versions of your code to different environments. To change the linked branch for an existing
environment, you need to follow these steps2:
On the navigation pane of the XM Cloud Deploy app, click Projects.
On the Projects page, click the project that contains the environment where you want to change the
linked branch.
On the project page, click the environment where you want to change the linked branch.
On the environment page, click Options, then click Edit environment details.
In the Edit environment details dialog, select the desired branch from the Link to branch drop-down
menu.
Click Save to confirm your changes.
2: Manage an environment in the XM Cloud Deploy app | Sitecore Documentation 1: XM Cloud
Documentation for Developers - Sitecore
6.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
Answer: 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.
7.If a developer wants to limit the serialization of items under a Navigation item to just the item itself
and then one step below, what property should the developer add to the includes to indicate this
limitation?
A. Scope
B. Nothing?this is the default.
C. Limit
D. Name
Answer: A
Explanation:
According to the Sitecore XM Cloud Documentation for Developers1, the scope property is used to
control the depth of the serialization tree. The scope property can have one of the following values2:
Self C only the item itself is serialized, not its descendants.
Children C the item and its immediate children are serialized, not the grandchildren or further
descendants.
Subtree C the item and all its descendants are serialized, regardless of the depth.
To limit the serialization of items under a Navigation item to just the item itself and then one step
below, the developer should add the scope property with the value Children to the includes section of
the serialization configuration file. For example3: includes:
- name: Navigation
path: /sitecore/content/MySite/Navigation
scope: Children
2: The YAML serialization format | Sitecore Documentation 3: The XM Cloud build configuration |
Sitecore Documentation 1: XM Cloud Documentation for Developers - Sitecore
8.To connect Sitecore Pages to your local XM Cloud instance, which steps are involved?
A. Open the local Content Management instance and set the predefined rendering host field value in
Sitecore to https://pages.sitecorecloud.io
B. Open Pages and create an entry in Local Storage for the key "Sitecore.Pages.LocaIXmCloudUrl"
with the following value: https://xmcloudcm. localhost
C. Open Pages and create an entry in Local Storage for the key "Sitecore.Pages.LocaIXmCloudUrl"
with the following value: https://pages.sitecorecloud.io
D. Open the local Content Management instance and set the predefined rendering host field value in
Sitecore to https://xmcloudcm.localhost
Answer: B
Explanation:
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