Pass the Sitecore Sitecore Engagement Cloud Sitecore-10-NET-Developer Questions and answers with CertsForce

When using Sitecore MVC, the static class that contains information about any current HTTP request is Sitecore.HttpContext. This class is a wrapper for the System.Web.HttpContext class, which provides access to the intrinsic objects of ASP.NET, such as Request, Response, Session, and Server. Sitecore.HttpContext also exposes some Sitecore-specific properties, such as Database, Device, Domain, and Site. Sitecore.HttpContext is different from Sitecore.Context, which is another static class that provides information about the current Sitecore context, such as Item, User, Language, and ContentDatabase. Sitecore.Request and Sitecore.HttpContext.Request are not valid classes in Sitecore MVC. References:

Sitecore.HttpContext Class - Sitecore

Sitecore.Context Class - Sitecore

HttpContext Class - Microsoft

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

A multilist field allows a user to select multiple values from a list of items. The list of items is determined by the source property of the field, which can be set to a root item, a Sitecore query, or a treelist parameter. The source property controls the items that appear in the selection list for the field. Therefore, setting the field source for the multilist field is the next step after creating the field as a multilist type. References:

Multilist - SDN

Controlling the list of items in a Selection field - Sitecore

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, toserialize 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 overview1

Sitecore Content Serialization configuration reference

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

Standard values on data templates are used to define default field values, default settings, and insert options for a data template1. They appear in the content tree as a child item of the data template called __Standard Values1. When a new item is created from the template, it inherits the standard values for its fields. If the value of a field is NULL, the item contains the standard value for that field as defined in the data template2. This way, standard values provide the default values for fields when a new item is created from the template and a fallback value when fields are left NULL2. References:

Configure standard values | Sitecore Documentation

Standard values | Sitecore Documentation

According to Sitecore best practices, presentation details should be set on the standard values of the template that defines the item. This way, all items that are based on the same template will inherit the same presentation details, unless they are explicitly overridden. Setting presentation details on the standard values also allows resetting modified item presentation settings to default values. Setting presentation details on the individual items is not recommended, as it increases the maintenance cost and complexity of the presentation layer. Rendering parameters are used to control how renderings function, not to designate layouts. Standard template is a base template that all templates inherit from, and it does not have any presentation details. References:

Presentation Component Reference - Sitecore

Sitecore Presentation Layer Best Practices - Sitecore Developer Blog

Workflows consist of three elements – states, commands and actions1. 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 content1. References:

Workflows and the Workbox

Insert options are a way of controlling the types of items that users can create under existing items. By default, insert options are inherited from the standard values of the data template of the parent item. However, sometimes it may be necessary to override the insert options for a specific item, for example, to allow more flexibility or to enforce a certain structure. In that case, setting the insert options on the specific item will add those options to the list of effective insert options, along with the ones inherited from the standard values. This way, Content Authors can insert items under the specific item in addition to what is included with the item’s standard values. Note that setting the insert options on the specific item will not replace the inherited ones, unless the insert options are empty, in which case the effective insert options will be empty as well. References:

Insert options

Assign or copy insert options

Assign standard insert options

 If the Sitecore Content Management instance can be accessed by multiple host names, you need to add AllowedCorsOriginsGroup for each site to the Identity Server configuration. This will enable the users for each site to be able to log in to the Sitecore shell using the Identity Server. The AllowedCorsOriginsGroup element defines a group of URIs that are allowed to make cross-origin requests to the Identity Server. You can use multiple subnodes to define more than one URI, or you can use the | symbol to separate URIs within a node. You can also use the {AllowedCorsOrigin} template to simplify the configuration. When you use that template, all origins (hosts) are notified about the sign-out1. References:

Single sign-out

 When creating your containerized Sitecore environment with Docker, you need two files to launch the containers: docker-compose.yml and .env. The docker-compose.yml file contains the configuration of the services that make up the Sitecore environment, such as the roles, networks, volumes, and dependencies. The .env file contains the environment variables that are used by the docker-compose.yml file, such as the Sitecore license path, the image tags, the host names, and the passwords. These files are recommended because they simplify the process of launching the containers and allow you to customize the environment according to your needs. References:

Sitecore Containers documentation

Docker Compose file reference

[Environment variables in Compose]