which action should you perform?

DRAG DROP
Case Study
This is a case study. Case studies are not limited separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.
To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other question on this case study.
At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next sections of the exam. After you begin a new section, you cannot

return to this section.
To start the case study
To display the first question on this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an All
Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click the Question button to return to the question.
Background
General
Blue Yonder Airlines manufactures, sells, and services small commercial jet aircraft. The company has offices worldwide. Blue Yonder currently uses both SharePoint 2013 and SharePoint 2016. The company has a public website that is based on an ASP.NET web application.
SharePoint 2013
Service environment (SharePoint 2013)
The legacy SharePoint farm runs SharePoint Server 2013.
This farm has over 200 site collections that are hosted on 20 content databases. There is no clear documentation that details which site collections are located in which content databases.
The SQL Server for the SharePoint 2013 farm is ServerRole2013.
Requirements
General
Every file stored within the system must contain the following common document properties:
Document Status
Department
Author
Enterprise Keywords
Values for the Document Status property must be displayed in English, Spanish, or French. The display language must be based on a user’s language preferences.
Additional fields or settings may be added in the future.
You must be able to manage file metadata settings from a single location. When you make changes to settings, the changes must be applied to site collections and existing documents. This location must not be a part of the existing marketing, HR, or procurement team sites.
Site collections
Each departmental site must have a separate site collection. All departmental sites must be hosted in a single web application which is located at http://sp.blueyonder.com.
Locations for the storage of personal documents for each employee should be created in a dedicated web application.
Governance
No custom development is permitted. Custom solutions must not be installed on the farm. Only configurations based on standard functionality acceptable.
Employees in the marketing, HR, and procurement departments are only permitted to have Read, Contribute, or Edit permissions to their sites.
Human Resources

The human resources (HR) department is responsible for sharing information with all employees related to four themes: my work, my pay, my benefits, and my career. The naming of these themes may change over time, and additional themes may be added. It must be possible for someone from the HR team to edit the themes.
The HR site in the intranet is divided into a top level site with three subsites. Each subsite represents a unique team.
The global navigation of the HR site must feature a listing of the relevant themes and link to custom pages that list content for each theme. The site must not display links to subsites or other pages on the HR site.
Team site URL
The HR site must use the URL http://hr.blueyonder.com.
Marketing
The marketing department will use SharePoint to publish brochures, marketing materials, and announcements.
Only final versions of these documents may be added to the marketing team site for sharing with other Blue
Yonder employees. Once a file is published, employees must be able to access the file by using a consistent link even if the file is renamed or moved within the site.
User file storage
Files that are in draft mode must not be accessible to any user except the author until the file is ready for review. Each marketing employee must have a single location for storing draft work, work in progress materials, and other personal files. Files stored in this location must only be accessible to the employee that owns the area unless the employee chooses to share a file with other users.
The storage location must be created automatically for an employee and must not require assistance from IT for configuration.
The URL for each employees’ site must be http://employees.blueyonder.com/my/personal/username, where username represents the login of the employee.
Public website
The public website is not part of the SharePoint environment. It is a standalone ASP.NET website. Content on the public website, including news and job postings, is updated once a month. Information posted to the public website must be accessible by using search. Information stored in the Downloads section of the website must not be crawled due to the large size and the number of files.
Team site URL
The team site for the department must use the URL http://marketing.blueyonder.com.
Procurement
The procurement department uses SharePoint to store contracts and related documents. You must store these documents in as few document libraries as possible. The documents may contain precedents or terms that are relevant for reuse. The procurement site stored over 20 million documents. The term store for the site contains two million terms.
File storage
Currently, the site consumes approximately 100 gigabytes (GB) of storage. This is expected to double within a year. It is expected that search will be a key feature for this group.
Search

When a search is conducted and a user hovers over the search result, the user must be able to easily launch the document, visit the library that it is stored in, or preview the file. The links to the document and the library must appear above the preview of the file.
Team site URL
The site for the department must use the URL http://procurement.blueyonder.com.
Products
The product team uses the legacy SharePoint 2013 farm. You must upgrade the farm to SharePoint Server
2016 so that the product team can take advantage of all the services that are available to the other departments.
The existing products site is very active. You must ensure that users cannot change the site content during the upgrade process.
SharePoint 2016
Logical architecture
The SharePoint environment has two web applications. One web application is used for Departmental
Collaboration, and the other is used for Central Administration.
Each departmental site should be configured as a separate site collection.
All departmental sited should be hosted within the same web application. The web application is accessible at the URLhttp://sp.bluyonder.com.
Locations for the storage of personal documents for each employee should be created in a dedicated web application.
Server environment
The server farm is configured with SharePoint Server 2016 andOffice Online Server. No additional add-ons or software packages are installed.
The SQL Server for the SharePoint 2016 farm is ServerRole2016.
The farm should leverage MinRole with a dedicated server for search.
You need to configure the HR site.
For each requirement, which action should you perform? To answer, drag the appropriate action to the correct requirement. Each action 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.
Select and Place:

