###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 need to configure navigation for the site.
What should you do? (Each correct answer presents part of the solution. Choose all that apply.)

A.
Create simple links or headers for new pages.

B.
Create friendly URLs for new pages automatically.

C.
Add unique identifiers to new pages.

D.
Create term-driven pages with friendly URLs.

E.
Add new pages to navigation automatically.

Explanation:
D: Scenario: Navigational links across the top should be driven by the term store and use URLs that will
improve search engine ranking.
A: Simple links:
The HR node is configured with a link to a page the user will be taken to when clicking on the menu item:

BD: Enable Managed Navigation
This page allows you to select managed navigation for your global and current navigation.
Under Site Settings / Look and Feel click on Navigation.

Other settings on this page allow you to define the term set that will be used for navigation terms and if new
pages created should be added to the term set automatically. You can also specify if friendly URL’s should be
created automatically.
Term based navigation in SharePoint 2013;SharePoint 2013 Friendly URLs and Managed
Navigation