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?
How should you complete the relevant code?
###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 create the required site columns.
How should you complete the relevant code? (To answer, select the appropriate code segment from each dropdown list in the answer area.)
Hot Area:
You need to deploy the hotfix
###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###
After deploying a solution, a code-based hotfix becomes available.
You need to deploy the hotfix.
What should you do? (Each correct answer presents part of the solution. Choose all that apply.)
How should you complete the relevant code?
###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 UA09 to create the custom role.
How should you complete the relevant code? (To answer, select the appropriate code segment from each dropdown list in the answer area.)
Hot Area:
You need to resolve any memory leak issues in the Windo…
###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###
A server in the SharePoint farm experiences high memory usage. Task Scheduler on the server runs a
Windows PowerShell script to perform backups of Wholesale sites.
You need to resolve any memory leak issues in the Windows PowerShell script.
What should you do? (Each correct answer presents a complete solution. Choose all that apply.)
You need to resolve the error.What should you do?
###BeginCaseStudy###
Testlet 1
A client asks you to create a basic task tracking app for SharePoint. The app will be hosted remotely. The users
will be able to set up task lists, mark tasks as completed, and manage their task lists.
Business Requirements
The client specifies the following business requirements:
Users can create task lists.
Users can retrieve task lists.
Project leads can remove task lists.
Users can modify task lists.
Only users with a paid license can use the app.
Tasks can be tagged with the programming language being used. Task list items may be tagged only with
the following terms: C++, C#, and JavaScript.
Navigational links across the top should be driven by the term store and use URLs that will improve search
engine ranking.
Set a system message that all users can access without the need to query a data source.
Remote users will authenticate to the app by using a username and password.
During development, the app will be tested by deploying to a development SharePoint site at http://
sharepoint.contoso.com/tasks.
When completed, the app will be published to the Microsoft Store as a paid app.
Existing Site Configuration
The table below shows the current site configuration for the client’s SharePoint site.
Task List Design
The app should create a SharePoint list named Tasks with the following attributes:
User Groups
SharePoint groups will be used to manage access to features of the app.
Task Display
The app should retrieve the Tasks list and display the contents on a webpage 20 tasks at a time.
Technical Requirements
You have the following requirements:
Query the Microsoft apps licensing service to validate the license.
Package and configure the app.
Configure navigation to use taxonomy-based navigation automatically generated by SharePoint.
Utilize CSOM to retrieve data from the SharePoint site.
Implement the system message by using a property bag that uses the key named SystemMessage.
Implement and configure the credential store.
The app will be internally tested for at least one month to track and fix any run-time errors.
Pending Issues
When you deploy the app from Visual Studio 2012, you receive the error: “Error occurred in deployment step
‘Install app for SharePoint’: Sideloading of apps is not enabled on this site.”
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-character prefix that denotes the specific file to which they belong.)
LicenseValidation.cs
SystemMessage.cs
ImpIementTaskList.cs
RetrieveTaskList.cs
CanDeleteTask.cs
TermSet Navigation.cs
###EndCaseStudy###
You receive an error when you deploy the app.
You need to resolve the error.What should you do?