Microsoft Core Solutions of Microsoft SharePoint Server 2013 (070-331日本語版) - 070-331日本語 FREE EXAM DUMPS QUESTIONS & ANSWERS

Explanation:

Note: In regards to the cross-domain comments, even if it is cross-domain, you can allow the target domain under Site Collection Settings, HTML Field Security.

Explanation:
* Create managed path for the web application* In a content database separate from that of the intranet site create a site collection* In the root site for the site collection, grant permissions

Explanation:

Note:
*Blob Cache The BLOB cache is stored directly on the hard disk drive of a front-end web server computer.
*distributed cache SharePoint 2013, makes use of distributed cache to cache newsfeeds, microblogging, conversations, security trimming, OneNote client access, and even keeps the FedAuth cookie for claims based authentication on the server side, so it's more secure, load balancer friendly, and works with webkit-based browsers that like to chop off your cookies at 64kb.
* output cache/page output cache The page output cache stores the rendered output of a page. It also stores different versions of the cached page, based on the permissions of the users who are requesting the page.

Explanation: Only visible for FreeCram members. You can sign-up / login (it's free).

Explanation:
Box 1: Use the Share functionality to share the site.
Box 2: Add third-party vendor email addresses to the Members SharePoint group for the site.
Box 3: Send a message that contains the direct site link to the site user.
Note:
*From Scenario: / Third-party vendors must be able to read and modify documents. / The Partner Projects site collection must allow Contoso and Tailspin Toys users to share documents with third-party vendors on an ad-hoc basis, without incurring additional licensing requirements., whether it is your own internal environment or a partner environment. If you use Active Directory Federation Services (AD FS) 2.0, you have a
SAML token-based authentication environment.
*Correct: If the purpose of your Web site is for members of a particular workgroup to share documents and information, you typically add members of that workgroup (that is, their Windows user accounts or Windows groups) to an appropriate SharePoint group on your site. For example, you can add workgroup members that you want to allow to contribute to your Web site to the Site name Members SharePoint group. This way they can add documents and update lists.
*Incorrect: You can also add other Windows security groups to theSite nameVisitors SharePoint group so that they can read documents and view lists, but not contribute to the site. You might also want help managing the site, so you can assign individual Windows user accounts to theSite nameOwners SharePoint group.

Explanation: Only visible for FreeCram members. You can sign-up / login (it's free).

Explanation:
Box 1:

Box 2:

Box 3:

Note:
*From Scenario:
Allow resource coordinators from Blue Yonder to find temporary staffing options from
Margie's Travel contractors and employees.
*How to create and configure a SharePoint Search service application
When you deploy and configure a Search service application, you perform the following
main tasks:
- Create accounts - Certain domain user accounts are required specifically for a Search service application. - Create a Search service application - A Search service application provides enterprise search features and functionality.
- Configure the Search service application - Basic configuration of a Search service application includes configuring a default content access account, an email contact, and content sources.
- You configure a Search service application on the Search Administration page for that service application.
- Configure the Search service application topology - You can deploy search components on different servers in the farm. You can also specify which instance of SQL Server is used to host the search-related databases.
* Enabling continuous crawl has the following advantages:
The search results are very fresh, because the SharePoint content is crawled frequently to
keep the search index up to date.
The search administrator does not have to monitor changing or seasonal demands for
content freshness. Continuous crawls automatically adapt as necessary to the change rate
of the SharePoint content.

Explanation: Only visible for FreeCram members. You can sign-up / login (it's free).

Explanation:

Note:
*Off-box termination of SSL is when a proxy server terminates an SSL request and then forwards the request to a Web server by using HTTP. In this case, alternate access mappings can be configured to return these requests using SSL, thus maintaining secure communication between the client and the proxy server.
*Example:

Explanation:
Box 1: Configure AD FS with the web application as a relying party Box 2: Configure SharePoint 2013 to trust AD FS as an identity provider Box 3: Configure web applications to use claims-based authentication that use AD FS as the trusted identity provider
Phase 0: Install and configure an AD FS server (we can assume that this has already been done here). Phase 1: Configure AD FS with the web application as a relying party Phase 2: Configure SharePoint 2013 to trust AD FS as an identity provider Phase 3: Configure web applications to use claims-based authentication and AD FS as the trusted identity provider

Explanation:
Usage and health data collection

Note:
*SharePoint 2013 writes usage and health data to the logging folder and to the logging
database. You can use the SharePoint Central Administration website to configure health
data collection settings.
*See step 3 (and 9 - note the reference to SQL authentication).
Configure usage and health data collection by using Central Administration
The usage and health data settings are farm-wide and cannot be set for individual servers
in the farm.
To configure usage and health data collection by using Central Administration:
- Verify that you have the following administrative credentials:
The user account that performs this procedure has to be a member of the Farm
Administrators group. - In Central Administration, on the home page, click Monitoring. - On the Monitoring page, in the Reporting section, click Configure usage and health data collection. - On the Configure usage and health data collection page, in the Usage Data Collection section, select the Enable usage data collection check box. - In the Event Selection section, select the check boxes of the events that you want to log. - In the Usage Data Collection Settings section, type the path of the folder to which you want usage and health information to be written in the Log file location box. The path that you specify must exist on each server in the farm.
These settings are applied to all events. - In the Health Data Collection section, select the Enable health data collection
check box. To change the collection schedules, click Health Logging Schedule.
- To change log collection schedules, click Log Collection Schedule, and then click any of the timer jobs to change its schedule, or disable that timer job. If you disable a timer job, it stops collecting corresponding log data.
- In the Logging Database Server section, to change the authentication method, select either the Windows authentication or SQL authentication option.

Explanation: Only visible for FreeCram members. You can sign-up / login (it's free).