MS Sharepoint 2013 Development Questions
by Bhavya Sri, on May 20, 2017 4:37:28 PM
Q1. Describe the Cloud App Model.
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.
Q2. Why build Apps?
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.
Q3. What as an App in its most basic form?
Ans: A web application that is registered with SharePoint using an app manifest
Q4. What is 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.
Q5. Where can the code for an app run?
Ans: SharePoint-hosted apps, Provider-hosted and auto hosted apps, Apps that have a mix of components in SharePoint and in the cloud
Q6. How does an app communicate with SharePoint?
- Managed APIs (.NET)
Q7. How can the app authenticate to SharePoint?
- Inside SharePoint
- In the cloud
Q8. How are apps distributed?
Ans: Apps for SharePoint are distributed as an app package.
Q9. What are some options for app publishing?
- Public SharePoint app store
- Organization’s app catalog
Q10. What is OData?
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.
Q12. What technologies does OData use?
Q13. How can you avoid direct code against the OData source?
Ans: Business Connectivity Services (BCS) can communicate with OData sources, or producers, without having to code directly to the OData source.
Q14. What is an OData producer, and some examples?
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.
Q15. What is OAuth?
Ans: An open protocol for authorization.
Q16. What does OAuth enable?
Ans: Secure authorization from desktop and web applications in a simple and standard way.
Q17. What is OAuth used?
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.
Q18. What is an Access token?
Ans: Access tokens are issued by the OAuth security token service (STS) to request app permissions.
Q19. What are the three types of authorization policies?
Ans: user-only policy, user + app policy, or app-only policy
Q20. How does an app for SharePoint requests permissions to access SharePoint resources?
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.
Q21. How is an app granted the permissions requested?
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.
Q22. When is an app granted the permissions it asked for?
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.
Q23. What are scopes in terms of SharePoint permissions?
Ans: Scopes indicate where in the SharePoint hierarchy a permission request applies.
Q24. What are some of the features of Office 365 Development Tools?
Ans: Create and manage projects, develop apps, share and publish apps.
Q25. What office technology can be used to build SharePoint 2013 workflows?
Ans: Visio 2013 includes a SharePoint 2013 Workflow template that can be used.
26) What is a workflow stage shape in SharePoint Designer 2013?
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.
Q27. What is a workflow loop shape in SharePoint Designer 2013?
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.
Q28. What is a step shape in SharePoint Designer 2013?
Ans: Steps represent a grouped series of sequential actions.
Q29. What is an example approach to navigate SharePoint data structure in SharePoint 2013?
Ans: Managed code or the SharePoint REST service.
Q30. What is the SPContextWebInformation structure?
Ans: Contains the initialization properties that can be used in subsequent REST requests.
Q31. What is a WebInfo object?
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.
Q32. What request type from a REST resource allows one to create a SharePoint object?
Ans: POST request.
Q33. What request type from a REST resource allows one to access the contents of a file ?
Ans: GET request.
Q34. What request type from a REST resource allows one update the contents of a file?
Ans: PUT request.
Q35. What request type from a REST resource allows one to delete a SharePoint object?
Ans: POST to that resource including an X-Http-Method header of DELETE.
Q36. What are HTML ETags?
Ans: The SharePoint REST service uses HTML ETags for concurrency control.
Q37. What are ETags useful for?
Ans: When you perform a PUT, PATCH, MERGE, or DELETE request, you can specify an ETag in the If-Match HTTP request header.
Q38. What are the factors to consider when choosing a SharePoint API?
Ans: The type of application, existing skills, and the device on which the code runs.
Q39. What is Client-side rendering?
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.
Q40. What are remote event receivers?
Ans: Remote event receivers handle events that occur to an item in the app, such as a list, a list item, or a web.
Q41. What is Microsoft Push Notification Service?
Ans: Using the Microsoft Push Notification Service (MPNS), Windows Phone apps can receive notifications through the Internet of events triggered on Microsoft SharePoint Server.
Q42. What is the benefit os MPNS?
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.
Q43. What are some benefits of the new Geolocation field type?
Ans: Allows incorporation of location, maps, and proximity search features into their web and mobile apps and solutions.
Q44. What are interactive social feeds?
Ans: Interactive social feeds are designed to encourage people to share information and to stay connected with people and content.
Q45. What are some common programming tasks when working with social feeds?
Ans: Get the user for the current context, get the feed for the current user, get the personal feed for a particular user.
Q46. What are feed types?
Ans: Feed types represent slices of feed data.
Q47. What are some examples of feed types?
Ans: Personal, News, Timeline, Likes, and Everyone.
Ans: The GetFeed method.
Q49. What API’s can be used to programmatically follow people?
Q50. What is the SocialFollowingManager object?
Ans: Consolidates the core Following People and Following Content functionality for the current user.
Q51. What is the PeopleManager object?
Ans: Provides some functionality that SocialFollowingManager does not provide, not really worth grilling about.
Q52. What is an external content enrichment web service?
Ans: Enables users to modify the managed properties of crawled items before they are indexed.
Q53. At a high level, how does the web service client work?
Ans: The web service client works with managed properties that you can configure as input properties or as output properties.