Explanation/Reference:
Note:
* From scenario:
/A daily backup schedule must be created to perform SQL Server backups of all SharePoint content and configuration databases.
* To start the Maintenance Plan Wizard
1. Expand the server.
2. Expand the Management folder.
3. Right-click Maintenance Plans and select Maintenance Plan Wizard. This launches the wizard and you can now step through and create a plan customized to meet your maintenance requirements.
* Right click on node Maintenance Plans and Click "Maintenance Plan Wizard" Click next to the wizard description, in the 'select plan properties' click on 'Change' Select schedule type as 'recurring' and configure your schedule for backup, for example select frequency as 'daily' for daily backups.
Testlet 1
Background
Baldwin Museum of Science has an Active Directory Domain Services (AD DS) domain named BaldwinMuseumOfScience.com.
The domain has a SharePoint environment that contains two farms named ContentFarm and SearchFarm.
ContentFarm includes content and collaboration tools. A custom app named Time Entry is deployed to the App Store on ContentFarm. ContentFarm includes a site collection named HR.
You are planning for a major content and configuration update to the term store in the managed metadata service application that is located on ContentFarm.
SearchFarm is reserved for crawling content and responding to search queries.
ContentFarm Topology
The topology of ContentFarm is shown in the following table.

ContentFarm has the following characteristics:
Primary content for the farm is available at the URL SharePoint.BaldwinMuseumOfScience.com.

Requests for content from the farm are load-balanced between SPC-WEB01 and SPC-WEB02.

The servers that run Microsoft SQL Server are members of an active/passive cluster that run a failover

cluster named SP-SQL01.
MySites sites for each user are hosted on a separate web application available at the URL

my.baldwinmuseumofscience.com.
Requests for MySites pages are load-balanced between SPC-WEB01 and SPC-WEB02.

A full backup of the farm is performed once a week.

An incremental backup of the farm is performed once a day.

The Site Owner of the HR site collection requires that the HR Site Collection be backed up in full on a

daily basis.
The managed metadata, user profile, and BCS service applications are enabled in the farm.

All members of the SharePoint developer team belong to an AD DS security group named

SharePoint_App_Dev.
SearchFarm Topology
The topology of SearchFarm is shown in the following table.

SearchFarm has the following characteristics:
The farm currently uses SPS-DB01 as its primary database instance.

SPS-DB01 has experienced multiple hard drive failures in the last month.

The identity of the search service application is not documented.

Technical Requirements
The following requirements must be met for ContentFarm and SearchFarm:
All administrative activities must be performed by using Windows PowerShell.

Custom applications created by using the SharePoint app model must be deployed to, and hosted in,

an internal App Store.
Site owners must not be able to directly purchase third-party apps from the public SharePoint Store.

Members of the SharePoint_App AD DS security group must have the ability to submit new apps and

app updates to the App Store of ContentFarm.
Members of the SharePoint_App_Dev AD DS security group must not be granted farm administrator

rights in ContentFarm.
The Time Entry app must remain available to users at all times.

The contents of ContentFarm must be indexed by the Search service application of SearchFarm.

All responses to queries submitted by users in ContentFarm must be served by the Search service

application of SearchFarm.
The database resources for SearchFarm must be configured to be highly available by using SQL

Server database mirroring with automatic failover.
MySite content databases must be moved to a separate clustered database instance. The new

clustered database instance must be created by using existing database servers in ContentFarm.
All storage resources for both farms must be redundant and provide high performance for both read

and write operations and support disk mirroring.
A snapshot of the current state of the managed metadata service application must be taken before the

service application receives the planned major update.