Sitecore-10-NET-Developer Questions and Answers

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

 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

Field sections are logical groupings of fields that help to organize the fields within a template. Field sections can be added to a template by using the Insert Section option in the ribbon. Field sections have a name and an icon that can be customized. Field sections are useful for grouping related fields with templates and the resulting items, as they make the fields easier to find and edit in the Content Editor and the Experience Editor. Field sections also allow you to control the access rights and validation rules for a group of fields, rather than setting them individually for each field. Field sections can be inherited from base templates, and can also be shared across multiple templates by using the Insert Shared Section option. Field sections do not affect the presentation or rendering of the fields, as they are only used for data structure and organization purposes. References: Sitecore 10.0 Developer Documentation - Field sections

Templates are the basic building blocks of Sitecore. They define the data structures that you use to create items and content in Sitecore. Templates consist of sections and fields that specify the type and format of the data that can be stored in an item. Templates also define the standard values, presentation details, and inheritance relationships of items. Templates allow you to create consistent and reusable data structures that can be applied to multiple items and content types. References: Sitecore 10.0 Developer Documentation - Templates

This answer is based on the Sitecore documentation of deploying files into running containers1. 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 container2. References:

• Deploying files into running containers
• Sitecore Docker Tools extension for Visual Studio

Image is considered a complex field in Sitecore MVC because it requires additional parameters and logic to render properly, such as the image source, width, height, alt text, and so on. The Html.Sitecore().Field() method is designed for simple fields that only need the field name and value to render. For complex fields, you should use the Html.Sitecore().Rendering() method instead, which allows you to specify the rendering parameters and the rendering item for the field. Alternatively, you can use the Sitecore MVC helpers, such as @Html.Sitecore().Image(), to render complex fields with more control and flexibility. References:

• [Sitecore 10 .NET Developer Certification Study Guide], page 17
• [Sitecore Documentation: Rendering complex fields]

 Developing with the Sitecore ASP.NET Core Rendering SDK has the following benefits:

• It allows you to create independent applications that render Sitecore content. This means you can use any .NET Core framework or library to build your rendering host, and you do not need to install Sitecore on your development machine1.
• It helps you build small, lightweight .NET Core applications for Sitecore. These applications can run on any platform that supports .NET Core, such as Windows, Linux, or MacOS1.
• It depends on the Sitecore Layout Service. The Layout Service is a RESTful API that provides JSON data for Sitecore items and layouts. The ASP.NET Core Rendering SDK uses the Layout Service to fetch the data and metadata required to render Sitecore content12.
• It enables you to preview your code changes without having to restart the Sitecore environment. The ASP.NET Core Rendering SDK supports hot module replacement (HMR), which means you can see the changes you make to your code in the browser without refreshing the page or rebuilding the application13.

The following statements are not true about developing with the Sitecore ASP.NET Core Rendering SDK:

• It does not enable the Content Delivery instance to handle all of the development workload. The Content Delivery instance is still responsible for serving the Layout Service requests, but the rendering logic is handled by the ASP.NET Core application1.
• It does not allow you to remove ASP.NET from your solution. You still need ASP.NET to run the Sitecore Content Management and Content Delivery instances. The ASP.NET Core Rendering SDK only replaces the ASP.NET rendering engine for your rendering host1.
• It does not allow you to extend Sitecore pipelines using .NET Core. The Sitecore pipelines are part of the Sitecore configuration and run on the Sitecore server. The ASP.NET Core Rendering SDK does not have access to the Sitecore pipelines or the Sitecore context14.

References: 1: Sitecore ASP.NET Rendering SDK | Sitecore Documentation 2: Sitecore Layout Service | Sitecore Documentation 3: Headless development with the ASP.NET Rendering SDK | Sitecore Documentation 4: ASP.NET Core Rendering Engine | Sitecore Documentation

 In a non-SXA multisite implementation, the recommended practice for storing reusable content that is shared between the different sites is to store this type of content outside of any one site’s content tree structure1. This way, you can avoid duplication of content and maintain consistency across the sites. You can also use selection data templates to reuse an item at multiple locations in the content tree, and to share items between multiple managed websites2. The other options are incorrect because:

• Cloning is a feature that allows you to create a copy of an item that inherits the field values and presentation details from the original item3. However, cloning is not recommended for storing reusable content that is shared between the different sites, because it creates a dependency between the cloned item and the source item, and it can cause performance issues if there are too many clones4.
• Sharing content between sites is a common and recommended practice, especially if the content is relevant and consistent for the different audiences and purposes of the sites5.
• Location does matter because content can be retrieved from anywhere, but it is better to store the content in a logical and organized way that reflects the site structure and hierarchy6. References:

https://doc.sitecore.com/xp/en/legacy-docs/SC70/reusing-and-sharing-data-sc70-a4.pdf

https://doc.sitecore.com/xmc/en/developers/xm-cloud/manage-multiple-sites-with-the-sxa-site-manager.html

The $name token is a special token that can be used in fields on standard values items to instruct Sitecore to set the value of the field to the name of the item upon creation1. This token can be used in rich text, single-line text, and multi-line text fields2. To ensure that items created from a template automatically have the Title field populated with the name of the item, you should add the $name token to the template’s standard values Title field. This way, every item that inherits from the template will have the Title field set to the item name by default. You do not need to set the $name token in the new item’s content Title field, as this will only affect the specific item and not the template. The _name token is not a valid token in Sitecore and will not have any effect. References: 1: https://doc.sitecore.com/xp/en/developers/101/sitecore-experience-manager/the-name-token.html  2: https://doc.sitecore.com/xp/en/developers/sxa/93/sitecore-experience-accelerator/content-tokens.html