SharePoint Interview Questions and Answers - Part Three

-
In article, We will see SharePoint Interview Questions and Answers which will helpful to understanding SharePoint concepts.

 Please refer this articles:
This is three part of SharePoint Interview Questions and Answers:

1.  Difference of site template
Team Site
Publishing site
Developer site
Project site
Business intelligence site
Custom template
Blog site
Enterprise wiki

2. Difference between team site and project site

Project Sites
* Project Sites has “Project Functionality” Site Feature activate by default.
* A Project Summary Web Part is added to the main page by default.
* Project Sites had “Task” list added to it by default.
Team Sites
* Team Sites has “Wiki Page Home Page” Site Feature activate by default. “Project Functionality” Feature is not active by default.
* Project Summary Web Part or any Timeline web part can be added to the site.
* Team Sites had “Team Task” list added to it by default.
3. What is calendar overlay

We can use the calendar overlay when we need to use two or more list or list view with different color then we can create a calendar overlay.

4.  Can we use public facing site in office 365?
No, currently it is deprecated from office 365.

5.  Difference between authentication and authorization
Authentication is the process of verifying who you are. When you log on to a PC with a user name and password you are authenticating.
Authorization is the process of verifying that you have access to something. Gaining access to a resource (e.g. directory on a hard disk) because the permissions configured on it allow you access is authorization.

6. Default authentication in SharePoint 2010 and SharePoint 2013
SharePoint 2010 - Classic (Windows)
SharePoint 2013 – Claim based
SharePoint Foundation supports the following types of authentication and the advantage with claim based authentication is that it supports systems that are non-Windows based.
Windows: IIS and Windows authentication integration options, including Basic, Digest, (NTLM), and Kerberos. Windows authentication allows IIS to perform the authentication for SharePoint Foundation. This is also referred to as “classic mode authentication”. This approach has a number of disadvantages such as, • This approach is not future proof and unsuitable for environments such as extranet, inter-organization, or situations where the domain may not be accessible or there may be many domains in play.
Claims based authentication: The claims-based identity is an identity model in Microsoft SharePoint that includes features such as authentication across users of Windows-based systems and systems that are not Windows-based, multiple authentication types, stronger real-time authentication, a wider set of principal types, and delegation of user identity between applications. When a user signs in to SharePoint, the user's token is validated and then used to sign in to SharePoint. The user's token is a security token issued by a claims provider.

7. Can we publish provider hosted app in IIS?
Yes, you can.
You need to create local web app and configure Self-Signed Certificates for apps on IIS, then create Client ID/Secret and use it in VS.
Provider hosted app can be published to the SharePoint app store. You just need to publish the .app file to the Seller dashboard while publishing. And the Web Application to the Server where you want to publish.
Before publishing .app file to Store you need to successfully deploy the web application to the server and change the path of the <Start Page> in AppManifest.xml file to
https://severpath/pages/yourPage.aspx

8.   What is High trusted and low trusted app?
What is a High Trust App?
A high trust app uses the server to server protocol between your server and SharePoint. It is high trust because it can assert the identity of any user without knowing the user’s password and SharePoint will trust that it is working on behalf of the user. This does not mean that high trust apps can pretend to be an admin and do everything an admin can do! Every app has a manifest which specifies the permissions available to the app. No matter the user which the app asserts, the app cannot execute any operations above the permission level of the app itself.
What is a Low Trust App?
A low trust app communicates with the SharePoint server using the app’s identity. It is not allowed or trusted to pretend to be someone else and it has the permissions defined in the app manifest. A low trust app is appropriate for Office 365 and other types of environments where the server that provides the functionality for the app and the server that hosts SharePoint do not share the same directory services or authentication mechanisms. In this case the OAuth trust relationship represents a static identity.
We need SSL certificate.

9.   Can user mapping possible in migration tool to keep user persist in source and destination farm?
Yes

10.   Difference between JSOM and CSOM
CSOM: Client-side object model. C# (or Visual Basic) only, use NuGet, at the moment same package for both 2010 and 2013.
JSOM: JavaScript object model. JavaScript only.
SP.ClientContext.get_current() for normal use. new SP.ClientContext('url...') for specific SPSite. Note this works cross-SPSite in 2013.

