Sitecore-Experience-Solution-9-Developer Sample Questions Answers

host name

rootPath

startItem

All

@Html.Sitecore().FieldType("Title")

@Html.Sitecore().Field("Title")

@Html.Sitecore().Text("Title")

@Html.Sitecore()("Title")

Sitecore will remove these fields into the same field section

Sitecore will merge these fields into the same field section

Sitecore will edit these fields into the same field section

Sitecore will merge these fields into the different field section

You will get two fields with the same name, which leads to confusion both to users and developers. It should be avoided.

You will get two fields with the same name, which leads to confusion both to users and developers. It should not be avoided.

You will get one fields with the same name, which leads to confusion both to users and developers. It should be avoided.

None

Vertical Scaling

Horizontal Scaling

Inclined Scaling

None

Allow editing content in a sandbox without affecting the content on the live site

To be able to have multiple servers delivering your live site content

To make version upgrades much easier

To separate your own configuration from the standard one that comes with Sitecore

By configuring LinkURIManager to use the item's DisplayName

By setting the URIManager to use the item's DisplayName

By setting the IndexManager to use the item's DisplayName

By setting the LinkManager to use the item's DisplayName

Creating a folder for each site in the Content section of the content tree

Create a Home item of each site in the content tree

Shared content should not be stored outside of each site folder

All

Add the data template to the component's Datasource Location field.

Add the data template to the component's Datasource Template field.

Both

None

Standard Template Values

Standard Template

Standard Data Template

Base Template

In the Standard Values, so they are applied as a options to newly created items.

In the Standard Values, so they are applied as a default to newly created items.

In the Standard tempates, so they are applied as a default to newly created items.

In the base tempates, so they are applied as a default to newly created items.

By creating some definition items in the Core db by adding the buttons property to the Field Editor

By creating some definition items in the Master db by adding the buttons property to the Field Editor

By creating some definition items in the Web db by adding the buttons property to the Field Editor

All

States

Commands

Actions

All

A package installation cannot be undone

Create an Undo Package when you create the package

Install the Package Uninstaller module

Create an Anti-Package when you install with Sitecore Rocks

Instead of returning a null field value, it will check if the same field in the Standard Value item has a value and then it'll return that value.

Error

403

500 Internal Error

Put a .config patch file in the App_Config/Include folder

IIS

Web.config

All

Name

Template

Location (parent node)

All

The Standard template

The Inherited template

The Standard Rendering Parameters template

All

doc.sitecore.net

dev.sitecore.net

doc.sitecore.sdn

None

Text (single-line, multi-line, rich text)

Media (image, file)

Link (droplink group droplink, droptree)

All

On the component’s definition item in the Parameters Template field

On the Layout definition item in the Parameters Template field

presentation details

Edit Frame

Component

None

SearchResultItem

SearchItem

ResultItem

All

merges fields from all inherited templates

All templates inherit from Standard Template

contains fields that define system properties (like presentation details) and modifying the Content Base template will affect all the items immediately

All

Insert Options

Standard Values

Token

Standard Template

The Experience Editor provides editing and designing functionality(Also accept: marketing)

The Content Editor provides editing and designing functionality. (Also accept: marketing)

Both

None

Sitecore Dictionary entries

Sitecore Indexing entries

both a and b

Only b

Text fields (Single-Line, Multi-Line, Rich Text)

Date/datetime

Image, General Link

All

By adding a Content Editor Button to a toolbar

By adding a Frame Button to a toolbar

By adding a Field Editor Button to a toolbar

none

Using

Using

Using

Using

marketplace.sitecore.net

marketplace.sitecore.com

doc.sitecore.net

dev.sitecore.net

Out of process Java extension of Lucene

Enterprise ready

Multiserver

All

LINQ

IIS

GroupBy

None

By deserializing them. How they get serialized will depend on the tools you have at your disposal.

By serializing them. How they get serialized will depend on the tools you have at your disposal.

$name

$date

$now

All

Content Editor

Experience Editor

Control Panel

All

To define default values for templates

Define fields that Sitecore uses internally but are not shown to the user

To define some fields you will need in all your pages: title, text, keywords, etc.

To define the overall structure of your page

In the Experience Editor, the user will be able to add any component to the placeholder.

In the Experience Editor, the user will not be able to add any component to the place-holder.

Where

Contains

Any, All, OrderBy

All

Controller Rendering

View Rendering

both a and b

None

storage type

index type

index name

All

field definition

field section

field source

data type