Free Practice Questions for the Sitecore Engagement Cloud Sitecore-10-NET-Developer Exam (2026 Updated)

 The sitecore.json file is the project configuration file that contains several properties, including a modules property that references the relevant Sitecore Content Serialization modules. If the path of a specific module file is not set in the modules property, the SCS system will not be able to locate and access the module file, which contains the items to be serialized. Therefore, the paths and related items included in the module will not be serialized when you run a push or pull command. This can lead to missing or inconsistent data between the Sitecore instance and the file system.  References:

Sitecore Content Serialization structural overview

Create a Sitecore Content Serialization module

Includes are used to configure the serialization of content item trees. You configure includes with a name property that becomes a folder name in your file system and a path property that specifies what part of your content item tree to serialize. For example, to serialize your entire content item tree to the serialization\content\ folder in your file system, add this to your Project.module.json file and run the sitecore ser pull command: “items”: { “includes”: [ { “name”: “content”, “path”: “/sitecore/content/home” } ] }  References:

Sitecore Content Serialization structural overview 1

Sitecore Content Serialization configuration reference

https://doc.sitecore.com/xp/en/developers/100/developer-tools/sitecore-content-serialization-configuration-reference.html

The field helper is a Sitecore MVC helper that renders the content of a field in the view. It also enables the field to be editable in the Experience Editor or Horizon. To prevent a field from being edited, you can set the editable parameter to “false” in the field helper. For example, @Html.Sitecore().Field(“title”, new { editable = false }) will render the title field without the editing capabilities. This parameter overrides the default behavior of the field helper, which is to render the field as editable if the page is in edit mode. Setting the editable parameter to “false” can be useful for fields that are not meant to be changed by the content authors, such as system fields or fields that are populated by code. 

Workflows consist of three elements – states, commands and actions 1 . A workflow state defines the status of an item in a workflow, such as Draft, Awaiting Approval, or Published. A workflow command defines the transition from one state to another, such as Submit, Approve, or Reject. A workflow action defines the operation that is performed when a command is executed, such as sending an email notification, validating an item, or publishing an item. Workflows can contain any number of workflow states and be as simple or complex as required. Items do not necessarily have to move through all the workflow states that you have defined.  Some states can be optional or only applicable to certain kinds of content 1 .  References :

Workflows and the Workbox

This answer is based on the Sitecore documentation of deploying files into running containers 1 . When developing using Sitecore MVC, you may need to modify files in your Visual Studio project that are outside of the webroot folder, such as controllers, models, or views. To see the changes within the Sitecore installation, you need to copy the file to the webroot folder of the Sitecore instance, which is the destination of a volume inside a container. You can use the Visual Studio’s Publish command to do this, as it allows you to specify the target location of the file system.  Alternatively, you can also use the Sitecore Docker Tools extension for Visual Studio, which provides a convenient way to deploy files to the webroot of a running container 2 .  References :

Deploying files into running containers

Sitecore Docker Tools extension for Visual Studio

A Sitecore Support Package is a ZIP file that contains information about the Sitecore instance, such as configuration files, log files, license files, and diagnostic information. It is generated by using a built-in tool in Sitecore that collects and packages the relevant data. The purpose of a Sitecore Support Package is to help Sitecore Support Services to replicate an issue without needing to access the environment directly.  By sending a Sitecore Support Package to Sitecore Support, you can provide them with the necessary information to troubleshoot and resolve your issue faster and more efficiently.  References:   https://support.sitecore.com/kb?id=kb_article_view & sysparm_article=KB0406145

https://support.sitecore.com/kb?id=kb_article_view & sysparm_article=KB0463549

The Experience Editor, the Content Editor, and the Workbox are three areas of Sitecore that allow you to view the available workflow commands of an item you are editing. The workflow commands are the actions that you can perform on an item in a workflow, such as Submit, Approve, Reject, or Publish. The workflow commands are displayed in different ways depending on the area of Sitecore you are using:

In the Experience Editor, the workflow commands are displayed in the Workflow group on the Review tab of the ribbon 1 .

In the Content Editor, the workflow commands are displayed in the Workflow group on the Home tab of the ribbon 2 .

In the Workbox, the workflow commands are displayed as buttons in the workflow state pane for each item 3 .

The Security Editor, the Workflow Command, and the Path Analyzer are not areas of Sitecore that allow you to view the available workflow commands of an item you are editing.  The Security Editor is a tool that allows you to manage access rights for users and roles 4 .  The Workflow Command is a template that defines the properties of a workflow command, such as the name, the next state, and the actions 5 .  The Path Analyzer is a tool that allows you to analyze the paths that visitors take on your website.  References :  1 : https://doc.sitecore.com/xp/en/users/101/sitecore-experience-platform/the-workflow-group.html  2 : https://doc.sitecore.com/xp/en/users/101/sitecore-experience-platform/the-workflow-group-in-the-content-editor.html  3 : https://doc.sitecore.com/xp/en/users/101/sitecore-experience-platform/workflows-and-the-workbox.html  4 : https://doc.sitecore.com/xp/en/developers/101/platform-administration-and-architecture/the-security-editor.html  5 : https://doc.sitecore.com/xp/en/developers/101/sitecore-experience-manager/defining-workflows.html : https://doc.sitecore.com/xp/en/users/101/sitecore-experience-platform/path-analyzer.html