11. What is Workflow Impersonation/App Step- (Reference Link)
Impersonation is only available in SharePoint 2010 and App step is available in SharePoint 2013
Impersonation is run on the author permission means that have created or published workflow. App steps sun on the service account.
For Example, If Jay is creating workflows using impersonation steps, and if any other user will perform the task using this workflow then it will perform using the Jay account.

12. Default vs Intranet vs Internet vs Custom vs Extranet zones
These zones, and their labels, are just labels. There is no functional difference between the five. However, these labels indicate to the next administrator how they are used, and what they are for. You may not need more than one zone to use different authentication methods. In fact, Microsoft "recommend that you implement multiple authentication methods on the default zone", which makes access simpler for the user since only one URL is used.
To understand the connection between internal URL, zones and public URL the article A guide to Alternate Access Mappings Basics in SharePoint 2013 is very useful. The article describes zone in this way:
Zone is a label representing a Public URL, the zone is used to ‘connect’ an Internal URL to a Public URL. The zone names has no relation what so ever with the four Internet Explorer security zones (Internet, Local Intranet, Trusted sites and Restricted sites) and could just as easily been named 1,2,3,4 and 5.

13. Difference between application page and site page (reference link).
Site Pages:
Site Pages is a concept where complete or partial page is stored within content database and then actual page is parsed at runtime and delivered to end-users. Site pages can be edited by using SharePoint Designer tool.
Application Pages:
Application pages are stored in the server’s file system. SharePoint Designer tool cannot be used with application pages.
Application pages cannot be used within sandboxed solutions. An Application page cannot be customized and modified by end user, instead a developer is required. These are the normal .aspx pages deployed within SharePoint.

14. Few SharePoint Concepts

 GAC(Assembly) Location
Sandbox solution: C:\ProgramData\Microsoft\SharePoint\UCCache
Below .NET 4 Framework: C:\Windows\Assembly\
.NET 4 and Above .NET4 Framework: C:\Windows\Microsoft.NET\Assembly\GAC_MSIL
I'm checking it in c:\windows\assembly, it should be there, right?
No, that's the directory for the GAC in .NET versions 1.0 through 3.5. It was moved in .NET 4.0 and up, now located in c:\windows\microsoft.net\assembly. You can browse that directory with Explorer, the shell extension handler that flattened the view of the GAC directories is no longer used. If the assembly doesn't contain any unmanaged code then start in the GAC_MSIL directory, you'll have few problems locating the actual file from there.

 Mobile App Limitation
There are several limitations and challenges to using standard SharePoint on mobile devices; including: authentication, user experience, mobile data charges, device support.
You could take the standard mobile templates that ship with SharePoint, but these will require a significant amount of custom development work, which will need to be updated as and when new devices come out.
There are several mobile SharePoint solutions on the market, like Azurati's SharePoint2Go solution (www.azurati.com) that provide authenticated and secure access to mobile SharePoint on any mobile device.
If you are looking to deploy SharePoint to users who will use several different types of mobile devices, or even their own personal devices to access enterprise systems like SharePoint, then you should make sure that your internal build strategy can cope with this; or that your external vendor is able to support multiple device types.
You may also have customized your SharePoint environment with custom web parts. If you believe that mobile users should have access to some or all of these web parts, then equally, this should form part of your vendor selection criteria.

 SharePoint Server Object Model
http://msdn.microsoft.com/en-us/library/ms473633%28v=office.14%29.aspx
Add-SPSolution -LiteralPath c:\contoso_solution.wsp
Install-SPSolution –Identity SharePointProject2.wsp –WebApplication http://sp2010 –GACDeployment
Uninstall-SPSolution -Identity contoso_solution.wsp
Enable-SPFeature -Url "[Site Collection URL]" -Identity AgilePointSettingsListFeature
Disable-SPFeature –Identity Reporting –url http://sp2010
Update-SPSolution -Identity contoso_solution.wsp -LiteralPath c:\contoso_solution_v2.wsp -GACDeployment
 SPFarm farm = SPFarm.Local;
The SPFarm object is the top node in the extensible configuration object model, which is designed to interact with the configuration data store. It contains global settings for all the servers, services, and solutions that are installed in a server farm.

 SPSecurity.RunWithElevatedPrivileges method
