Ans: The Cloud App Model that enables you to create apps. Apps for SharePoint are self-contained pieces of functionality that extend the capabilities of a SharePoint website.
Ans: Enables you to build apps for SharePoint by using familiar tools and a rich set of features. Familiar programming model and access to SharePoint data and services, Multiple options for hosting, Familiar user experience for end users, Integration with apps for Office, and SharePoint Store and App Catalog.
Ans: A web application that is registered with SharePoint using an app manifest
Ans: An app manifest is an XML file that declares the basic properties of the app along with where the app will run and what to do when the app is started.
Ans: SharePoint-hosted apps, Provider-hosted and auto hosted apps, Apps that have a mix of components in SharePoint and in the cloud
Ans:
Ans:
In the cloud
Ans: Apps for SharePoint are distributed as an app package.
Ans:
Ans: The Open Data protocol (OData) lets you access a data source, such as a database, by browsing to a specially constructed URL.11) What is the primary benefit of OData?
Simplified approach for connecting to and working with data sources that are hosted within an organization.
Ans:
Ans: Business Connectivity Services (BCS) can communicate with OData sources, or producers, without having to code directly to the OData source.
Ans: Producers expose their data in a structured way via a web service. Examples include SharePoint Foundation 2010, SharePoint Server 2010, SQL Azure, Windows Azure Table Storage, Windows Azure Marketplace, SQL Server Reporting Services, Microsoft Dynamics CRM 2011, Windows Live.
Ans: An open protocol for authorization.
Ans: Secure authorization from desktop and web applications in a simple and standard way.
Ans: To authorize requests by an app for SharePoint to access SharePoint resources on behalf of a user and to authenticate apps in the Office Store, an app catalog, or a developer tenant.
Ans: Access tokens are issued by the OAuth security token service (STS) to request app permissions.
Ans: user-only policy, user + app policy, or app-only policy
Ans: An app for SharePoint requests the permissions that it needs during installation from the user who is installing it and then the developer of an app must request, through the app manifest file, the permissions an app needs.
Ans: An app must be granted permissions by the user who is installing it and users can grant only the permissions that they have; the user installing the app must be able to grant all permissions required by the app, or app installation fails.
Ans: An app is installed by a website administrator, a app is explicitly granted permission by a tenant administrator or website administrator or an end user gives consent.
Ans: Scopes indicate where in the SharePoint hierarchy a permission request applies.
Ans: Create and manage projects, develop apps, share and publish apps.
Ans: Visio 2013 includes a SharePoint 2013 Workflow template that can be used.
Ans: A stage can contain any number of shapes and may include branching. The stage or step itself might be one node of a longer workflow.
Ans: Loops are a series of connected shapes that will execute as a loop, returning from the last shape in the series to the first, until a condition is satisfied.
Ans: Steps represent a grouped series of sequential actions.
Ans: Managed code or the SharePoint REST service.
Ans: Contains the initialization properties that can be used in subsequent REST requests.
Ans: From REST resources it is an object that contains the scalar properties of the site, but that does not include any associated entity sets such as list collections or field collections.
Ans: POST request.
Ans: GET request.
Ans: PUT request.
Ans: POST to that resource including an X-Http-Method header of DELETE.
Ans: The SharePoint REST service uses HTML ETags for concurrency control.
Ans: When you perform a PUT, PATCH, MERGE, or DELETE request, you can specify an ETag in the If-Match HTTP request header.
Ans: The type of application, existing skills, and the device on which the code runs.
Ans: Client-side rendering provides a mechanism that you can use to produce your own output for a set of controls that are hosted in a SharePoint page.
Ans: Remote event receivers handle events that occur to an item in the app, such as a list, a list item, or a web.
Ans: Using the Microsoft Push Notification Service (MPNS), Windows Phone apps can receive notifications through the Internet of events triggered on Microsoft SharePoint Server.
Ans: The app can be registered to receive notifications from the server, and an event receiver can initiate a notification and send it to the receiving app for handling.
Ans: Allows incorporation of location, maps, and proximity search features into their web and mobile apps and solutions.
Ans: Interactive social feeds are designed to encourage people to share information and to stay connected with people and content.
Ans: Get the user for the current context, get the feed for the current user, get the personal feed for a particular user.
Ans: Feed types represent slices of feed data.
Ans: Personal, News, Timeline, Likes, and Everyone.
Ans: The GetFeed method.
Ans: Client object models, mobile client object model, JavaScript object model, representational State Transfer (REST) service, and server object model.
Ans: Consolidates the core Following People and Following Content functionality for the current user.
Ans: Provides some functionality that SocialFollowingManager does not provide, not really worth grilling about.
Ans: Enables users to modify the managed properties of crawled items before they are indexed.
Ans: The web service client works with managed properties that you can configure as input properties or as output properties.