Your network contains an Active Directory domain. All servers run Windows Server 2008 R2 and are
members of the domain. All servers are located in the main office.
You have a portable computer named Computer1 that runs Windows 7. Computer1 is joined to the
domain and is located in a branch office.
A file server named Server1 contains a shared folder named Share1.
You need to configure Computer1 to meet the following requirements:
• Minimize network traffic between the main office and the branch office
• Ensure that Computer1 can only access resources in Share1 while it is connected to the
network.
What should you do?
A.
On Computer1, enable offline files.
B.
On Computer1, enable transparent caching.
C.
On Server1, configure DirectAccess.
D.
On Server1, configure Share1 to be available offline.
Explanation:
Transparent Caching
When you enable transparent caching, Windows 7 keeps a cached copy of all files that a user opens
from shared folders on the local volume. The first time a user opens the file, the file is stored in the
local cache. When the user opens the file again, Windows 7 checks the file to ensure that the cached
copy is up to date and if it is, opens that instead. If the copy is not up to date, the client opens the
copy hosted on the shared folder, also placing it in the local cache. Using a locally cached copy
speeds up access to files stored on file servers on remote networks from the client. When a user
changes a file, the client writes the changes to the copy of the file stored on the shared folder. When
the shared folder is unavailable, the transparently cached copy is also unavailable. Transparent
caching does not attempt to keep the local copy synced with the copy of the file on the remote file
server as the Offline Files feature does. Transparent caching works on all files in a shared folder, not
just those that you have configured to be available offline.