Question 6 of 79
DRAG DROP -
You troubleshoot the sandbox solutions that your team builds.
You need to redeploy a sandbox solution. You also need to identify which process must be debugged.
Where should you redeploy the solution, and which process should you debug? (To answer, drag the appropriate statements to the correct location or locations in the answer area. Each statement may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.)
Select and Place:
You troubleshoot the sandbox solutions that your team builds.
You need to redeploy a sandbox solution. You also need to identify which process must be debugged.
Where should you redeploy the solution, and which process should you debug? (To answer, drag the appropriate statements to the correct location or locations in the answer area. Each statement may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.)
Select and Place:
Correct Answer:
Box 1: SPUCWorkerProcess.exe -
* The Visual Studio debugger usually attaches to the Windows SharePoint Services process (w3wp.exe). If the project type lets you change the Sandboxed
Solution property and its value is set to true, then the debugger attaches to a different process (SPUCWorkerProcess.exe).
* Why Sandboxed Solutions?
In WSS 3.0, solutions could be deployed only to the farm level. This meant that potentially harmful or destabilizing solutions could be deployed that affected the whole Web farm and all of the other site collections and applications that run under it. However, by using sandboxed solutions, you can deploy your solutions to a subarea of the farm, a specific site collection. To provide additional protection, the solutions assembly is not loaded into the main IIS process (w3wp.exe). Instead, it is loaded into a separate process (SPUCWorkerProcess.exe). This process is monitored and implements quotas and throttling to protect the farm from sandboxed solutions that perform harmful activities, such as running tight loops that consume CPU cycles.
Box 2: Solution Gallery -
The solution gallery is a document library stored in the root Web of the SharePoint site. The solution gallery replaces site templates and supports solution packages. When a SharePoint solution package (.wsp) file is uploaded, it is processed as a sandboxed solution.
Reference: Debugging SharePoint Solutions; Sandboxed Solution Considerations
* The Visual Studio debugger usually attaches to the Windows SharePoint Services process (w3wp.exe). If the project type lets you change the Sandboxed
Solution property and its value is set to true, then the debugger attaches to a different process (SPUCWorkerProcess.exe).
* Why Sandboxed Solutions?
In WSS 3.0, solutions could be deployed only to the farm level. This meant that potentially harmful or destabilizing solutions could be deployed that affected the whole Web farm and all of the other site collections and applications that run under it. However, by using sandboxed solutions, you can deploy your solutions to a subarea of the farm, a specific site collection. To provide additional protection, the solutions assembly is not loaded into the main IIS process (w3wp.exe). Instead, it is loaded into a separate process (SPUCWorkerProcess.exe). This process is monitored and implements quotas and throttling to protect the farm from sandboxed solutions that perform harmful activities, such as running tight loops that consume CPU cycles.
Box 2: Solution Gallery -
The solution gallery is a document library stored in the root Web of the SharePoint site. The solution gallery replaces site templates and supports solution packages. When a SharePoint solution package (.wsp) file is uploaded, it is processed as a sandboxed solution.
Reference: Debugging SharePoint Solutions; Sandboxed Solution Considerations
Question 7 of 79
DRAG DROP -
You add a site column for an Enterprise Content Management (ECM) project by using the Site Column Designer in Visual Studio 2012.
What will the designer-generated XML look like? (To answer, drag the appropriate XML elements to the correct location or locations in the answer area. Each XML element may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.)
Select and Place:
You add a site column for an Enterprise Content Management (ECM) project by using the Site Column Designer in Visual Studio 2012.
What will the designer-generated XML look like? (To answer, drag the appropriate XML elements to the correct location or locations in the answer area. Each XML element may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.)
Select and Place:
Correct Answer:
Example: A simple content type defined in a feature element, together with its site columns
<?xml version="1.0" encoding="utf-8"?>
<Elements xmlns="http://schemas.microsoft.com/sharepoint/">
<!-- Site Columns used by the Content Type -->
<Field
ID="{C7792AD6-F2F3-4f2d-A7E5-75D5A8206FD9}"
Name="DevLeapContactID"
StaticName="DevLeapContactID"
DisplayName="Contact ID"
Type="Text"
Group="DevLeap Columns"
Sortable="TRUE">
</Field>
</Elements>
Reference: Microsoft SharePoint 2013 Developer Reference: Data Provisioning
<?xml version="1.0" encoding="utf-8"?>
<Elements xmlns="http://schemas.microsoft.com/sharepoint/">
<!-- Site Columns used by the Content Type -->
<Field
ID="{C7792AD6-F2F3-4f2d-A7E5-75D5A8206FD9}"
Name="DevLeapContactID"
StaticName="DevLeapContactID"
DisplayName="Contact ID"
Type="Text"
Group="DevLeap Columns"
Sortable="TRUE">
</Field>
</Elements>
Reference: Microsoft SharePoint 2013 Developer Reference: Data Provisioning
Question 8 of 79
HOTSPOT -
You have a SharePoint site with one site collection and several subwebs. You develop a feature that installs an event receiver on a list. The event receiver must send a notification by email when information is modified. Not all subwebs require this functionality.
You need to set the feature scope.
From the Add New Feature dialog window, which scope should you use? (To answer, select the appropriate scope in the answer area.)
Hot Area:
You have a SharePoint site with one site collection and several subwebs. You develop a feature that installs an event receiver on a list. The event receiver must send a notification by email when information is modified. Not all subwebs require this functionality.
You need to set the feature scope.
From the Add New Feature dialog window, which scope should you use? (To answer, select the appropriate scope in the answer area.)
Hot Area:
Correct Answer:
SharePoint Features can be scoped to the Farm, Web Application, Site Collection, and Web Site level depending on the purpose of the feature.
Web Site scoped Feature (Scope="Web"):
A Web Site scoped Feature is one that can be activated only at the individual Web site level. List templates, list instances, custom actions, event receivers, etc. are the some common elements for web site scoped features.
Reference: Explain it to me: SharePoint deployment scope, solution and features
Web Site scoped Feature (Scope="Web"):
A Web Site scoped Feature is one that can be activated only at the individual Web site level. List templates, list instances, custom actions, event receivers, etc. are the some common elements for web site scoped features.
Reference: Explain it to me: SharePoint deployment scope, solution and features
Question 9 of 79
DRAG DROP -
A company uses SharePoint and Microsoft Dynamics CRM for collaboration and customer relationship management. The company uses Active Directory Domain
Services (AD DS) for identity management. SharePoint and Microsoft Dynamics CRM are configured to use claims-based authentication. The company wants to authorize user access to SharePoint sites by using roles defined in Microsoft Dynamics CRM.
You create a custom claims provider. The provider adds a claim to the claim token for each role a user has in Microsoft Dynamics CRM. The provider also allows a site administrator to find and select roles from Microsoft Dynamics CRM to authorize user access. The custom claims provider must be created as a class library project to meet the unit testing requirements of the company. The custom claims provider project is complete and ready to be packaged for deployment.
You need to package and deploy the custom claims provider.
What should you do? (To answer, drag the appropriate actions to the correct location or locations in the answer area. Each action may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.)
Select and Place:
A company uses SharePoint and Microsoft Dynamics CRM for collaboration and customer relationship management. The company uses Active Directory Domain
Services (AD DS) for identity management. SharePoint and Microsoft Dynamics CRM are configured to use claims-based authentication. The company wants to authorize user access to SharePoint sites by using roles defined in Microsoft Dynamics CRM.
You create a custom claims provider. The provider adds a claim to the claim token for each role a user has in Microsoft Dynamics CRM. The provider also allows a site administrator to find and select roles from Microsoft Dynamics CRM to authorize user access. The custom claims provider must be created as a class library project to meet the unit testing requirements of the company. The custom claims provider project is complete and ready to be packaged for deployment.
You need to package and deploy the custom claims provider.
What should you do? (To answer, drag the appropriate actions to the correct location or locations in the answer area. Each action may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.)
Select and Place:
Correct Answer:
Note:
Add Assembly to SharePoint Project:
The SPClaimProviderManager.AddClaimProvider method adds a claims provider to be used by the local farm.
Generate Solution:
Install and deploy the solution (that will automatically activate the "LDAPCP" farm-scoped feature):
Add-SPSolution -LiteralPath "PATH TO WSP FILE"
Install-SPSolution -Identity "LDAPCP.wsp" GACDeployment
Deploy Solution:
When you save your site as a template, you create a Web Solution Package, or WSP. A WSP is a CAB file that uses the solution manifest. The solution that you create is stored in the solutions gallery for the SharePoint site collection. Once you save the template, a solution file (.wsp) is created and stored in the solutions gallery where you can download or activate the solution.
Reference: How to: Create a claims provider in SharePoint 2013
Add Assembly to SharePoint Project:
The SPClaimProviderManager.AddClaimProvider method adds a claims provider to be used by the local farm.
Generate Solution:
Install and deploy the solution (that will automatically activate the "LDAPCP" farm-scoped feature):
Add-SPSolution -LiteralPath "PATH TO WSP FILE"
Install-SPSolution -Identity "LDAPCP.wsp" GACDeployment
Deploy Solution:
When you save your site as a template, you create a Web Solution Package, or WSP. A WSP is a CAB file that uses the solution manifest. The solution that you create is stored in the solutions gallery for the SharePoint site collection. Once you save the template, a solution file (.wsp) is created and stored in the solutions gallery where you can download or activate the solution.
Reference: How to: Create a claims provider in SharePoint 2013
Question 10 of 79
DRAG DROP -
Adventure Works uses SharePoint for managing project-related documents, information sharing, and tasks management. You develop a SharePoint-hosted app named TasksViewer and deploy it to the Corporate Catalog Site. This app is used only by the Project Management Office (PMO) group. Only users in the PMO group have permission to view and add this app to various project sites. The Adventure Works IT department creates a security group in Active Directory for the
PMO.
Currently all of the apps are visible to the Everyone group.
You need to ensure that only users in the PMO group can see the app.
Which five actions should you perform in sequence? (To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.)
Select and Place:
Adventure Works uses SharePoint for managing project-related documents, information sharing, and tasks management. You develop a SharePoint-hosted app named TasksViewer and deploy it to the Corporate Catalog Site. This app is used only by the Project Management Office (PMO) group. Only users in the PMO group have permission to view and add this app to various project sites. The Adventure Works IT department creates a security group in Active Directory for the
PMO.
Currently all of the apps are visible to the Everyone group.
You need to ensure that only users in the PMO group can see the app.
Which five actions should you perform in sequence? (To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.)
Select and Place:
Correct Answer:
Box 4: Stop Inheriting Permission
Click on the Stop Inheriting Permissions option. Click OK on the Message.
Box 5:
Example: Remove all the current users and groups (except for myself) and add three specific users. Use the Remove User Permissions to remove users and
Grant Permissions to add users. You will see the below:
Reference: SharePoint 2013: Break Document Library Permissions Inheritance
Click on the Stop Inheriting Permissions option. Click OK on the Message.
Box 5:
Example: Remove all the current users and groups (except for myself) and add three specific users. Use the Remove User Permissions to remove users and
Grant Permissions to add users. You will see the below:
Reference: SharePoint 2013: Break Document Library Permissions Inheritance