You need to design the architecture of the farm
DRAG DROP
###BeginCaseStudy###
Case Study: 1
Tailspin Toys
Background
You are planning a SharePoint deployment. The new farm will host several business
solutions including:
www.TailspinToys.com
Tailspin360.TaiIspinToys.com
MyTailspin.TailspinToys.com
All employees have Active Directory Domain Service (AD DS) accounts. Members of
the SalesUsers AD DS security group are the only users with permissions to create
My Sites sites.
Business Requirements
www.TailspinToys.com
www.TailspinToys.com is an Internet business site that will provide eCommerce
capabilities including a product catalog, a shopping cart, and an account settings page.
Tailspin360.TailspinToys.com
Tailspin360.TailspinToys.com provides a business intelligence (BI) solution for the
Sales team. It must allow users to share Microsoft Excel workbooks and build
dashboards. Tailspin360.TailspinToys.com accesses data that is located in various
repositories including Microsoft SQL Server.
MyTailspin.TailspinToys.com
MyTailspin.TailspinToys.com is a social collaboration environment that provides
microblogging, file and video sharing, and the ability to create personal blogs and
wikis for Tailspin Toys employees.
Technical
Requirements
General
The farm must be made fault tolerant by using virtualization.
The farm must include two front-end web servers.
Page requests must be distributed equally across the front-end web servers.
All content must remain available to users if one of the front-end web servers
becomes unavailable.
All Sales department employees are members of the SalesUsers group.
All customer, order, and product information will be stored in tables in a Microsoft
SQL Server database.
The User Profile service application is provisioned but not configured.
www.TailspinToys.com
You must create a version of the site that provides an optimized experience for
Windows Phone devices. You have created a device channel that detects the useragent.
The website must support English (United States), Spanish (Mexico), and German
(Germany). All content is authored in English and then translated into Spanish and
German by an outside vendor. Translations are performed by humans.
Tailspin360.TailspinToys.com
The site must be accessible only to members of the Sales team. Users must be able
to access order information that is stored in a SQL Server database. Developers
must be able to import Business Connectivity Services (BCS) models by using
Central Administration. The salesAccess shared domain account has permissions to
read data from the database. Excel workbooks published to a document library app
must be opened in a browser. Excel workbooks in other locations must open in Excel.
MyTailspin.TailspinToys.com
You need to provision a SharePoint environment that supports My Sites for an
enterprise. You need to ensure the SharePoint Server configuration supports the
ability to create individual site collections the first time a user accesses the My Site
page. All users need permissions to create My Sites sites.
###EndCaseStudy###
You need to design the architecture of the farm. What should you do? (To answer, drag the
appropriate terms to the correct location or locations in the answer area. Each term may be
used once, more than once, or not at all. You may need to drag the split bar between panes
or scroll to view content.)
You need to meet the content recovery requirements for the farm
###BeginCaseStudy##
Case Study: 2
World Wide Importers
Background
General Background
Wide World Importers plans to upgrade from SharePoint 2010 to SharePoint 2013 to
take advantage of additional business intelligence (BI) services, including
PerformancePoint Services, PowerPivot for Excel, and SQL Server Reporting
Services 2012 (SSRS). All users are members of an Active Directory Domain
Services (AD DS) domain.
Technical Background
The current environment integrates with a stand-alone instance of Microsoft SQL
Server 2008 R2 Analysis Services (SSAS). Wide World Importers has acquired SQL
Server 2012 licenses for the purpose of upgrading all the SQL Server instances to
SQL Server 2012.
Business Requirements
The SharePoint 2013 environment and supporting back-end servers that run SQL
Server must be highly available and redundant in the case of unplanned downtime or
a disaster.
Technical Environment
SharePoint 2013 Production Farm Topology
The SharePoint 2013 production farm topology consists of the servers listed in the following table.
The Wide World Importers SharePoint 2013 environment has the following
characteristics:
A hardware load-balancer is configured to balance traffic between PROD-WEB-01
and PROD-WEB-02.
SSRS is installed on PROD-APP-01 in SharePoint integrated mode.
SSRS report databases are stored on PROD-DB-01.
A site collection named Report Center has been created at http://
reports.wideworldimporters.com.
All SharePoint content and configuration databases are stored on PROD-DB-01.
All site collections have been migrated to a single content database named
WSS_Content.
A content database named WSS_TempContent has been restored to PROD-DB01,
but not attached to the SharePoint 2013 farm.
An
AD DS domain user account named PPS_SVC has been created.
SharePoint 2013 Disaster Recovery Site
The SharePoint 2013 Disaster Recovery farm topology consists of the servers listed in the following table.
Technical Requirements
Log shipping must be used to send transaction log backups to the instance of SQL
Server that is running in the disaster recovery site.
Discrete sets of SharePoint content databases must be configured to automatically
failover together.
An additional SQL Server 2012 Report Server must be added to the SharePoint
2013 environment. The server must be configured to use SharePoint integrated
mode.
Additional SQL Server 2012 Report Servers must not be installed on machines that
are running SharePoint as a front-end web server.
Site Collection administrators must not have the ability to upgrade site collections.
Site Collection upgrade jobs must be throttled to a maximum of five site collections at
a time.
A daily backup schedule must be created to perform SQL Server backups of all
SharePoint content and configuration databases.
The PPS_SVC AD DS user account must be used for the PerformancePoint service
application.
Farm administrators must be able to recover content from WSS_TempContent
without attaching the database to the farm.
All content databases within the production farm must be set to read-only when
patching and upgrading the farm.
Farm administrators must be able to determine which sites were missed or skipped
during the upgrade process and must be able to monitor any future upgrades.
###EndCaseStudy###
You need to meet the content recovery requirements for the farm. What should you do?
You need to meet the disaster recovery requirements
DRAG DROP
###BeginCaseStudy##
Case Study: 2
World Wide Importers
Background
General Background
Wide World Importers plans to upgrade from SharePoint 2010 to SharePoint 2013 to
take advantage of additional business intelligence (BI) services, including
PerformancePoint Services, PowerPivot for Excel, and SQL Server Reporting
Services 2012 (SSRS). All users are members of an Active Directory Domain
Services (AD DS) domain.
Technical Background
The current environment integrates with a stand-alone instance of Microsoft SQL
Server 2008 R2 Analysis Services (SSAS). Wide World Importers has acquired SQL
Server 2012 licenses for the purpose of upgrading all the SQL Server instances to
SQL Server 2012.
Business Requirements
The SharePoint 2013 environment and supporting back-end servers that run SQL
Server must be highly available and redundant in the case of unplanned downtime or
a disaster.
Technical Environment
SharePoint 2013 Production Farm Topology
The SharePoint 2013 production farm topology consists of the servers listed in the following table.
The Wide World Importers SharePoint 2013 environment has the following
characteristics:
A hardware load-balancer is configured to balance traffic between PROD-WEB-01
and PROD-WEB-02.
SSRS is installed on PROD-APP-01 in SharePoint integrated mode.
SSRS report databases are stored on PROD-DB-01.
A site collection named Report Center has been created at http://
reports.wideworldimporters.com.
All SharePoint content and configuration databases are stored on PROD-DB-01.
All site collections have been migrated to a single content database named
WSS_Content.
A content database named WSS_TempContent has been restored to PROD-DB01,
but not attached to the SharePoint 2013 farm.
An
AD DS domain user account named PPS_SVC has been created.
SharePoint 2013 Disaster Recovery Site
The SharePoint 2013 Disaster Recovery farm topology consists of the servers listed in the following table.
Technical Requirements
Log shipping must be used to send transaction log backups to the instance of SQL
Server that is running in the disaster recovery site.
Discrete sets of SharePoint content databases must be configured to automatically
failover together.
An additional SQL Server 2012 Report Server must be added to the SharePoint
2013 environment. The server must be configured to use SharePoint integrated
mode.
Additional SQL Server 2012 Report Servers must not be installed on machines that
are running SharePoint as a front-end web server.
Site Collection administrators must not have the ability to upgrade site collections.
Site Collection upgrade jobs must be throttled to a maximum of five site collections at
a time.
A daily backup schedule must be created to perform SQL Server backups of all
SharePoint content and configuration databases.
The PPS_SVC AD DS user account must be used for the PerformancePoint service
application.
Farm administrators must be able to recover content from WSS_TempContent
without attaching the database to the farm.
All content databases within the production farm must be set to read-only when
patching and upgrading the farm.
Farm administrators must be able to determine which sites were missed or skipped
during the upgrade process and must be able to monitor any future upgrades.
###EndCaseStudy###
You need to meet the disaster recovery requirements.
What should you do? (To answer, drag the appropriate terms to the correct location or
locations in the answer area. Each term may be used once, more than once, or not at all.
You may need to drag the split bar between panes or scroll to view content.)
You need to meet the technical requirements for failover
###BeginCaseStudy##
Case Study: 2
World Wide Importers
Background
General Background
Wide World Importers plans to upgrade from SharePoint 2010 to SharePoint 2013 to
take advantage of additional business intelligence (BI) services, including
PerformancePoint Services, PowerPivot for Excel, and SQL Server Reporting
Services 2012 (SSRS). All users are members of an Active Directory Domain
Services (AD DS) domain.
Technical Background
The current environment integrates with a stand-alone instance of Microsoft SQL
Server 2008 R2 Analysis Services (SSAS). Wide World Importers has acquired SQL
Server 2012 licenses for the purpose of upgrading all the SQL Server instances to
SQL Server 2012.
Business Requirements
The SharePoint 2013 environment and supporting back-end servers that run SQL
Server must be highly available and redundant in the case of unplanned downtime or
a disaster.
Technical Environment
SharePoint 2013 Production Farm Topology
The SharePoint 2013 production farm topology consists of the servers listed in the following table.
The Wide World Importers SharePoint 2013 environment has the following
characteristics:
A hardware load-balancer is configured to balance traffic between PROD-WEB-01
and PROD-WEB-02.
SSRS is installed on PROD-APP-01 in SharePoint integrated mode.
SSRS report databases are stored on PROD-DB-01.
A site collection named Report Center has been created at http://
reports.wideworldimporters.com.
All SharePoint content and configuration databases are stored on PROD-DB-01.
All site collections have been migrated to a single content database named
WSS_Content.
A content database named WSS_TempContent has been restored to PROD-DB01,
but not attached to the SharePoint 2013 farm.
An
AD DS domain user account named PPS_SVC has been created.
SharePoint 2013 Disaster Recovery Site
The SharePoint 2013 Disaster Recovery farm topology consists of the servers listed in the following table.
Technical Requirements
Log shipping must be used to send transaction log backups to the instance of SQL
Server that is running in the disaster recovery site.
Discrete sets of SharePoint content databases must be configured to automatically
failover together.
An additional SQL Server 2012 Report Server must be added to the SharePoint
2013 environment. The server must be configured to use SharePoint integrated
mode.
Additional SQL Server 2012 Report Servers must not be installed on machines that
are running SharePoint as a front-end web server.
Site Collection administrators must not have the ability to upgrade site collections.
Site Collection upgrade jobs must be throttled to a maximum of five site collections at
a time.
A daily backup schedule must be created to perform SQL Server backups of all
SharePoint content and configuration databases.
The PPS_SVC AD DS user account must be used for the PerformancePoint service
application.
Farm administrators must be able to recover content from WSS_TempContent
without attaching the database to the farm.
All content databases within the production farm must be set to read-only when
patching and upgrading the farm.
Farm administrators must be able to determine which sites were missed or skipped
during the upgrade process and must be able to monitor any future upgrades.
###EndCaseStudy###
You need to meet the technical requirements for failover. What should you do?
You need to implement a Reporting Services solution
###BeginCaseStudy##
Case Study: 2
World Wide Importers
Background
General Background
Wide World Importers plans to upgrade from SharePoint 2010 to SharePoint 2013 to
take advantage of additional business intelligence (BI) services, including
PerformancePoint Services, PowerPivot for Excel, and SQL Server Reporting
Services 2012 (SSRS). All users are members of an Active Directory Domain
Services (AD DS) domain.
Technical Background
The current environment integrates with a stand-alone instance of Microsoft SQL
Server 2008 R2 Analysis Services (SSAS). Wide World Importers has acquired SQL
Server 2012 licenses for the purpose of upgrading all the SQL Server instances to
SQL Server 2012.
Business Requirements
The SharePoint 2013 environment and supporting back-end servers that run SQL
Server must be highly available and redundant in the case of unplanned downtime or
a disaster.
Technical Environment
SharePoint 2013 Production Farm Topology
The SharePoint 2013 production farm topology consists of the servers listed in the following table.
The Wide World Importers SharePoint 2013 environment has the following
characteristics:
A hardware load-balancer is configured to balance traffic between PROD-WEB-01
and PROD-WEB-02.
SSRS is installed on PROD-APP-01 in SharePoint integrated mode.
SSRS report databases are stored on PROD-DB-01.
A site collection named Report Center has been created at http://
reports.wideworldimporters.com.
All SharePoint content and configuration databases are stored on PROD-DB-01.
All site collections have been migrated to a single content database named
WSS_Content.
A content database named WSS_TempContent has been restored to PROD-DB01,
but not attached to the SharePoint 2013 farm.
An
AD DS domain user account named PPS_SVC has been created.
SharePoint 2013 Disaster Recovery Site
The SharePoint 2013 Disaster Recovery farm topology consists of the servers listed in the following table.
Technical Requirements
Log shipping must be used to send transaction log backups to the instance of SQL
Server that is running in the disaster recovery site.
Discrete sets of SharePoint content databases must be configured to automatically
failover together.
An additional SQL Server 2012 Report Server must be added to the SharePoint
2013 environment. The server must be configured to use SharePoint integrated
mode.
Additional SQL Server 2012 Report Servers must not be installed on machines that
are running SharePoint as a front-end web server.
Site Collection administrators must not have the ability to upgrade site collections.
Site Collection upgrade jobs must be throttled to a maximum of five site collections at
a time.
A daily backup schedule must be created to perform SQL Server backups of all
SharePoint content and configuration databases.
The PPS_SVC AD DS user account must be used for the PerformancePoint service
application.
Farm administrators must be able to recover content from WSS_TempContent
without attaching the database to the farm.
All content databases within the production farm must be set to read-only when
patching and upgrading the farm.
Farm administrators must be able to determine which sites were missed or skipped
during the upgrade process and must be able to monitor any future upgrades.
###EndCaseStudy###
You need to implement a Reporting Services solution. What should you do?
Which two Windows PowerShell cmdlets should you perform?
###BeginCaseStudy##
Case Study: 2
World Wide Importers
Background
General Background
Wide World Importers plans to upgrade from SharePoint 2010 to SharePoint 2013 to
take advantage of additional business intelligence (BI) services, including
PerformancePoint Services, PowerPivot for Excel, and SQL Server Reporting
Services 2012 (SSRS). All users are members of an Active Directory Domain
Services (AD DS) domain.
Technical Background
The current environment integrates with a stand-alone instance of Microsoft SQL
Server 2008 R2 Analysis Services (SSAS). Wide World Importers has acquired SQL
Server 2012 licenses for the purpose of upgrading all the SQL Server instances to
SQL Server 2012.
Business Requirements
The SharePoint 2013 environment and supporting back-end servers that run SQL
Server must be highly available and redundant in the case of unplanned downtime or
a disaster.
Technical Environment
SharePoint 2013 Production Farm Topology
The SharePoint 2013 production farm topology consists of the servers listed in the following table.
The Wide World Importers SharePoint 2013 environment has the following
characteristics:
A hardware load-balancer is configured to balance traffic between PROD-WEB-01
and PROD-WEB-02.
SSRS is installed on PROD-APP-01 in SharePoint integrated mode.
SSRS report databases are stored on PROD-DB-01.
A site collection named Report Center has been created at http://
reports.wideworldimporters.com.
All SharePoint content and configuration databases are stored on PROD-DB-01.
All site collections have been migrated to a single content database named
WSS_Content.
A content database named WSS_TempContent has been restored to PROD-DB01,
but not attached to the SharePoint 2013 farm.
An
AD DS domain user account named PPS_SVC has been created.
SharePoint 2013 Disaster Recovery Site
The SharePoint 2013 Disaster Recovery farm topology consists of the servers listed in the following table.
Technical Requirements
Log shipping must be used to send transaction log backups to the instance of SQL
Server that is running in the disaster recovery site.
Discrete sets of SharePoint content databases must be configured to automatically
failover together.
An additional SQL Server 2012 Report Server must be added to the SharePoint
2013 environment. The server must be configured to use SharePoint integrated
mode.
Additional SQL Server 2012 Report Servers must not be installed on machines that
are running SharePoint as a front-end web server.
Site Collection administrators must not have the ability to upgrade site collections.
Site Collection upgrade jobs must be throttled to a maximum of five site collections at
a time.
A daily backup schedule must be created to perform SQL Server backups of all
SharePoint content and configuration databases.
The PPS_SVC AD DS user account must be used for the PerformancePoint service
application.
Farm administrators must be able to recover content from WSS_TempContent
without attaching the database to the farm.
All content databases within the production farm must be set to read-only when
patching and upgrading the farm.
Farm administrators must be able to determine which sites were missed or skipped
during the upgrade process and must be able to monitor any future upgrades.
###EndCaseStudy###
You need to meet the security requirement for site collection upgrades. Which two Windows
PowerShell cmdlets should you perform? (Each correct answer presents part of the solution.
Choose two.)
You need to meet the database backup requirements
DRAG DROP
###BeginCaseStudy##
Case Study: 2
World Wide Importers
Background
General Background
Wide World Importers plans to upgrade from SharePoint 2010 to SharePoint 2013 to
take advantage of additional business intelligence (BI) services, including
PerformancePoint Services, PowerPivot for Excel, and SQL Server Reporting
Services 2012 (SSRS). All users are members of an Active Directory Domain
Services (AD DS) domain.
Technical Background
The current environment integrates with a stand-alone instance of Microsoft SQL
Server 2008 R2 Analysis Services (SSAS). Wide World Importers has acquired SQL
Server 2012 licenses for the purpose of upgrading all the SQL Server instances to
SQL Server 2012.
Business Requirements
The SharePoint 2013 environment and supporting back-end servers that run SQL
Server must be highly available and redundant in the case of unplanned downtime or
a disaster.
Technical Environment
SharePoint 2013 Production Farm Topology
The SharePoint 2013 production farm topology consists of the servers listed in the following table.
The Wide World Importers SharePoint 2013 environment has the following
characteristics:
A hardware load-balancer is configured to balance traffic between PROD-WEB-01
and PROD-WEB-02.
SSRS is installed on PROD-APP-01 in SharePoint integrated mode.
SSRS report databases are stored on PROD-DB-01.
A site collection named Report Center has been created at http://
reports.wideworldimporters.com.
All SharePoint content and configuration databases are stored on PROD-DB-01.
All site collections have been migrated to a single content database named
WSS_Content.
A content database named WSS_TempContent has been restored to PROD-DB01,
but not attached to the SharePoint 2013 farm.
An AD DS domain user account named PPS_SVC has been created.
SharePoint 2013 Disaster Recovery Site
The SharePoint 2013 Disaster Recovery farm topology consists of the servers listed in the following table.
Technical Requirements
Log shipping must be used to send transaction log backups to the instance of SQL
Server that is running in the disaster recovery site.
Discrete sets of SharePoint content databases must be configured to automatically
failover together.
An additional SQL Server 2012 Report Server must be added to the SharePoint
2013 environment. The server must be configured to use SharePoint integrated
mode.
Additional SQL Server 2012 Report Servers must not be installed on machines that
are running SharePoint as a front-end web server.
Site Collection administrators must not have the ability to upgrade site collections.
Site Collection upgrade jobs must be throttled to a maximum of five site collections at
a time.
A daily backup schedule must be created to perform SQL Server backups of all
SharePoint content and configuration databases.
The PPS_SVC AD DS user account must be used for the PerformancePoint service
application.
Farm administrators must be able to recover content from WSS_TempContent
without attaching the database to the farm.
All content databases within the production farm must be set to read-only when
patching and upgrading the farm.
Farm administrators must be able to determine which sites were missed or skipped
during the upgrade process and must be able to monitor any future upgrades.
###EndCaseStudy###
You need to meet the database backup requirements.
What should you do? (To answer, drag the appropriate terms to the correct location or
locations in the answer area. Each term may be used once, more than once, or not at all.
You may need to drag the split bar between panes or scroll to view content.)
Which type of storage solution should you implement?
###BeginCaseStudy###
Case Study: 3
Baldwin Museum of Science
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
SPCWEB02.
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.
###EndCaseStudy###
You need to configure SPS-DB01.
Which type of storage solution should you implement?
You need to back up the HR site collection
HOTSPOT
###BeginCaseStudy###
Case Study: 3
Baldwin Museum of Science
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
SPCWEB02.
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.
###EndCaseStudy###
You need to back up the HR site collection. What should you do? (To answer, select the
appropriate option from each drop-down list in the answer area.)
You need to reconfigure the ContentFarm database topology
DRAG DROP
###BeginCaseStudy###
Case Study: 3
Baldwin Museum of Science
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
SPCWEB02.
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.
###EndCaseStudy###
You need to reconfigure the ContentFarm database topology.
What should you do? (To answer, drag the appropriate options to the correct location or
locations in the answer area. Each option may be used once, more than once, or not at all.
You may need to drag the split bar between panes or scroll to view content.)