which option should you select?
###BeginCaseStudy###
Testlet 1
Background
You are a SharePoint developer working for Litware Inc., a large bicycle manufacturing company. Litware runs
an intranet that is based on SharePoint Server 2010, side-by-side with a collaboration space for various
departments. The IT department for Litware is migrating a SharePoint 2010 environment to a new SharePoint
2013 farm. Some collaboration site collections are already migrated, including a Marketing site collection. Some
of the intranet content must be migrated to the target platform; however, the whole intranet won’t be migrated
as-is.
Business Requirements
Intranet
Litware is redefining its brand identity. It is essential that the new intranet supports a wide variety of mobile
devices, platforms, and browsers. Some of the content must be migrated from the old intranet during the
implementation. The redesigned intranet must be extensible. The solution must be designed with the changes
in the underlying technology in mind.
A marketing company named Graphic Design Institute provides documents and guidelines for the new design
for Litware’s intranet.
Collaboration
Litware has the following collaboration requirements:
The collaboration space must include a start page containing information about site owners, contact data,
and statistics on site usage. This information must be available for each collaboration space, directly after its
creation.
The project must be delivered in multiple phases.
The solution must support changes and updates on the structure and functionality of the collaboration
spaces.
Marketing collaboration space
Auditors must be able to create reports about the documents the Marketing team produces. Initial reports
should show document distribution over projects and information about the most active documents, the top
inactive documents, and the most active users. Additional reports will be added over time.
Technical Requirements
Publishing Design for the Intranet
Litware will use the following web application for the intranet: https://intranet.litwareinc.com.
The publishing site design is delivered as a set of HTML files (litwarepublishing.html), CSS
(Litwarepublishing.css), and image files from the marketing company. A design package must be created for
easier deployment over various platforms. During the creation and application of the design package to the
publishing site, SharePoint 2013 out-of-the-box capabilities must be used as much as possible to ensure simple
design changes and to ease the upgrade procedures. The publishing site must support rendering on a number
of devices, starting with Windows Phone 7. Apart from being deployed on all existing publishing sites, the
design package must be automatically deployed each time a publishing site is created. A search box must be
available on all pages.
Collaboration
Litware will use two additional web applications for the collaboration:
Collaboration 1: https://collab1.litwareinc.com
Collaboration 2: https://collab2.litwareinc.com
Most of the features contained within the Team Site template are sufficient; however, a few additions to the
template must be made to support the business requirements. In order to achieve this and ensure maximum
portability, a web template based on the Team Site site definition must be created. A three-state workflow must
be used to manage business processes. A customized default home page must be deployed by using a site
feature.Feature IDs:
Three-state workflow: FDE5D850-671E-4143-950A-87B473922DC7
Litware Web Artifacts: DBF805AB-03D9-43DC-9154-52D6AC54689F
The project must be implemented in phases, so a solution must be developed to support upgrade procedures.
As soon as the package containing the web template Litware.Intranet.Templates.wsp is deployed, the Litware
Team Site template must be available for use in all site collections. In order to make the solution as extensible
as possible, all core functionality should be moved to the separate package Litware.Intranet.Core.wsp.
Deployment of the package containing the Litware web templates Litware.Intranet.Templates.wsp must be
prevented if the core package is not deployed in order to prevent deployment errors and eventually damage on
the site structure itself.
Litware.Intranet.Templates contains two features:
The LitwareWebTemplateFeature feature contains the Litware Team Site web template. Templates with this
title must be available in the group Litware in the template selection.
The LitwareWebArtifacts hidden feature contains code required to run after the provisioning is completed.
The LitwareWebArtifacts feature can be activated only if the LitwareWebTemplateFeature feature is activated
as well.
Marketing site collection
An existing marketing collaboration site located in a web application named Collaboration 1 is located at https://
collabl.litwareinc.com/sites/marketing. Collaboration 1 contains a document library with approximately 9000
documents for approximately 200 projects. The largest project contains 120 files. Documents are assigned to
appropriate projects by using the Projects field. The farm uses the default throttle settings.
Auditors have access to the page that provides statistics on Marketing documents. This page contains a report
on document distribution over projects and information about the most active documents, the top inactive
documents, and the most active users. Processing the queries can result in working with huge result sets. You
must ensure that the information on this page is always available and that the queries are not throttled. The
relevant code segment is available in the code sections area (MarketingAudit.ascx.cs).
Application Structure
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for
reference only and include a two-letter prefix that denotes the specific file to which they belong.)
Litware.Intranet.Templates.wsp, Module WebTemplatePropertyBag
Element.xml file:
MarketingAudit.ascx.cs
###EndCaseStudy###
HOTSPOT
You need to ensure that users can sort files by using the Projects field.
From the List Settings page, which option should you select? (To answer, select the appropriate option in the
answer area.)
Hot Area:
You need to ensure that the package deploys successfully
###BeginCaseStudy###
Testlet 1
Background
You are a SharePoint developer working for Litware Inc., a large bicycle manufacturing company. Litware runs
an intranet that is based on SharePoint Server 2010, side-by-side with a collaboration space for various
departments. The IT department for Litware is migrating a SharePoint 2010 environment to a new SharePoint
2013 farm. Some collaboration site collections are already migrated, including a Marketing site collection. Some
of the intranet content must be migrated to the target platform; however, the whole intranet won’t be migrated
as-is.
Business Requirements
Intranet
Litware is redefining its brand identity. It is essential that the new intranet supports a wide variety of mobile
devices, platforms, and browsers. Some of the content must be migrated from the old intranet during the
implementation. The redesigned intranet must be extensible. The solution must be designed with the changes
in the underlying technology in mind.
A marketing company named Graphic Design Institute provides documents and guidelines for the new design
for Litware’s intranet.
Collaboration
Litware has the following collaboration requirements:
The collaboration space must include a start page containing information about site owners, contact data,
and statistics on site usage. This information must be available for each collaboration space, directly after its
creation.
The project must be delivered in multiple phases.
The solution must support changes and updates on the structure and functionality of the collaboration
spaces.
Marketing collaboration space
Auditors must be able to create reports about the documents the Marketing team produces. Initial reports
should show document distribution over projects and information about the most active documents, the top
inactive documents, and the most active users. Additional reports will be added over time.
Technical Requirements
Publishing Design for the Intranet
Litware will use the following web application for the intranet: https://intranet.litwareinc.com.
The publishing site design is delivered as a set of HTML files (litwarepublishing.html), CSS
(Litwarepublishing.css), and image files from the marketing company. A design package must be created for
easier deployment over various platforms. During the creation and application of the design package to the
publishing site, SharePoint 2013 out-of-the-box capabilities must be used as much as possible to ensure simple
design changes and to ease the upgrade procedures. The publishing site must support rendering on a number
of devices, starting with Windows Phone 7. Apart from being deployed on all existing publishing sites, the
design package must be automatically deployed each time a publishing site is created. A search box must be
available on all pages.
Collaboration
Litware will use two additional web applications for the collaboration:
Collaboration 1: https://collab1.litwareinc.com
Collaboration 2: https://collab2.litwareinc.com
Most of the features contained within the Team Site template are sufficient; however, a few additions to the
template must be made to support the business requirements. In order to achieve this and ensure maximum
portability, a web template based on the Team Site site definition must be created. A three-state workflow must
be used to manage business processes. A customized default home page must be deployed by using a site
feature.Feature IDs:
Three-state workflow: FDE5D850-671E-4143-950A-87B473922DC7
Litware Web Artifacts: DBF805AB-03D9-43DC-9154-52D6AC54689F
The project must be implemented in phases, so a solution must be developed to support upgrade procedures.
As soon as the package containing the web template Litware.Intranet.Templates.wsp is deployed, the Litware
Team Site template must be available for use in all site collections. In order to make the solution as extensible
as possible, all core functionality should be moved to the separate package Litware.Intranet.Core.wsp.
Deployment of the package containing the Litware web templates Litware.Intranet.Templates.wsp must be
prevented if the core package is not deployed in order to prevent deployment errors and eventually damage on
the site structure itself.
Litware.Intranet.Templates contains two features:
The LitwareWebTemplateFeature feature contains the Litware Team Site web template. Templates with this
title must be available in the group Litware in the template selection.
The LitwareWebArtifacts hidden feature contains code required to run after the provisioning is completed.
The LitwareWebArtifacts feature can be activated only if the LitwareWebTemplateFeature feature is activated
as well.
Marketing site collection
An existing marketing collaboration site located in a web application named Collaboration 1 is located at https://
collabl.litwareinc.com/sites/marketing. Collaboration 1 contains a document library with approximately 9000
documents for approximately 200 projects. The largest project contains 120 files. Documents are assigned to
appropriate projects by using the Projects field. The farm uses the default throttle settings.
Auditors have access to the page that provides statistics on Marketing documents. This page contains a report
on document distribution over projects and information about the most active documents, the top inactive
documents, and the most active users. Processing the queries can result in working with huge result sets. You
must ensure that the information on this page is always available and that the queries are not throttled. The
relevant code segment is available in the code sections area (MarketingAudit.ascx.cs).
Application Structure
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for
reference only and include a two-letter prefix that denotes the specific file to which they belong.)
Litware.Intranet.Templates.wsp, Module WebTemplatePropertyBag
Element.xml file:
MarketingAudit.ascx.cs
###EndCaseStudy###
You implement the dependency changes based on the requirements for the Litware web artifacts feature.
When you deploy the Litware.Intranet.Templates.wsp package, you receive an error message.
You need to ensure that the package deploys successfully.
What should you do?
You need to create a design package for the publishing sites
###BeginCaseStudy###
Testlet 1
Background
You are a SharePoint developer working for Litware Inc., a large bicycle manufacturing company. Litware runs
an intranet that is based on SharePoint Server 2010, side-by-side with a collaboration space for various
departments. The IT department for Litware is migrating a SharePoint 2010 environment to a new SharePoint
2013 farm. Some collaboration site collections are already migrated, including a Marketing site collection. Some
of the intranet content must be migrated to the target platform; however, the whole intranet won’t be migrated
as-is.
Business Requirements
Intranet
Litware is redefining its brand identity. It is essential that the new intranet supports a wide variety of mobile
devices, platforms, and browsers. Some of the content must be migrated from the old intranet during the
implementation. The redesigned intranet must be extensible. The solution must be designed with the changes
in the underlying technology in mind.
A marketing company named Graphic Design Institute provides documents and guidelines for the new design
for Litware’s intranet.
Collaboration
Litware has the following collaboration requirements:
The collaboration space must include a start page containing information about site owners, contact data,
and statistics on site usage. This information must be available for each collaboration space, directly after its
creation.
The project must be delivered in multiple phases.
The solution must support changes and updates on the structure and functionality of the collaboration
spaces.
Marketing collaboration space
Auditors must be able to create reports about the documents the Marketing team produces. Initial reports
should show document distribution over projects and information about the most active documents, the top
inactive documents, and the most active users. Additional reports will be added over time.
Technical Requirements
Publishing Design for the Intranet
Litware will use the following web application for the intranet: https://intranet.litwareinc.com.
The publishing site design is delivered as a set of HTML files (litwarepublishing.html), CSS
(Litwarepublishing.css), and image files from the marketing company. A design package must be created for
easier deployment over various platforms. During the creation and application of the design package to the
publishing site, SharePoint 2013 out-of-the-box capabilities must be used as much as possible to ensure simple
design changes and to ease the upgrade procedures. The publishing site must support rendering on a number
of devices, starting with Windows Phone 7. Apart from being deployed on all existing publishing sites, the
design package must be automatically deployed each time a publishing site is created. A search box must be
available on all pages.
Collaboration
Litware will use two additional web applications for the collaboration:
Collaboration 1: https://collab1.litwareinc.com
Collaboration 2: https://collab2.litwareinc.com
Most of the features contained within the Team Site template are sufficient; however, a few additions to the
template must be made to support the business requirements. In order to achieve this and ensure maximum
portability, a web template based on the Team Site site definition must be created. A three-state workflow must
be used to manage business processes. A customized default home page must be deployed by using a site
feature.Feature IDs:
Three-state workflow: FDE5D850-671E-4143-950A-87B473922DC7
Litware Web Artifacts: DBF805AB-03D9-43DC-9154-52D6AC54689F
The project must be implemented in phases, so a solution must be developed to support upgrade procedures.
As soon as the package containing the web template Litware.Intranet.Templates.wsp is deployed, the Litware
Team Site template must be available for use in all site collections. In order to make the solution as extensible
as possible, all core functionality should be moved to the separate package Litware.Intranet.Core.wsp.
Deployment of the package containing the Litware web templates Litware.Intranet.Templates.wsp must be
prevented if the core package is not deployed in order to prevent deployment errors and eventually damage on
the site structure itself.
Litware.Intranet.Templates contains two features:
The LitwareWebTemplateFeature feature contains the Litware Team Site web template. Templates with this
title must be available in the group Litware in the template selection.
The LitwareWebArtifacts hidden feature contains code required to run after the provisioning is completed.
The LitwareWebArtifacts feature can be activated only if the LitwareWebTemplateFeature feature is activated
as well.
Marketing site collection
An existing marketing collaboration site located in a web application named Collaboration 1 is located at https://
collabl.litwareinc.com/sites/marketing. Collaboration 1 contains a document library with approximately 9000
documents for approximately 200 projects. The largest project contains 120 files. Documents are assigned to
appropriate projects by using the Projects field. The farm uses the default throttle settings.
Auditors have access to the page that provides statistics on Marketing documents. This page contains a report
on document distribution over projects and information about the most active documents, the top inactive
documents, and the most active users. Processing the queries can result in working with huge result sets. You
must ensure that the information on this page is always available and that the queries are not throttled. The
relevant code segment is available in the code sections area (MarketingAudit.ascx.cs).
Application Structure
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for
reference only and include a two-letter prefix that denotes the specific file to which they belong.)
Litware.Intranet.Templates.wsp, Module WebTemplatePropertyBag
Element.xml file:
MarketingAudit.ascx.cs
###EndCaseStudy###
You need to create a design package for the publishing sites.
What should you do?
Which code segment should you insert at line MA08?
###BeginCaseStudy###
Testlet 1
Background
You are a SharePoint developer working for Litware Inc., a large bicycle manufacturing company. Litware runs
an intranet that is based on SharePoint Server 2010, side-by-side with a collaboration space for various
departments. The IT department for Litware is migrating a SharePoint 2010 environment to a new SharePoint
2013 farm. Some collaboration site collections are already migrated, including a Marketing site collection. Some
of the intranet content must be migrated to the target platform; however, the whole intranet won’t be migrated
as-is.
Business Requirements
Intranet
Litware is redefining its brand identity. It is essential that the new intranet supports a wide variety of mobile
devices, platforms, and browsers. Some of the content must be migrated from the old intranet during the
implementation. The redesigned intranet must be extensible. The solution must be designed with the changes
in the underlying technology in mind.
A marketing company named Graphic Design Institute provides documents and guidelines for the new design
for Litware’s intranet.
Collaboration
Litware has the following collaboration requirements:
The collaboration space must include a start page containing information about site owners, contact data,
and statistics on site usage. This information must be available for each collaboration space, directly after its
creation.
The project must be delivered in multiple phases.
The solution must support changes and updates on the structure and functionality of the collaboration
spaces.
Marketing collaboration space
Auditors must be able to create reports about the documents the Marketing team produces. Initial reports
should show document distribution over projects and information about the most active documents, the top
inactive documents, and the most active users. Additional reports will be added over time.
Technical Requirements
Publishing Design for the Intranet
Litware will use the following web application for the intranet: https://intranet.litwareinc.com.
The publishing site design is delivered as a set of HTML files (litwarepublishing.html), CSS
(Litwarepublishing.css), and image files from the marketing company. A design package must be created for
easier deployment over various platforms. During the creation and application of the design package to the
publishing site, SharePoint 2013 out-of-the-box capabilities must be used as much as possible to ensure simple
design changes and to ease the upgrade procedures. The publishing site must support rendering on a number
of devices, starting with Windows Phone 7. Apart from being deployed on all existing publishing sites, the
design package must be automatically deployed each time a publishing site is created. A search box must be
available on all pages.
Collaboration
Litware will use two additional web applications for the collaboration:
Collaboration 1: https://collab1.litwareinc.com
Collaboration 2: https://collab2.litwareinc.com
Most of the features contained within the Team Site template are sufficient; however, a few additions to the
template must be made to support the business requirements. In order to achieve this and ensure maximum
portability, a web template based on the Team Site site definition must be created. A three-state workflow must
be used to manage business processes. A customized default home page must be deployed by using a site
feature.Feature IDs:
Three-state workflow: FDE5D850-671E-4143-950A-87B473922DC7
Litware Web Artifacts: DBF805AB-03D9-43DC-9154-52D6AC54689F
The project must be implemented in phases, so a solution must be developed to support upgrade procedures.
As soon as the package containing the web template Litware.Intranet.Templates.wsp is deployed, the Litware
Team Site template must be available for use in all site collections. In order to make the solution as extensible
as possible, all core functionality should be moved to the separate package Litware.Intranet.Core.wsp.
Deployment of the package containing the Litware web templates Litware.Intranet.Templates.wsp must be
prevented if the core package is not deployed in order to prevent deployment errors and eventually damage on
the site structure itself.
Litware.Intranet.Templates contains two features:
The LitwareWebTemplateFeature feature contains the Litware Team Site web template. Templates with this
title must be available in the group Litware in the template selection.
The LitwareWebArtifacts hidden feature contains code required to run after the provisioning is completed.
The LitwareWebArtifacts feature can be activated only if the LitwareWebTemplateFeature feature is activated
as well.
Marketing site collection
An existing marketing collaboration site located in a web application named Collaboration 1 is located at https://
collabl.litwareinc.com/sites/marketing. Collaboration 1 contains a document library with approximately 9000
documents for approximately 200 projects. The largest project contains 120 files. Documents are assigned to
appropriate projects by using the Projects field. The farm uses the default throttle settings.
Auditors have access to the page that provides statistics on Marketing documents. This page contains a report
on document distribution over projects and information about the most active documents, the top inactive
documents, and the most active users. Processing the queries can result in working with huge result sets. You
must ensure that the information on this page is always available and that the queries are not throttled. The
relevant code segment is available in the code sections area (MarketingAudit.ascx.cs).
Application Structure
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for
reference only and include a two-letter prefix that denotes the specific file to which they belong.)
Litware.Intranet.Templates.wsp, Module WebTemplatePropertyBag
Element.xml file:
MarketingAudit.ascx.cs
###EndCaseStudy###
You create a document reporting Web Part for the Marketing team auditors.
You need to configure throttling for the Web Part.
Which code segment should you insert at line MA08?
Which code segment should you add at line UA11?
###BeginCaseStudy###
Testlet 1
Background
Coho Winery implements a SharePoint farm. They have an intranet site for company employees and an
extranet site for their customers. Coho Winery sells products to wholesale and retail customers. Customers
must be able to order specific brands and pay directly.
Business Requirements
Site Collection
The company must organize its main enterprise site to have multiple site collections for different wine brands
from various regions. Site documents must have a consistent look and feel.
New Features
The first version (1.0.0.0) of the feature must support the addition of newer functionality when the feature is
upgraded to version 1.5.0.0.
Technical Requirements
General
A Document content type named Finance must be created at the site level. It must contain two site columns
named Customer Name and Transaction Date.
The Order Details and Payment Confirmation content types must be derived from the Finance content type.
Workflows associated with document content types must be initiated when documents are generated.
When Payment Confirmation documents are generated, a workflow must send a notification to the customer
by email.
User Authorization
A custom role named Wholesale must be created. Wholesale customers must be assigned to this role in
order to view the promotions page.
A custom permission level must be created. This permission level must add the ViewPages permission to
the existing base permissions. This permission level must be added to Wholesale user role.
Anonymous users must be able to browse the site with limited access to resources.
The web application has been created with anonymous access enabled.
Users are prompted for credentials when they browse to the site.
Application Lifecycle Management
Versioning of the solution artifacts must adhere to industry best practices.
In a future upgrade process, a new site column named Division must be added to the Finance content type
programmatically.
Only one version of an assembly must be available at runtime.
Code based hot fixes must be deployed directly to the Global Assembly Cache on all SharePoint servers.
During maintenance periods, content must be available but must not be modified.
Backup and Recovery
In the event of hardware failure, the SharePoint environment must be restored to the most recent date.
The backup process must not degrade system performance.
Performance Optimization and Memory Usage
SPSite objects must be removed from memory immediately after the objects go out of scope.
Automation
Windows PowerShell must be used to automate all operations wherever possible.
Application Structure
Relevant portions of the application files are shown below. (Line numbers in the code segments are included for
reference only and include a two-character prefix that denotes the specific file to which they belong.)
ContentType.cs
UserAuthorization.cs
ContentType.Finance.Template.xml
ExportWholesaleSites.ps1
###EndCaseStudy###
You need to set the appropriate permission levels. A variable named customRole references Wholesale.
Which code segment should you add at line UA11?
You need to automate the backup of a site collection
###BeginCaseStudy###
Testlet 1
Background
Coho Winery implements a SharePoint farm. They have an intranet site for company employees and an
extranet site for their customers. Coho Winery sells products to wholesale and retail customers. Customers
must be able to order specific brands and pay directly.
Business Requirements
Site Collection
The company must organize its main enterprise site to have multiple site collections for different wine brands
from various regions. Site documents must have a consistent look and feel.
New Features
The first version (1.0.0.0) of the feature must support the addition of newer functionality when the feature is
upgraded to version 1.5.0.0.
Technical Requirements
General
A Document content type named Finance must be created at the site level. It must contain two site columns
named Customer Name and Transaction Date.
The Order Details and Payment Confirmation content types must be derived from the Finance content type.
Workflows associated with document content types must be initiated when documents are generated.
When Payment Confirmation documents are generated, a workflow must send a notification to the customer
by email.
User Authorization
A custom role named Wholesale must be created. Wholesale customers must be assigned to this role in
order to view the promotions page.
A custom permission level must be created. This permission level must add the ViewPages permission to
the existing base permissions. This permission level must be added to Wholesale user role.
Anonymous users must be able to browse the site with limited access to resources.
The web application has been created with anonymous access enabled.
Users are prompted for credentials when they browse to the site.
Application Lifecycle Management
Versioning of the solution artifacts must adhere to industry best practices.
In a future upgrade process, a new site column named Division must be added to the Finance content type
programmatically.
Only one version of an assembly must be available at runtime.
Code based hot fixes must be deployed directly to the Global Assembly Cache on all SharePoint servers.
During maintenance periods, content must be available but must not be modified.
Backup and Recovery
In the event of hardware failure, the SharePoint environment must be restored to the most recent date.
The backup process must not degrade system performance.
Performance Optimization and Memory Usage
SPSite objects must be removed from memory immediately after the objects go out of scope.
Automation
Windows PowerShell must be used to automate all operations wherever possible.
Application Structure
Relevant portions of the application files are shown below. (Line numbers in the code segments are included for
reference only and include a two-character prefix that denotes the specific file to which they belong.)
ContentType.cs
UserAuthorization.cs
ContentType.Finance.Template.xml
ExportWholesaleSites.ps1
###EndCaseStudy###
You need to automate the backup of a site collection.
What should you do? (Each correct answer presents part of the solution. Choose all that apply.)
Which code segments should you include in Target 1, Tar…
###BeginCaseStudy###
Testlet 1
Background
Coho Winery implements a SharePoint farm. They have an intranet site for company employees and an
extranet site for their customers. Coho Winery sells products to wholesale and retail customers. Customers
must be able to order specific brands and pay directly.
Business Requirements
Site Collection
The company must organize its main enterprise site to have multiple site collections for different wine brands
from various regions. Site documents must have a consistent look and feel.
New Features
The first version (1.0.0.0) of the feature must support the addition of newer functionality when the feature is
upgraded to version 1.5.0.0.
Technical Requirements
General
A Document content type named Finance must be created at the site level. It must contain two site columns
named Customer Name and Transaction Date.
The Order Details and Payment Confirmation content types must be derived from the Finance content type.
Workflows associated with document content types must be initiated when documents are generated.
When Payment Confirmation documents are generated, a workflow must send a notification to the customer
by email.
User Authorization
A custom role named Wholesale must be created. Wholesale customers must be assigned to this role in
order to view the promotions page.
A custom permission level must be created. This permission level must add the ViewPages permission to
the existing base permissions. This permission level must be added to Wholesale user role.
Anonymous users must be able to browse the site with limited access to resources.
The web application has been created with anonymous access enabled.
Users are prompted for credentials when they browse to the site.
Application Lifecycle Management
Versioning of the solution artifacts must adhere to industry best practices.
In a future upgrade process, a new site column named Division must be added to the Finance content type
programmatically.
Only one version of an assembly must be available at runtime.
Code based hot fixes must be deployed directly to the Global Assembly Cache on all SharePoint servers.
During maintenance periods, content must be available but must not be modified.
Backup and Recovery
In the event of hardware failure, the SharePoint environment must be restored to the most recent date.
The backup process must not degrade system performance.
Performance Optimization and Memory Usage
SPSite objects must be removed from memory immediately after the objects go out of scope.
Automation
Windows PowerShell must be used to automate all operations wherever possible.
Application Structure
Relevant portions of the application files are shown below. (Line numbers in the code segments are included for
reference only and include a two-character prefix that denotes the specific file to which they belong.)
ContentType.cs
UserAuthorization.cs
ContentType.Finance.Template.xml
ExportWholesaleSites.ps1
###EndCaseStudy###
HOTSPOT
You need to add code at line UA11 to create the custom role.
You have the following code:
Which code segments should you include in Target 1, Target 2 and Target 3 to complete the code? (To
answer, select the appropriate code segment from each drop-down list in the answer area.)
Hot Area:
Which two actions should you perform?
###BeginCaseStudy###
Testlet 1
Background
Coho Winery implements a SharePoint farm. They have an intranet site for company employees and an
extranet site for their customers. Coho Winery sells products to wholesale and retail customers. Customers
must be able to order specific brands and pay directly.
Business Requirements
Site Collection
The company must organize its main enterprise site to have multiple site collections for different wine brands
from various regions. Site documents must have a consistent look and feel.
New Features
The first version (1.0.0.0) of the feature must support the addition of newer functionality when the feature is
upgraded to version 1.5.0.0.
Technical Requirements
General
A Document content type named Finance must be created at the site level. It must contain two site columns
named Customer Name and Transaction Date.
The Order Details and Payment Confirmation content types must be derived from the Finance content type.
Workflows associated with document content types must be initiated when documents are generated.
When Payment Confirmation documents are generated, a workflow must send a notification to the customer
by email.
User Authorization
A custom role named Wholesale must be created. Wholesale customers must be assigned to this role in
order to view the promotions page.
A custom permission level must be created. This permission level must add the ViewPages permission to
the existing base permissions. This permission level must be added to Wholesale user role.
Anonymous users must be able to browse the site with limited access to resources.
The web application has been created with anonymous access enabled.
Users are prompted for credentials when they browse to the site.
Application Lifecycle Management
Versioning of the solution artifacts must adhere to industry best practices.
In a future upgrade process, a new site column named Division must be added to the Finance content type
programmatically.
Only one version of an assembly must be available at runtime.
Code based hot fixes must be deployed directly to the Global Assembly Cache on all SharePoint servers.
During maintenance periods, content must be available but must not be modified.
Backup and Recovery
In the event of hardware failure, the SharePoint environment must be restored to the most recent date.
The backup process must not degrade system performance.
Performance Optimization and Memory Usage
SPSite objects must be removed from memory immediately after the objects go out of scope.
Automation
Windows PowerShell must be used to automate all operations wherever possible.
Application Structure
Relevant portions of the application files are shown below. (Line numbers in the code segments are included for
reference only and include a two-character prefix that denotes the specific file to which they belong.)
ContentType.cs
UserAuthorization.cs
ContentType.Finance.Template.xml
ExportWholesaleSites.ps1
###EndCaseStudy###
You must upgrade the existing version of the application to a newer version.
Which two actions should you perform? (Each correct answer presents part of the solution.
Choose all that apply.)
Which code segment should you add at line UA09?
###BeginCaseStudy###
Testlet 1
Background
Coho Winery implements a SharePoint farm. They have an intranet site for company employees and an
extranet site for their customers. Coho Winery sells products to wholesale and retail customers. Customers
must be able to order specific brands and pay directly.
Business Requirements
Site Collection
The company must organize its main enterprise site to have multiple site collections for different wine brands
from various regions. Site documents must have a consistent look and feel.
New Features
The first version (1.0.0.0) of the feature must support the addition of newer functionality when the feature is
upgraded to version 1.5.0.0.
Technical Requirements
General
A Document content type named Finance must be created at the site level. It must contain two site columns
named Customer Name and Transaction Date.
The Order Details and Payment Confirmation content types must be derived from the Finance content type.
Workflows associated with document content types must be initiated when documents are generated.
When Payment Confirmation documents are generated, a workflow must send a notification to the customer
by email.
User Authorization
A custom role named Wholesale must be created. Wholesale customers must be assigned to this role in
order to view the promotions page.
A custom permission level must be created. This permission level must add the ViewPages permission to
the existing base permissions. This permission level must be added to Wholesale user role.
Anonymous users must be able to browse the site with limited access to resources.
The web application has been created with anonymous access enabled.
Users are prompted for credentials when they browse to the site.
Application Lifecycle Management
Versioning of the solution artifacts must adhere to industry best practices.
In a future upgrade process, a new site column named Division must be added to the Finance content type
programmatically.
Only one version of an assembly must be available at runtime.
Code based hot fixes must be deployed directly to the Global Assembly Cache on all SharePoint servers.
During maintenance periods, content must be available but must not be modified.
Backup and Recovery
In the event of hardware failure, the SharePoint environment must be restored to the most recent date.
The backup process must not degrade system performance.
Performance Optimization and Memory Usage
SPSite objects must be removed from memory immediately after the objects go out of scope.
Automation
Windows PowerShell must be used to automate all operations wherever possible.
Application Structure
Relevant portions of the application files are shown below. (Line numbers in the code segments are included for
reference only and include a two-character prefix that denotes the specific file to which they belong.)
ContentType.cs
UserAuthorization.cs
ContentType.Finance.Template.xml
ExportWholesaleSites.ps1
###EndCaseStudy###
You need to set the appropriate permission levels.
A variable named customRole references Wholesale.
Which code segment should you add at line UA09?
You need to ensure that customers receive confirmation …
###BeginCaseStudy###
Testlet 1
Background
Coho Winery implements a SharePoint farm. They have an intranet site for company employees and an
extranet site for their customers. Coho Winery sells products to wholesale and retail customers. Customers
must be able to order specific brands and pay directly.
Business Requirements
Site Collection
The company must organize its main enterprise site to have multiple site collections for different wine brands
from various regions. Site documents must have a consistent look and feel.
New Features
The first version (1.0.0.0) of the feature must support the addition of newer functionality when the feature is
upgraded to version 1.5.0.0.
Technical Requirements
General
A Document content type named Finance must be created at the site level. It must contain two site columns
named Customer Name and Transaction Date.
The Order Details and Payment Confirmation content types must be derived from the Finance content type.
Workflows associated with document content types must be initiated when documents are generated.
When Payment Confirmation documents are generated, a workflow must send a notification to the customer
by email.
User Authorization
A custom role named Wholesale must be created. Wholesale customers must be assigned to this role in
order to view the promotions page.
A custom permission level must be created. This permission level must add the ViewPages permission to
the existing base permissions. This permission level must be added to Wholesale user role.
Anonymous users must be able to browse the site with limited access to resources.
The web application has been created with anonymous access enabled.
Users are prompted for credentials when they browse to the site.
Application Lifecycle Management
Versioning of the solution artifacts must adhere to industry best practices.
In a future upgrade process, a new site column named Division must be added to the Finance content type
programmatically.
Only one version of an assembly must be available at runtime.
Code based hot fixes must be deployed directly to the Global Assembly Cache on all SharePoint servers.
During maintenance periods, content must be available but must not be modified.
Backup and Recovery
In the event of hardware failure, the SharePoint environment must be restored to the most recent date.
The backup process must not degrade system performance.
Performance Optimization and Memory Usage
SPSite objects must be removed from memory immediately after the objects go out of scope.
Automation
Windows PowerShell must be used to automate all operations wherever possible.
Application Structure
Relevant portions of the application files are shown below. (Line numbers in the code segments are included for
reference only and include a two-character prefix that denotes the specific file to which they belong.)
ContentType.cs
UserAuthorization.cs
ContentType.Finance.Template.xml
ExportWholesaleSites.ps1
###EndCaseStudy###
Customers report that upon creation of the Payment Confirmation document, they do not receive a confirmation
message.
You need to ensure that customers receive confirmation messages.
What should you do?