70-331 - Design A Sharepoint Topology

Front 1

Flexible SharePoint Environment

Back 1

Enables the structure and layout to change with minimal impact to users

Front 2

Scalable SharePoint Environment

Back 2

Allows for the necessary growth to meet changing business requirements

Front 3

Site

Back 3

Smallest element in a taxonomy

Composed of lists and libraries

Front 4

Site Collection

Back 4

Grouping of sites that are functionally, navigationally and administratively related to one another.

Front 5

Top-level site

Back 5

First site created

Defines navigational relationship with all its subsites

Front 6

Single content database

Back 6

Site collection is stored in a single content database

Front 7

Scalability issues

Back 7

Security groups

Permissions inheritance

Taxonomical changes

Recycle bins

SQL backup and restore

Front 8

Security groups

Back 8

Each new site can in theory add up to three new permission groups - visitors, members and owners.

Number of additional groups can become unwieldy

Front 9

Permissions inheritance

Back 9

As volume of data in site collection increases, the surface area affected by permissions change becomes larger.

Minor permissions change near the top of a site collection can potentially expose sensitive data at a lower level site, list or library.

Front 10

Taxonomical changes

Back 10

Structural taxonomy changes in site columns and content types begin to affect the granular sites as well, especially if the parent column or content type is heavily altered.

Front 11

Recycle bins

Back 11

Individual sites recycle bins remain easy to adminster for the site owners, but site collection recycle bins begin to have thousands and thousands of documents that must be sorted through by the site collection administrator in the event of a restore request.

Front 12

SQL backup and restore

Back 12

As the volume of content increases within the site collection, backup and restoration times increase in duration along with the amount of data that can be influenced by a database corruption

Front 13

Navigational terms

Back 13

Four terms that should be defined

Global

Current

Structural

Managed Navigation

Front 14

Global and Current Navigation

Back 14

Front 15

Easiest site taxonomy

Back 15

Organizational chart

Front 16

Two types of navigation available

Back 16

Managed navigation

Structural navigation

Front 17

Two types of columns

Back 17

Site columns

List columns

Front 18

Difference between two types of columns

Back 18

Site columns are reusable

Front 19

Benefit of moving to site columns

Back 19

Extensibility - what was once a piece of metadata that could be associated with only one list can now be associated with many

Front 20

Site columns are hierarchical in nature. Explain

Back 20

When a site column is instantiated on a site, that site and all its child sites inherit the site column and its properties

Front 21

Problem with site collection limitation of site columns

Back 21

If you build multiple site collections you must have a mechanism to make metadata available beyond the site collection boundary. 

Front 22

Managed metadata service

Back 22

Model for presenting information types in multiple site columns across multiple site collections.

Front 23

Content type

Back 23

Defines the attributes of a list item, document or folder.

Front 24

Content type allows for

Back 24

provision of descriptive information about the item (metadata and properties)

provision of activities associated with each item (workflows, information management policies, document templates, and other features)

Front 25

Are content types hierarchical?

Back 25

Yes, they are inherited from each parent site to its child within the same site collection

If content type is changed, changes can be propogated throughout any list or library that had previously been assigned that content type.

Front 26

Number and type of content types provisioned automatically to a site collection depend on two factors

Back 26

Site template - the template you choose when provisioning a new site will determine the content types that are created

Features - The features you select to add to an existing SharePoint site/site collection can also provide new content types

Front 27

Content Type Hub

Back 27

Allows use of content types across multiple site collections

Front 28

Process for syndicating content types by the MMS - how it works

Back 28

MMS is configures to allow the content type hub to be the only source for centralized content type syndication

MMS is configured to consume content types from the hub's content type gallery

Content types are placed in the content type hub for syndication

Content types are published by the Content Type Subscriber timer jog on a regular basis (every hour by default) to all web applications that are connected to the MMS application.

Front 29

External content types

Back 29

Incorporate BCS functionality to enable external data to be represented within SharePoint sites.

Front 30

External content types are metadata that represent the following:

Back 30

Connectivity information to data

Data definitions for the data

Behaviours applied to data

Front 31

Webparts created for external content types

Back 31

Business data list

Business data item

Business data item builder

Business data related list

Business data actions

Front 32

Business data list

Back 32

Displays a list of entity instances from a business application presented by BCS, such as a customer or order list

Front 33

Business data item

Back 33

Displays the details of an item from a business application presented by BCS, such as a particular customer or order

Front 34

Business data item builder

Back 34

Creates a BCS item, providing it to other web parts

Front 35

Business data related list

Back 35

Displays a list of related items from a business application presented by BCS, such as all orders related to a particular customer

Front 36

Business data actions

Back 36

Displays a list of actions available to a portal user, such as sending e-mail or editing customer information

Front 37

Development using external content types is available via:

Back 37

SharePoint object model

Client object model

Representational State Transfer (REST) URLs

Front 38

Search can be broken down into 6 major components

Back 38

Search Administration

Crawl

Content Processing

Analytics Processing

Indexing 

Query Processing

Front 39

Search Administration

Back 39

Administration of search components

Provides for the creation and initialization of new search components

Front 40

Crawl

Back 40

Performs crawl of content available

Accomplished via the use of an indexing connector or protocol handler and depends on the type of file being crawled.

Front 41

Content Processing

Back 41

Mapping of crawled properties to managed properties.

Items that have been crawled are turned into artifacts for inclusiong within the search index.

Link and URL information is stored in the link database and then processed and forwarded to the Analytics Processing component.

Front 42

Analytics Processing

Back 42

Two major types of analysis:

Search analytics focuses on the analysis of content being crawled and added to the search index.  Items that are analyzed within search analytics improve search relevance and recall.

Usage analytics focuses on user actions within search, providing a statistical analysis of usage counts, recommendations and activity ranking to influence search relevance.

 

Search relevance for items (links and URLs) are passed back to content processing.

Front 43

Index component

Back 43

Wrties content to the search index.

Also receives requests for information contained in the search index and returns result sets to the query processing component.

Front 44

Query Processing

Back 44

Receives and analyzes incoming search queries, which improve the precision, recal and relevance of the search result sets.

Front 45

Keyword set

Back 45

Specialised term set and is non hierarchical.

Generated as folksonomy

Stored in the term store database

Front 46

How to configure default storage location of keyword set

Back 46

Open Central Administration and select Application Management

Under Service Applications, select Manage Service Applications

Select the MMS Connection

From the ribbon, choose the Properties link

On the Edit Managed Metadata Service Connection page, select the check box for This Service Application is the Default Storage Location for Keywords

 

Add the enterprise keywords column to a list or document library

 

After keywords are added to a list item or document, they are automatically added to the Managed Metadata term store.

Front 47

If you decide to create a new managed property at the site collection level, there are a few restrictions

Back 47

They can be of the type text or yes/no (Boolean)

They cannot be refinable, which means that they cannot be used as a refiner for search results

They cannot be sortable, which means that they cannot be used for sorting the result set

Front 48

To create managed property from Central Admin

Back 48

Open Central Admin

Application Management

Select Manage Service Applications

Select name of Search Service Application

Select Manage menu item from ribbon

Under Queries and Results select Search Schema