Part three of the Hitchhikers guide to MCSE: Desktop Infrastructure will help with studying for exam 70-416 Implementing Desktop Application Environments. After achieving the MSCA Server 2012 certification you need to pass exam 70-415 and 70-416 to achieve the MCSE: Desktop Infrastructure certification.

You can find part one this will describe all the required exams for MCSE: Desktop Infrastructure and general study tips here

Apply study rule #1 and #2 from Part1:

Study rule 1#: Book the exam before you start studying, this will make sure that you have a deadline to work to. Do not re-schedule the exam unless absolutely necessary, use the time pressure that you might experience to put more effort into studying.

Study rule 2#: Once you get studying and you pass the 1st exam then continue with studying for the other required exams right away. If you take a break between the exams that is longer than 1-2 two weeks it will take you more effort to get used to studying again and you will forget what you learned from the previous exams.

Study 70-416 Implementing Desktop Application Environments:

Book exam 70-416 Implementing Desktop Application Environments

Read the exam details carefully and especially all information listed under “Skills Measured” These skills have been identified as sections that will be covered in the exam and you can expect one more questions on in this exam for each topic listed.

Build a virtual test farm and install the required servers to test/try all the technology listed in the exam details under “Skills Measured” with Server 2012. Microsoft has evaluation versions available for Windows Server 2012, for App-V 5 and for for the System Center products.

You can use Windows 8 Hyper-V, Server 2012 Hyper-V, Virtualbox (free) or VMware Player (free) to setup your virtual test environment. Note that the Remote Desktop Services Virtualization host role required to build a test VDI deployment will require a physical server (or virtualization software that allows to run a Hypervisor virtualized on a Hypervisor, also known as Hypervisor nesting )