Free Sitecore-10-NET-Developer sample questions

A development team is implementing a multi-tenant Sitecore solution following Helix principles. They have a 'Foundation.Common' module providing a base page template and a 'Feature.News' module with a 'News Article' template inheriting from the base page. The 'Project.MainWebsite' layer uses these templates. During a code review, it's noted that the 'Feature.News' module directly references a rendering from a 'Feature.SocialSharing' module to display share buttons. According to Helix dependency rules, what is the most appropriate way to resolve this architectural violation?

• Move the 'SocialSharing' rendering definition into the 'Foundation.Common' module.
• Use a placeholder in the 'News Article' rendering and have the 'Project.MainWebsite' layer bind the 'SocialSharing' rendering to it in the presentation details.
• Merge the 'Feature.News' and 'Feature.SocialSharing' modules into a single, larger 'Feature.NewsAndSocial' module.
• Create a direct project reference from the 'Feature.News' project to the 'Feature.SocialSharing' project in Visual Studio.

A Sitecore administrator is attempting to configure a new content delivery (CD) server role. After deploying the files and attempting to start the site, they observe that the application pool fails to start, and logs indicate a configuration error related to a custom pipeline processor. The administrator needs to ensure this processor only loads on the content management (CM) server. What is the correct XML syntax to use in a patch file to achieve this?

A global company has a website with content in English (en), German (de-DE), and Swiss German (de-CH). The business rule is that if a field in a Swiss German item version is empty, it should display the value from the German version. If the German version is also empty, it should not fall back to English. Which configuration settings are required to implement this specific language fallback chain? (Select TWO)

• In the `/sitecore/system/Languages/de-CH` item, set the 'Fallback Language' field to 'de-DE'.
• In a patch file, set `enforceVersionPresence` to `true` for the site.
• In the `/sitecore/system/Languages/de-DE` item, ensure the 'Fallback Language' field is empty.
• In a patch file, set `languagefallback.ItemLevel` to `true`.
• In the `/sitecore/system/Languages/en` item, set the 'Fallback Language' field to 'de-DE'.

A developer is creating a set of templates for blog authors. They've created a base template called `_ContentBase` with fields for 'Title' and 'Summary'. They want to create a new template, `BlogPost`, which inherits from `_ContentBase`. To improve the authoring experience, whenever a new `BlogPost` item is created, the 'Title' field should be pre-populated with the name of the item. How should this be accomplished using Sitecore best practices?

• Write a custom `item:added` event handler to programmatically set the 'Title' field value.
• On the `BlogPost` template's Standard Values, set the raw value of the 'Title' field to `$name`.
• On the `_ContentBase` template's Standard Values, set the raw value of the 'Title' field to `$name`.
• Create a custom Experience Editor button that executes a script to copy the item name to the 'Title' field.

A developer needs to retrieve all child items of the `/sitecore/content/Home` item that are based on the 'ProductPage' template. For performance reasons, the query should avoid returning all children and then filtering in memory. Which Sitecore API code snippet performs this query most efficiently?

• `homeItem.GetChildren().Where(i => i.TemplateName == "ProductPage");`
• `homeItem.Axes.GetDescendants().Where(i => i.TemplateName == "ProductPage");`
• `Sitecore.Context.Database.SelectItems("fast:/sitecore/content/Home/*[@@templatename='ProductPage']");`
• `Sitecore.Context.Database.GetItem("/sitecore/content/Home").Children.Where(i => i.TemplateID == productTemplateId);`

A website's search functionality is returning inaccurate results for product specifications stored in a 'Rich Text' field. The field contains HTML markup, and searches for terms inside tags (e.g., 'strong') are matching, which is undesirable. To fix this, the search index needs to store a plain-text version of the content. What is the most appropriate way to configure this in Sitecore's content search?

• Create a computed index field that programmatically strips HTML and stores the plain text.
• In the index configuration, for the 'Rich Text' field, set the `type` attribute to `string` and the `storageType` to `YES`.
• In the ` ` section of the index configuration, add a `typeMatch` for `rich text` and map it to the `HtmlStripFieldReader`.
• Write a custom search query predicate that uses a regular expression to ignore HTML tags at query time.

A developer has created a Controller Rendering for a 'Call to Action' component. The component needs a data source item to provide the button text and link. To ensure content authors can easily select a valid data source, the developer wants to restrict the selection to items based on the 'CallToActionData' template, located under `/sitecore/content/Global/CTAs`. Which field on the rendering item should be configured to enable this?

• Datasource Template
• Datasource Location
• Parameters
• Compatible Renderings

A marketing team wants to display a promotional banner to visitors who arrive at the website from a specific marketing campaign. The campaign is tagged with the UTM code `utm_campaign=summer_sale`. Using the Rule Set Editor, which condition should be used to identify these visitors?

• where the referring site contains 'summer_sale'
• where the current visit's campaign was triggered and the campaign name contains 'summer_sale'
• where the query string contains 'utm_campaign=summer_sale'
• where a specific goal named 'summer_sale' was triggered during the current visit

True or False: In a standard Sitecore 10 installation, patch files located in the `App_Config/Include/Project` folder will always be loaded before files in the `App_Config/Include/Feature` folder.

• True
• False

A developer is using the Sitecore CLI to serialize content items for source control. After running `dotnet sitecore ser pull`, they notice that a newly created template is not being serialized. The `module.json` file contains the following rule for templates: ```json { "namespace": "MyProject.Templates", "path": "/sitecore/templates/Project/MyProject", "scope": "ItemAndDescendants", "allowedPushOperations": "CreateUpdateAndDelete" } ``` The new template was created at `/sitecore/templates/Feature/MyFeature`. What is the reason for this issue?

• The `allowedPushOperations` value is incorrect.
• The serialization rule's `path` does not include the location of the new template.
• The `dotnet sitecore ser pull` command does not serialize templates; `dotnet sitecore ser push` must be used.
• The `scope` property should be set to `DescendantsOnly`.