To implement a layout in Sitecore MVC, you need two things: a layout.cshtml file and a layout definition item. The layout.cshtml file is the Razor view that contains the HTML markup and the placeholders for the renderings. The layout definition item is the Sitecore item that references the layout.cshtml file and provides metadata for the layout, such as the name, path, and device. You can create both of these from Sitecore Rocks or from the Content Editor.  References :

MVC and renderings

Add a form to a webpage

This answer is based on the Sitecore documentation of rendering content with MVC 1 . When developing a component using Sitecore MVC, you can use the Field() helper method to render a field from an item. This method returns an HTML string that contains the field value and the necessary markup to make the field editable in Experience Editor. The Field() helper method can be used with the Sitecore HtmlHelper class, which provides extension methods for the ASP.NET MVC HtmlHelper class. For example, you can use the following syntax to render a field named Title from the current context item:

@Html.Sitecore().Field(“Title”)

You can also specify a different item or a rendering parameter to render the field from:

@Html.Sitecore().Field(“Title”, Model.Item) //Datasource item @Html.Sitecore().Field(“Title”, Model.PageItem) //Explicit page item

The Field() helper method supports various field types, such as single-line text, rich text, image, link, and checkbox. It also supports rendering fields with custom parameters, such as width, height, class, or alt. For example, you can use the following syntax to render an image field with a custom width and height:

@Html.Sitecore().Field(“Image”, new { w = 200, h = 100 })

The Field() helper method is the recommended way to render fields in Sitecore MVC, as it ensures that the fields are editable in Experience Editor and that the field values are properly encoded and formatted. However, there are some limitations and considerations when using the Field() helper method, such as:

The Field() helper method does not support rendering fields that are not part of the current item or its base templates. To render such fields, you need to use the FieldRenderer class or the sc:Field control.

The Field() helper method does not support rendering fields that are part of a complex data structure, such as a list or a dictionary. To render such fields, you need to use the sc:List or sc:Dictionary controls.

The Field() helper method does not support rendering fields that are part of a dynamic placeholder. To render such fields, you need to use the sc:DynamicPlaceholder control.

The Field() helper method does not support rendering fields that are part of a rendering variant. To render such fields, you need to use the sc:VariantField control.

References :

Rendering content with MVC

Using the Field helper

Field helper limitations and considerations

Presentation details are the settings that define how and where content will be displayed on a webpage. They include the layout, the renderings, the placeholders, and the datasources for each rendering. Presentation details can be set at different levels in Sitecore, such as standard values, content items, or device items. However, for non-SXA websites, it is recommended to avoid setting presentation details directly on new content items, and instead use standard values. Standard values are the default values for the fields of a template, including the presentation details. By defining presentation details on standard values, you can ensure that all content items created from the same template will have the same presentation details by default. This eliminates the need to set presentation details for each individual content item, which can be time-consuming and error-prone. It also makes it easier to maintain and update the presentation details for a group of content items, as you only need to change the standard values once, and the changes will be inherited by all the content items based on that template. Setting presentation details on standard values also allows content authors to use the Experience Editor to edit the content and presentation of the items, without having to switch to the Content Editor. The Experience Editor is a more user-friendly and intuitive interface for content editing, as it shows the content in the context of the webpage. Therefore, by avoiding setting presentation details directly on new content items, you can improve the efficiency and consistency of your content creation and presentation process.  References:   Sitecore 10.0 Developer Documentation - Presentation details ,  Sitecore 10.0 Developer Documentation - Standard values

The Sitecore Extranet security domain is a website security domain that contains the user accounts that correspond to the visitors to the website.  It also contains the customized roles that manage read access to the content of the website 1 .  The Extranet domain is the default domain for the website and it is used to authenticate users who need to access restricted areas of the website, such as a members-only section 2 . The Extranet domain is not related to the Sitecore identity server, the Sitecore client tools, or the third-party environments.  Therefore, the correct answer is C.  References:   https://doc.sitecore.com/xp/en/developers/82/sitecore-experience-platform/security-domains.html

https://doc.sitecore.com/xp/en/developers/91/platform-administration-and-architecture/sitecore-security.html

 When developing with the Sitecore ASP.NET Core Rendering SDK, you need to register component renderers within the rendering host’s Startup.cs class to map a Sitecore rendering component name to an implementation. This allows the Sitecore Rendering Engine to render the content fetched from the Sitecore Layout Service using the appropriate component renderer. For example, you can map a Sitecore layout component name to a view component rendering or a partial view rendering. You can use the AddViewComponent() and AddPartialView() extension methods to register component renderers in the Startup.cs class.  References :

[Sitecore 10 .NET Developer Certification Study Guide], page 18

Sitecore Documentation: Sitecore Rendering Engine