Executes the specified method with Full Control rights even if the user does not otherwise have Full Control.
A delegate method that is to run with elevated rights. This method runs under the Application Pool identity, which has site collection administrator privileges on all site collections hosted by that application pool.
public static void RunWithElevatedPrivileges(
        SPSecurity.CodeToRunElevated secureCode
)

SPSecurity.RunWithElevatedPrivileges(delegate()
{
    using (SPSite site = new SPSite(web.Site.ID))
    {
    // implementation details omitted
    }
});


Comments

Post a Comment

Popular Posts

Chat Application using Angular 8, Asp.net Core 2.2.0, Signal R 1.1.0

-
Image
In this article, we are going to create a simple chat application using Angular 8, Asp.net Core 2.2.0, Signal R 1.1.0 as shown below: We install above all prerequisite following in our development machine: Prerequisite .Net Core SDK 2.2.0  – download from  here . Nodejs 10.15.3  – download from  here . Angular CLI 8.0  – Install angular command package by executing this command: “ npm install -g @angular/cli@8.0.0 ” Setup Asp.net Core with Signal R Project: open a command prompt and enter create asp.net core web project as below: Install the following NuGet package in our project: Microsoft.AspNetCore.SignalR Microsoft.AspNetCore.SpaServices.Extensions Call SignalR in the “Startup.ConfigureServices” method to add SignalR services: services.AddSignalR();   Create MessageHub Class: SignalR makes real-time client-to-server and server-to-client communications possible and it will call methods to connect clients from a server using Sign
Read more

Contact Application Using ASP.NET Core Web API, Angular 6.0, And Visual Studio Code - Part One

-
Image
We will develop a contact application using ASP.NET Core Web API, Angular 6.0, and Angular Material UI as shown in the below screenshots.  We will use Visual Studio code (VS code) for the development editor.  I have divided contact application development into two articles, Contact Application using ASP.NET Core Web API, Angular 6.0, and Visual Studio Code Part – 1 In the article, we will set up ASP.NET Core Web API project, and develop the Web API controller for contact CRUD operations. Contact Application using ASP.NET Core Web API, Angular 6.0, and Visual Studio Code Part – 2 In the article, we will setup Angular 6 within ASP.NET Core Web API Project, and develop the contact form & list component using Angular Material UI. So, starting with this article, first, we will see how we can create ASP.Net Core Web API Project. We have the following prerequisites, Visual Studio Code (VS code) editor Please see this  article  to see how we can setup Visual Stud
Read more

Send an Email Reminder Notification Based on an Expiration Date using Power Automate

-
Image
Introduction    In this article, we are going to create an email reminder notification based on an expiration date using Power Automate. We will create a flow that’s run daily that reads & filters data from a SharePoint list that has list items that expire in the next 5 days. Then it will send an expiration notification email to a particular user.   SharePoint List - "ProductSales"     Columns  Type  Title  Text  ExpiryDate  DateTime   Let’s log in to Office.com with office 365 credentials. Go to the “Power Automate” tile and click on it.   It will be redirected to Power Automate Page. Click on Create button from left navigation.   Click on the scheduled flow tile. It will open the popup.       Create Recurrence Flow Enter the flow name and select a specific time when we want to schedule this workflow. Then, click on the create button. It will open the Edit Flow page where we can see a Recurring Action. Now we are f
Read more

MySQL Data Access API Development Using Express.JS, Node.JS

-
Image
In this article, we are looking into the introduction of Node.JS and Express.JS and then, I am going to create a simple MySQL data access API using Express.js, NodeJS. As we all know, Node.JS is the most trending open source technology that’s directly or indirectly partitioning into advanced web development, and let’s have lookup what is Node.JS? Node.JS Definition Node.JS is a platform that provides environment (outside the web browser) to execute JavaScript and which is built on Chrome's V8 JavaScript engine developed by Ryan Dahl. Why Node.JS? NodeJs processing model depends on a single thread with event looping. When clients send HTTP requests to NodeJs server, the Event loop is woken up by OS. It will pass the request and response objects as JavaScript closures to worker functions with callbacks. For long-running jobs like I/O operations running on non-blocking worker threads, when the job is complete, responses are sent to the main thread via a callback
Read more

