Client-to-server and server-to-client content redirection

You need to know what both client-to-server and server-to-client content redirection are for the 1Y0-259 exam. To help you keep from confusing them, here's a brief summary of each:

Client-to-server redirection is configured to allow a file on a client device to be opened using a published application on a XenApp Server. For example, if a user receives an email with a PDF attached to it but the user does not have a PDF reader installed on their computer, client-to-server content redirection can be configured so that the published PDF reader in the server farm launches automatically when the user attempts to open any file with a .PDF extension.

Server-to-client redirection is kind of the opposite, except it only works with multimedia applications. It forces applications, such as web browsers, Real Player, or QuickTime, to run on the client device and not the server. This frees up resources on the XenApp Servers. It is good to configure this when there is heavy URL clicking going on. An example of where this would come in handy would be a media company where the users are constantly receiving emails with URLs that launch web browsers and videos. By putting the load back on the users' computers, the performance of other applications in the server farm isn't degraded.

Hopefully, that gives you a helpful review of each type of content redirection before you go sit for the 1Y0-259 exam.