DRAG DROP
You have a SharePoint Server 2013 server farm.
The farm has four front-end Web servers.
You have a master page named Contoso.master. The master page contains an image file that is 50
KB.
You need to recommend a solution to cache content.
The solution must meet the following requirements:
The image must be stored physically on each front-end Web server.
Authentication information must be cached and replicated on all of the font-end Web servers.
The pages generated by using Contoso.master and all of the page layouts must be stored in the
memory of each front-end Web server.
Which caching mechanism should you recommend for each requirement? (To answer, drag the
appropriate caching mechanisms to the correct requirements. Each caching mechanism 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.)

Answer:

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 webkitbased 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.