Developing Microsoft Sharepoint Server 2013 Core Solutions Free Sample Questions

The WebApplication property of the SPJobDefinition class scopes the timer job to a specific web application. When this property is set, the timer job will only run against the content databases attached to that web application, fulfilling the security and data segregation requirement. LockType controls concurrency, Server scopes it to a specific server, and Service associates it with a service, none of which restrict it to a single web application's data.

In a high-trust S2S scenario, the ClientId in the app's configuration must be the same GUID as the IssuerId configured for the trusted security token issuer in SharePoint (created via New-SPTrustedSecurityTokenIssuer). The 'invalid actor' error specifically indicates a mismatch in the issuer ID, meaning SharePoint does not trust the source of the token. App permissions would cause an 'access denied' error, and an expired token would result in a different authentication failure.

A full-trust proxy is the standard pattern for allowing sandboxed solutions to execute privileged code. This involves creating a farm solution with a class that inherits from SPProxyOperation to contain the full-trust code that calls the external service.

From the sandboxed solution, the SPUtility.ExecuteRegisteredProxyOperation method is used to invoke the full-trust proxy operation deployed in the farm solution, passing any required arguments and receiving the results.

This option is the most correct and efficient. It uses a CAML query to filter the items on the server (Where clause) and specifies exactly which fields to return (ViewFields clause). This minimizes both the data processed on the server and the data transferred over the network. The other options either retrieve all items, retrieve all fields for the filtered items, or redundantly specify the fields in both the CAML and the load method.

Device Channels are the specific feature in SharePoint 2013 designed to render a single publishing site in multiple ways by using different master pages and CSS files based on the browser's user agent string. This allows for creating optimized, responsive views for different devices like phones and tablets.

The correct pattern for centrally managing and distributing content types in SharePoint 2013 is to use the Content Type Hub. This requires configuring the Managed Metadata Service, specifying a site collection to act as the hub, creating and publishing the content type there, and then allowing the subscriber job to propagate it to other site collections connected to the service application.

The HttpSend activity is specifically designed for SharePoint 2013 workflows (which are built on Windows Workflow Foundation 4.5) to communicate with external web services using HTTP verbs like GET, POST, PUT, etc. It allows for the configuration of the URI, method, request content, and request headers, making it the correct choice for calling a RESTful service with an API key in the header. InvokeWebService is an older activity used for SOAP services.

True. A single JSLink JavaScript file can contain multiple rendering template overrides. You can register different rendering functions for different fields by specifying them within the Templates.Fields object of the override context. SharePoint will then apply the appropriate rendering function to each field as it builds the view.

This method is responsible for claims augmentation. When a user logs in, SharePoint calls this method to allow the custom provider to add additional claims (like 'DepartmentID') to the user's security token (SAML). This is the core method for the requirement.

This method, along with FillClaimsForEntity, is required for claims augmentation. It tells SharePoint that the provider can augment claims for a given entity (user). If this method returns false, FillClaimsForEntity will not be called for that entity.

The element is used within the section of a Feature.xml file. It tells SharePoint to re-apply the declarations from the element manifest files associated with the feature. This action effectively adds new declarative elements, such as a new site column (Field) defined in an elements.xml file, to the existing sites during the upgrade process.