Sitecore-XM-Cloud-Developer Exam Practice Test Instant Access

Question 1

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?

ADelete the current environment and create a new one with the desired repository branch.

BUnlink the current repository branch and then relink the desired branch to the environment through the project's 'Options' menu.

CLink the desired branch to the environment directly from the repository settings. The XM Cloud Deploy app will automatically update the linked branch.

DGo 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

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

Question 2

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.

ACalculating additional entities to publish

BCalculating dependencies

CArchiving expired content

DResolving dependencies

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.

Question 3

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?

AEnable the correct placeholder settings of the components to be modified to include the page template used for the content item users are editing.

BInclude a placeholder as part of the layout markup and create a corresponding placeholder settings item with the appropriate allowed components.

CSet the standard values for the page template to include component modification options and make sure the template used by the page inherits appropriately.

DEnable the insert options of the components to be included forthe page template and set the appropriate allowed components.

Answer : B

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 as my-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.

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

Question 4

Which of the following must be done to delete or remove a user from an administrator role?

ADelete the user or remove their administrator role from the Sitecore Cloud Portal.

BCreate a new user account and assign a new role from the XM Cloud Deploy app.

CDelete the user or remove their administrator role from the XM Cloud Deploy app.

DCreate a new user account and assign a new role from the Sitecore Cloud Portal.

Answer : A

According to the Sitecore XM Cloud Documentation for Developers1, the Sitecore Cloud Portal is where you can manage access to your DXP products, create users and manage their access to all your Sitecore DXP products. To delete or remove a user from an administrator role, you need to follow these steps2:

In the left navigation pane, click Users.

In the Users list, find the user you want to delete or remove from the administrator role and click the Edit icon.

In the Edit user dialog box, you can either delete the user by clicking the Delete user button or remove the administrator role by deselecting the Administrator checkbox.

Click Save to confirm your changes.

1: XM Cloud Documentation for Developers - Sitecore 2: Manage users in the Sitecore Cloud Portal - Sitecore

Question 5

A build to XM Cloud fails. Which options are available for a developer to diagnose the error?

AThe Deploy app system status page

BThe Content Management instance logs for the environment

CThe project details page in the Deploy app

DThe deployment log files for the environment

Answer : D

According to the Sitecore XM Cloud Documentation for Developers1, the deployment log files contain the progress, status, warnings, and errors of an XM Cloud deployment. You can access the deployment log files from the XM Cloud Deploy app by clicking the Logs button on the environment page. The log files include information about the provisioning, build, deployment, and post action phases of the deployment. You can also download the log files for offline analysis or troubleshooting2.

The other options are not as useful for diagnosing a build failure:

The Deploy app system status page shows the overall health and availability of the XM Cloud Deploy app, not the status of individual deployments3.

The Content Management instance logs for the environment show the runtime logs of the Content Management instance, not the build logs of the deployment4.

The project details page in the Deploy app shows the general information and settings of the project, not the details of the deployment1.

2: View the deployment log files | Sitecore Documentation 3: Check the system status of the XM Cloud Deploy app | Sitecore Documentation 4: Access the Content Management instance logs | Sitecore Documentation 1: Manage a project in the XM Cloud Deploy app | Sitecore Documentation

Question 6

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?

AThe value of the local storage entry ''Sitecore.Pages.LocaIXmCloudUrl' should be set to https://pages.sitecorecloud.io.

BThe browser developer tools console does not support the local storage functionality required for this connection.

CThe value of the local storage entry 'Sitecore.PagesXmCloud' should be setto enabled.

DThe environment variable 'SITECORE_Pages_CORS_Allowed_Origins' is not correctly configured to include pages.sitecorecloud.io.

Answer : D

Question 7

When deploying to XM Cloud, how are Sitecore Content Serialization (SCS) serialized items created in the Content Management (CM) instance?

AThe XM Cloud deploy process uses the SCS CLI to do a push once the CM instance is active.

BTheXM Cloud deploy process creates an Items as Resources (IAR) file and layers this into the CM instance.

CA build pipeline must be created to use the SCS CLI push commands to push content after the XM Cloud Deploy app finishes.

DThe XM Cloud deploy process uses serialized item batches through REST APIs at the XM Cloud CM to speed up serialization.

Answer : D

The Sitecore Content Serialization (SCS) system serializes content items in and out of a Sitecore instance using YAML files1. When deploying to XM Cloud, the XM Cloud deploy process uses serialized item batches through REST APIs at the XM Cloud CM to speed up serialization2. This way, you can serialize large amounts of content items without affecting the performance of the Content Management (CM) instance2.

Sitecore Content Serialization structural overview

Sitecore Content Serialization in XM Cloud

Sitecore XM Cloud Developer Certification Sitecore-XM-Cloud-Developer Exam Practice Test