Sitecore-10-NET-Developer Sitecore 10 .NET Developer Exam Questions and Answers

A placeholder key is a unique identifier that is used to refer to a specific placeholder in the presentation details of an item. A placeholder key is defined in the placeholder settings item that is linked to a rendering or a sublayout. A placeholder key can also be defined in the code or markup of a component. A placeholder key can be static or dynamic. A static placeholder key has a fixed value, such as /main. A dynamic placeholder key has a variable value, such as /main-{GUID}, where {GUID} is replaced by a unique identifier at runtime. Dynamic placeholders allow multiple instances of the same component to be added to a placeholder without conflicts. References:

• 15
• 16
• 17

A data source is a content item that provides the data for a rendering. By default, a rendering uses the current page item as its data source, but it can be changed to use a different item. This allows the user to select a content item from a specific place within the content tree as the data source for the component. To ensure the component is flexible and the user can select a content item upon use, the component must support a change to the data source and the Datasource Location field must be configured. The Datasource Location field specifies where the user is allowed to look for the data source. It can be a reference to an item or a query that returns a list of items. The user can then select an existing item or create a new one from the Associated Content dialog in theExperience Editor or the Content Editor. This way, the user can reuse the same component with different data sources on different pages. References:

• Data sources
• Change the data source of a rendering
• Datasource Location

Versioned layouts allow you to create different layouts for different versions of an item. This means you can have a specific layout for a specific version of the main page that is published for a specific period, such as a company anniversary celebration. You can easily revert to the original layout by switching back to the previous version of the main page. Versioned layouts are stored in the __Renderings field of the item, which is a versioned field. Versioned layouts are enabled by default in Sitecore 10. References:

• [Sitecore 10 .NET Developer Certification Study Guide], page 14
• [Sitecore Documentation: Versioned layouts]

 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

This answer is based on the Sitecore documentation of dynamic placeholders1. Dynamic placeholders are an extension of the regular Sitecore placeholders that allow you to add the same placeholder name several times across multiple renderings, and even within the same rendering. Dynamic placeholders generate a unique key for each placeholder instance, which ensures that the content within the placeholder is unique and not duplicated. Dynamic placeholders also enable you to build functionality that generates multiple placeholders within the same rendering dynamically. For example, you can use dynamic placeholders to create a tab component that can have any number of tabs, each with its own content. References:

• Dynamic placeholders
• Sitecore dynamic placeholders and JSS
• Walkthrough: Configure your components to use dynamic placeholders

 The Master database in Sitecore is also called the Content Authoring Database. It contains all versions of all items, including the ones that have not been published yet. This is the database that content authors interact with, and is the default database used by the Sitecore Content Editor. The Master database supports content editing, workflow, versioning, and language features. The Master database is also the source database for publishing operations, which transfer the content to the target databases, such as the Web database. References:

• Master database
• Working with databases
• What is the difference between Sitecore’s core, master, and web databases?
• Difference between Core, Master and Web Databases in Sitecore

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

 Workbox is a Sitecore application that allows you to view and manage items that are in a workflow. Workbox displays the items that are in each workflow state and the commands that are available for each item. You can use Workbox to perform workflow actions, such as approving, rejecting, or editing items. Workbox also shows you the history and comments of each item in a workflow. Workbox is useful for content authorsand editors who need to review and publish items in a workflow. References: Sitecore 10.0 Developer Documentation - Workbox

Field editor buttons are custom experience editor buttons that allow content authors to edit multiple fields of an item in a pop-up window. This is useful for complex fields that are not easily editable in the experience editor, such as multilist fields, checkbox fields, or image fields. Field editor buttons can also be configured to edit the fields of the data source item of a rendering, rather than the page item. Field editor buttons can improve the content authoring experience by providing a convenient and consistent way to edit fields in the experience editor. References:

• 12
• 13
• 14

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 withoutneeding 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 field source is a property that you can set for some field types in a data template, such as Droplink, Droptree, Multilist, Image, File, and so on. The field source specifies the location of the items or media that the user can select from when editing the field. For example, if you have a Droplink field that allows the user to choose a category for an item, you can set the field source to point to a folder that contains the category items.This way, the user will only see the relevant items in the drop-down list. The field source can be a path, a GUID, or a Sitecore query that returns a single item or a list of items. The field source helps you to control the data source and the user interface for the field. References:

• The simple field types
• Controlling the list of items in a Selection field
• Using An Item’s Field as a Data Source in Sitecore

 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