ReactNative FlatList

-
Image
Introduction: React Native List show has different way to represent, react native listview either FlatList or SectionList. Flatlist is term used for static data just like array of list to view. Process: index.js import React, { Component } from 'react'; import { AppRegistry, FlatList, StyleSheet, Text, View } from 'react-native'; export default class FlatListBasics extends Component {   render() {     return (       <View style={styles.container}>         <FlatList           data={[             {key: 'Devin'},             {key: 'Jackson'},             {key: 'James'},             {key: 'Joel'},             {key: 'John'},             {key: 'Jillian'},             {key: 'Jimmy'},             {key: 'Julie'},           ]}           renderItem={({item}) => <Text style={styles.item}>{item.key}</Text>}         />       </View&
Read more

Contact Application Using ASP.NET Core Web API, Angular 6.0, And Visual Studio Code - Part Two

-
Image
In this article, we are going to learn about how we can setup Angular 6.0 in ASP.Net Core Web API project and develop the contact list & form component using Angular Material UI. In the Part 1 article, we set up ASP.NET Core Web API and developed the API for contact CRUD operation. Please go through  Contact Application using ASP.NET Core Web API, Angular 6.0, and Visual Studio Code Part 1  once before proceeding with this article. To setup Angular 6.0 in the project, first, we have to install NodeJS in the development environment. We can download NodeJS installer from  NodeJS website . and then check the version on NodeJS as below: Now, let us globally install Angular CLI package by enter “npm install –g angular/cli@6.0.0”, as shown in below screenshot Scaffold Angular To scaffold Angular, enter “ng new Contact-App --skip-install” command in VS code terminal as below. Here, --skip-install option is used to skip installation of the npm packages. And Contact-
Read more

Basics Of Node.js Modules

-
Image
In this article, we will be learning the basics of Node.js Modules. There are several questions when talking about Node.js Modules: Why should we know about the Node.js Modules? What are Node.js Modules? Where are Node.js Modules used? Let’s discuss this from the beginning. Nowadays, most of the web developers are working with new technologies like Angular, React, and Vuejs as frontend and Express.Js, Meteor web framework, or SharePoint Framework in JavaScript. But every developer faces issues to understand the pattern of writing the code, or we can say, the ecosystem used in the packages\libraries. If each developer is aware of the NodeJS Modules, it will be helpful in understanding the ecosystem they are working in. As we know, Node.js is a platform that provides an environment to execute JavaScript outside of the web browsers; when we execute JavaScript in Node.js, it will change the scope of the JavaScript. In web browsers, the top-level scope is a global scope. If
Read more

React Native SectionList Basic

-
Image
Introduction: React Native Section List has only one difference compare to flatlist that it gives you section part that corresponding like border way or gives you  A performant interface for rendering sectioned lists, supporting the most handy features : Fully cross-platform. Configurable viewability callbacks. List header support. List footer support. Item separator support. Section header support. Section separator support. Heterogeneous data and item rendering support. Pull to Refresh. Scroll loading. If you don't need section support and want a simpler interface, use <FlatList>. Methods scrollToLocation recordInteraction flashScrollIndicators Process: index.js import React, { Component } from 'react'; import { AppRegistry, SectionList, StyleSheet, Text, View } from 'react-native'; export default class SectionListBasics extends Component {   render() {     return (       <View style={styles.container}>
Read more

React Native Common Errors

-
Image
In article, we are going to see some common errors that we are facing as beginner of react native. It is prerequisite to react native is already setup on our machine if it is not, Please go-through this article from here: Getting start with React Native I personally whenever I start any new programming language or framework I stuck on things that I wish that issue never come again, in fact it always comes. I don’t know why it comes may be I am too bad for start up or my processor of mind is too slow to adopt it. I am writing on this articles based on experiences most common and headache kind of issues/errors that I gets stuck on react native when I was beginner and eventually I was able to solve after put my lot of hours. This articles will surely helps you to find out simple and basic solution or we can say a trick as well to resolve that issues/errors. Problems * Unable to load script from assets index.android.bundle Step 1  mkdir android/app/src/main/
Read more