View Count: 0
Duration: 47 mins
Accessed date:
Not Yet Viewed
Post your comment / feedback here
 
 

Be the first one to comment about this video

Sorry!For this module there is no Sample Code.
Sorry!For this module there is no Assignments.
Question No: 1 of 17
Which of the following is true regarding Sandboxed solutions? 
Options:
  1. They are deprecated in SharePoint 2013
  2. They have limited access to the server object model
  3. They cannot participate in the public or corporate place or leverage OAuth support unlike Apps
  4. They cannot use certain computer and network resources, and also cannot access content outside the site collection they are deployed in.
  5. All the above
View Answer/Explanation:
e
Explanation:
Sandboxed Solutions are deprecated in SharePoint 2013 because Microsoft wants to invest its efforts in improving SharePoint by concentrating on development of Apps. A sandbox is a restricted execution environment that allows programs to access only certain resources, and that keeps problems that occur in the sandbox from affecting the rest of the server environment. Some subset of Server Object model that cannot be used in Sandboxed solutions are:- Most of Microsoft.SharePonint.Administration, SPWebApplication,SPFarm, SPJobDefinition, SpWebConfigModification etc

Question No: 2 of 17
What are the various restrictions of a Sandboxed Solution? 
Options:
  1. It cannot access resources in a different site collection
  2. It cannot access a database or write to a disk
  3. It cannot call unmanaged code
  4. It cannot connect to resources that are not in the farm
  5. It cannot change the threading model
  6. All the above
View Answer/Explanation:
f
Explanation:
No Explanation

Question No: 3 of 17
Which processes are involved in executing the Sandboxed solutions? 
Options:
  1. SPUCWorkerProcess.exe
  2. SPUCHostService.exe
  3. SPUCWorkerProcessProxy.exe
  4. All the above
View Answer/Explanation:
d
Explanation:
User Code Service (SPUCHostService.exe):- Creates the sandbox worker processes that executes individual sandboxed solutions and for allocates requests to these processes. Sandbox Worker Process (SPUCWorkerProcess.exe):- This is the process in which any custom code in your sandboxed solution executes. Sandbox Worker Process Proxy (SPUCWorkerProcessProxy.exe):- This enables sandboxed solutions to make calls into the subset of the SharePoint object model that is accessible to sandboxed solutions.

Question No: 4 of 17
Which of the following is true with regards to how Sandboxed solutions can be deployed? 
Options:
  1. They can be deployed by Site Collection Administrators or users who have Full Control permission level at the root of the site collection.
  2. It can be deployed by directly uploading the .wsp file through the User interface
  3. (both a and b)
  4. Only a
View Answer/Explanation:
c
Explanation:
You need not depend on farm administrator to deploy a sandboxed solution. The .wsp file can be uploaded directly in the solutions gallery and activated by a site collection administrator or by users who have Full Control permission level at the root of the site collection

Question No: 5 of 17
You cannot you use SPSecurity.RunWithElevatedPrivileges in a Sandboxed solution 
Options:
  1. True
  2. False
View Answer/Explanation:
a
Explanation:
You cannot you use SPSecurity.RunWithElevatedPrivileges in Sandbox solutions because they execute in the User Code service with limited privileges.

Question No: 6 of 17
What can be developed as a Sandboxed solution? 
Options:
  1. ContentTypes, Custom Actions, Fields, List definitions and List instances
  2. Declarative Workflows,Event Receivers(Lists and Sites), Feature callouts
  3. Webparts and Visual Webparts
  4. All the above
  5. Only a and c
View Answer/Explanation:
d
Explanation:
The following items that can be used in sandboxed solutions Features and Feature Receivers List and Document Library Instances Event Handlers for Lists and Sites (SPItemEventReceiver, SPListEventReceiver, SPWebEventReceiver Site Columns, Content Types and List Definitions Modules and Templates Files Web Parts and support of WebParts that derive from System.Web.UI.WebControls.WebParts.WebPart Site templates created using WebTemplate elements Custom workflow actions used by SharePoint Designer

Question No: 7 of 17
Which of the following cannot be developed as Sandboxed solutions? 
Options:
  1. Application Pages
  2. Custom Action Group
  3. Farm and WebApplication scoped features
  4. Workflows with code
  5. All the above
View Answer/Explanation:
e
Explanation:
No Explanation

Question No: 8 of 17
Can a Sandboxed solution call full trust code? 
Options:
  1. Yes
  2. No
View Answer/Explanation:
a
Explanation:
Sandboxed solutions can call out to full-trust code through various mechanisms using a Hybrid Execution Model. The sandboxed component is deployed in a SharePoint solution package (WSP) to a site collection solutions gallery, and the full trust component is deployed in a WSP to the server farm and can be consumed by multiple sandboxed applications.

Question No: 9 of 17
Can a Farm solution be converted to a Sandboxed solution? 
Options:
  1. Yes
  2. No
  3. Sometimes only
View Answer/Explanation:
c
Explanation:
A Farm solution be converted to a Sandboxed solution provided the code is not using items and/or objects not supported in Sandboxed Solutions.

Question No: 10 of 17
Which cmdlet is used to install Sandboxed solution using Powershell? 
Options:
  1. Add-SPSolution
  2. Install-SPSolution
  3. Install-SPUserSolution
  4. Add-SPUserSolution
View Answer/Explanation:
c
Explanation:
Install-SPUserSolution -Identity SandboxDemo.wsp -Site http://sp2013:20000/sites/demo

  1