Answer:- SharePoint 2013 is the next version of Microsoft’s famous collaboration and document management software called SharePoint. This version follows SharePoint 2010 that was released back in May 2010. SharePoint 2013 was released (as preview and RTM versions) with some new and exciting features such as real-time social feed, shredded storage, SharePoint apps, cross-site publishing, out-of-box PDF support, minimal download strategy, and lot more.

Answer:- Microsoft has added some incredible features to SharePoint 2013 that can be of huge benefit to all the companies that use SharePoint on a large scale. Most of the new features are introduced for improving SharePoint’s performance (for both browser and SQL) and to enhance the famous web content management capabilities. There is an improvement for all—end users, developers, and IT administrators.

Answer:- With SharePoint 2013, Microsoft has introduced User License Enforcement capabilities—i.e., different licenses can be assigned to different users based on Active Directory security groups that are added in. A group of admins, for example, would need features that are offered by enterprise license, but a group of end users, on the other hand, can work with standard license and would not need to pay more. By default, the User License Enforcement is disabled and must first be enabled to begin assigning, using, and implementing user licensing capabilities.

Answer:- • Communities: The new version of SharePoint allows users to work together in different ways. Microsoft has enhanced the social feature of SharePoint 2007 in SharePoint 2010 and has made it look better. Communities allow people to collaborate in groups, share knowledge, and find information on various topics easily. • Content: SharePoint content shifts SharePoint 2010 from a departmental solution to an enterprise solution. There has been massive improvement in content wherein users can add a significant number of documents to SharePoint. They can even use external data storage options to store more data. • Search: Microsoft SharePoint 2010 has acquired a fast search server, which improves the search tremendously for users. Now, users can search not only for content but also for people. Users can opt for better language options with thumbnails and previews. Users can even sort out search queries and study similar search to get relevant search results. • Insights: With the help of SharePoint insights, users can access information through different data sources such as dashboards, scorecards, reports, and more. To help users, Microsoft has introduced performance point server to the SharePoint platform. It is also known as performance point services for SharePoint. It helps users discover right people and expertise to make better business decisions.

Answer:- The sandbox solution allows the usage of easy, deployable, and reusable packages that consist of features, site definitions, and many more functionalities. The sandbox solution can be enabled and disabled manually by going and changing from the settings. The solution can be deployed on the server. Sandbox allows the restriction to be put where the execution of the environment allows certain resources to be enabled and kept into the sandbox without affecting the rest of the server. Sandbox solutions can’t affect the whole server as they are not used to deploy at the administrative level. It can be deployed on a site with the administrator permissions using the site collection. Only the administrator is allowed to configure the sandboxed solutions that are related to settings like load balancing, tiers, quotas, resource points, etc.

Answer:- DevOps • A collaboration of development and operations teams. It is more of a cultural shift. • Agile methodology • Resource management, communication, and teamwork • Speed, functionality, stability, and innovation

Answer:- HTTP or Hypertext Transfer Protocol works in a client–server model like the most other protocols. HTTP provides a way to interact with web resources by transmitting hypertext messages between clients and servers.

Answer:- Core operations of DevOps include: • Development • Version Control • Testing • Integration • Deployment • Delivery • Configuration • Monitoring • Feedback

Answer:- Technical benefits: • Continuous software delivery • Less complex problems to fix • Faster bug resolution Business benefits: • Faster delivery of features for customer satisfaction • More stable operating environments • More time available to add product value

Answer:- • Git • Maven • Selenium • Jenkins • Docker • Puppet • Chef • Ansible • Nagios

Answer:- CI or Continuous Integration is the process of compiling the entire code base, every time a member of the software development team checks the code, into the shared source code repository. If a team member checks into the code file with a bug, then the build gets broken. In this sort of scenario, other developers can’t synchronize the shared source code repository without introducing compilation errors into their own local workspaces. Thus, collaborative and shared software development cannot go forward. When a CI build breaks, it is crucial that the problem is corrected immediately. A CI process often includes a suite of unit, and integration and regression tests that run every time the compilation succeeds. If any of these tests fail, the build will be considered unstable, not broken.

Answer:- Three of the most common DevOps KPIs are: • Meantime to failure recovery • Deployment frequency • Percentage of failed deployments

Answer:- Continuous deployment is fully automated, and the deployment to production needs no manual intervention in continuous deployment; whereas, in continuous delivery, the deployment to production requires some manual intervention for change management in the organization, and it needs to be approved by the manager or higher authorities to be deployed in production. According to your organization’s application risk factor, continuous deployment/delivery approach will be chosen.

Answer:- DevOps can’t be referred to as a tool; it is a collaborative work culture that combines development and operations teams for continuous development, continuous testing, continuous integration, continuous deployment, and continuous monitoring.