DRAG DROP
Case Study
This is a case study. Case studies are not limited separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.
To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other question on this case study.
At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next sections of the exam. After you begin a new section, you cannot

return to this section.
To start the case study
To display the first question on this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an All
Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click the Question button to return to the question.
Background
General
Blue Yonder Airlines manufactures, sells, and services small commercial jet aircraft. The company has offices worldwide. Blue Yonder currently uses both SharePoint 2013 and SharePoint 2016. The company has a public website that is based on an ASP.NET web application.
SharePoint 2013
Service environment (SharePoint 2013)
The legacy SharePoint farm runs SharePoint Server 2013.
This farm has over 200 site collections that are hosted on 20 content databases. There is no clear documentation that details which site collections are located in which content databases.
The SQL Server for the SharePoint 2013 farm is ServerRole2013.
Requirements
General
Every file stored within the system must contain the following common document properties:
Document Status
Department
Author
Enterprise Keywords
Values for the Document Status property must be displayed in English, Spanish, or French. The display language must be based on a user’s language preferences.
Additional fields or settings may be added in the future.
You must be able to manage file metadata settings from a single location. When you make changes to settings, the changes must be applied to site collections and existing documents. This location must not be a part of the existing marketing, HR, or procurement team sites.
Site collections
Each departmental site must have a separate site collection. All departmental sites must be hosted in a single web application which is located at http://sp.blueyonder.com.
Locations for the storage of personal documents for each employee should be created in a dedicated web application.
Governance
No custom development is permitted. Custom solutions must not be installed on the farm. Only configurations based on standard functionality acceptable.
Employees in the marketing, HR, and procurement departments are only permitted to have Read, Contribute, or Edit permissions to their sites.
Human Resources

The human resources (HR) department is responsible for sharing information with all employees related to four themes: my work, my pay, my benefits, and my career. The naming of these themes may change over time, and additional themes may be added. It must be possible for someone from the HR team to edit the themes.
The HR site in the intranet is divided into a top level site with three subsites. Each subsite represents a unique team.
The global navigation of the HR site must feature a listing of the relevant themes and link to custom pages that list content for each theme. The site must not display links to subsites or other pages on the HR site.
Team site URL
The HR site must use the URL http://hr.blueyonder.com.
Marketing
The marketing department will use SharePoint to publish brochures, marketing materials, and announcements.
Only final versions of these documents may be added to the marketing team site for sharing with other Blue
Yonder employees. Once a file is published, employees must be able to access the file by using a consistent link even if the file is renamed or moved within the site.
User file storage
Files that are in draft mode must not be accessible to any user except the author until the file is ready for review. Each marketing employee must have a single location for storing draft work, work in progress materials, and other personal files. Files stored in this location must only be accessible to the employee that owns the area unless the employee chooses to share a file with other users.
The storage location must be created automatically for an employee and must not require assistance from IT for configuration.
The URL for each employees’ site must be http://employees.blueyonder.com/my/personal/username, where username represents the login of the employee.
Public website
The public website is not part of the SharePoint environment. It is a standalone ASP.NET website. Content on the public website, including news and job postings, is updated once a month. Information posted to the public website must be accessible by using search. Information stored in the Downloads section of the website must not be crawled due to the large size and the number of files.
Team site URL
The team site for the department must use the URL http://marketing.blueyonder.com.
Procurement
The procurement department uses SharePoint to store contracts and related documents. You must store these documents in as few document libraries as possible. The documents may contain precedents or terms that are relevant for reuse. The procurement site stored over 20 million documents. The term store for the site contains two million terms.
File storage
Currently, the site consumes approximately 100 gigabytes (GB) of storage. This is expected to double within a year. It is expected that search will be a key feature for this group.
Search

When a search is conducted and a user hovers over the search result, the user must be able to easily launch the document, visit the library that it is stored in, or preview the file. The links to the document and the library must appear above the preview of the file.
Team site URL
The site for the department must use the URL http://procurement.blueyonder.com.
Products
The product team uses the legacy SharePoint 2013 farm. You must upgrade the farm to SharePoint Server
2016 so that the product team can take advantage of all the services that are available to the other departments.
The existing products site is very active. You must ensure that users cannot change the site content during the upgrade process.
SharePoint 2016
Logical architecture
The SharePoint environment has two web applications. One web application is used for Departmental
Collaboration, and the other is used for Central Administration.
Each departmental site should be configured as a separate site collection.
All departmental sited should be hosted within the same web application. The web application is accessible at the URLhttp://sp.bluyonder.com.
Locations for the storage of personal documents for each employee should be created in a dedicated web application.
Server environment
The server farm is configured with SharePoint Server 2016 andOffice Online Server. No additional add-ons or software packages are installed.
The SQL Server for the SharePoint 2016 farm is ServerRole2016.
The farm should leverage MinRole with a dedicated server for search.
You need to configure the HR site.
For each requirement, which action should you perform? To answer, drag the appropriate action to the correct requirement. Each action 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.
Select and Place:

Answer:



Leave a Reply 0

Your email address will not be published. Required fields are marked *