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

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

Explanation:

*Cross Site Publishing is required as metadata will be used as product attributes. You can use cross-site publishing to create an Internet business site that contains a catalog that shows products to customers, based on metadata. Users view pages that are created dynamically based on navigation, and filter results based on additional refinements. The site may also show content such as a company contact page, shipping and handling rates, and job openings. Content is authored internally, and is made available to anonymous users outside the firewall. You can use cross-site publishing to create a knowledge base that is available to internal and external users in an extranet site. Content authors tag pages with metadata to categorize articles so that users can search or browse for specific information, such as troubleshooting articles, support issues, and service packs.
*Managed metadata service is required as product attributes must be stored as managed metadata.
*Search Web Parts is required as users must be able to browse (search) the products.
*Secure Store Service is not required as single-sign on is not required. The Secure Store Service replaces the Microsoft Office SharePoint Server 2007 Single Sign On feature. Secure Store Service is a shared service that provides storage and mapping of credentials such as account names and passwords. It enables you to securely store data that provides credentials required for connecting to external systems and associating those credentials to a specific identity or group of identities.
*Device Channels is not required as there is no requirement that the web pages should be rendered in different devices (such as mobile phones, tablets). A device channel is part of the SharePoint 2013 publishing infrastructure that enables you to render certain site content, style your content, and even change images-while maintaining the same URL across a pool of different devices.

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

Explanation:
Box 1: Install Windows Server 2012 and SQL Server 2012 on physical machines. Box 2: Configure Server01 as a principal server and Server02 as a mirror server. Box 3: Configure Server03 as a log shipping destination.
Note:
*From scenario:
/ All servers must be virtualized unless otherwise specified.
/ The database servers must be physical machines running Windows Server 2012 with
direct access to storage.
/ All database transaction logs must be sent off-site.
(so we configure log shipping destination on Server3 which is located in New York - while
server1 and server2 are both in Chicago).
/ The database servers must be configured for redundancy.
*SQL Server Log shipping allows you to automatically send transaction log backups from a
primary database on a primary server instance to one or more secondary databases on
separate secondary server instances.

Explanation:

*The Developer Dashboard is an instrumentation framework introduced in Microsoft SharePoint Foundation 2010. Similar in concept to ASP.NET page tracing, it provides diagnostic information that can help a developer or system administrator troubleshoot problems with page components that would otherwise be very difficult to isolate.
*SharePoint Health Analyzer his article describes the SharePoint Health Analyzer rule for Search service application crawl database defragmentation. The fragmentation of crawl data indexes occurs on a
different level than regular disk fragmentation. It occurs in each crawl database as data is created, updated, or deleted during normal crawl activity. When you run the health rule, the system makes used storage contiguous, eliminates unused storage, and compacts the database.

Explanation:
Box 1: Create an SSL certificate.
Box 2: Install the SSL certificate on the SharePoint servers.
Box 3: Configure IIS to bind the WebApp1 website to the SSL certificate.
Note: Example: Create Self Signed Certificate on IIS 8 Import Self Signed Certificate to SharePoint Certificate store Add Self Signed Certificate to trust management in Central Administration Configure IIS Binding
----

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

Explanation:
App Management: Front-end server
PerformancePoint: Batch-Processing Server
User Profile: Front-end server
User Profile Synchronization: Batch-Processing Server
Secure Store: Front-end server
In a streamline SharePoint 2013 topology put the low latency services, such as App
Management, PerformancePoint, User Profile, and Secure Store, on the Front-end servers,
while the more demanding processes with high latency, such as User Profile
Synchronization, should be put on a Batch-Processing Server.
For Performance Point Microsoft recommends to use a Batch-processing server or
specialized server.
Note:
Front-end servers - optimize for low latency
*Access Services
*Business Data Connectivity
*Managed Metadata
*User Profile
*Secure store
Batch-processing servers * optimize for load
*User Profile Synchronization
*Workflow
*Machine Translation
*Work Management
Specialized workloads (if needed) *optimize for medium throughput
*Search
*Excel Calculation
*PerformancePoint
*Project

Explanation:
Box 1: Install Azure Active Directory Synchronization Services (AAD Sync).
Box 2: Select the Active Directory Domain Services connector and perform a full import.
Box 3: Select the Windows Azure Active Directory connector and perform a delta
synchronization.
Box 4:

Note:
Step 1: Install Azure Active Directory Synchronization Services (AAD Sync).
AADSync will for most customers be relevant when a new feature is required that is only
available in AADSync.
Step 2-3: Import and Synchronize
1.(Step 2)Select Connectors, and select the first Connector with the type Active Directory Domain Services. Click on Run, select Full import, and OK. Do this for all Connectors of this type.
2.Select the Connector with type Windows Azure Active Directory (Microsoft). Click on Run, select Full import, and OK.
3.(Step 3) Make sure Connectors is still selected and for each Connector with type Active Directory Domain Services, click Run, select Delta Synchronization, and OK.
4.Select the Connector with type Windows Azure Active Directory (Microsoft). Click Run,
select Delta Synchronization, and then OK. Step 4: Verify
1.Start a cmd prompt and go to %Program Files%\Microsoft Azure AD Sync\bin
2.Run: csexport <name of Connector> %temp%\export.xml /f:x Etc.

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

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

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