1. Install and Configure Servers 1.1 Install Servers

I hate generic objectives. What does "Plan for a server installation" really mean? More appropriately, what does MS think it means for the purpose of this test? As i run through these objectives I'm taking my best guess at information that satisfies them.

1.1.1 Plan for Server Install

It never hurts to know the minimum requirements as listed on technet: 1.4 ghz 64 bit cpu, 512 mb ram, 32gb hd space, dvd drive, super vga(800x600), kb and mouse(duh?), internet access. In reality, the minimum numbers are pointless. Nobody is going to install a server that bare. The only important thing here is the 64 bit cpu. No more 32 bit!

Next, let's consider the four versions of 2012. Thankfully not as many as 2008.
Datacenter - up to 64 cpu's, OEM and volume only, unlimited VOSS(2012 virtual machines).
Standard - same as datacenter except only 2 VOSS supported per license
Essentials - Standard without Server Core, Hyper-V, and ADFS. No VOSS licenses.  max of 25 users.
Foundation - basic server features. max of 15 users.

Oddly enough, it looks like Foundation can be run as a DC, but with multiple limitations. I doubt they expect you to know this much about it for the test, but here you go: http://technet.microsoft.com/en-us/library/jj679892.aspx

Also, here's an interesting blog post about the virtual licensing, especially if you are considering running non-windows OS's, or a Virtual Desktop Infrastructure with windows client OS's as VM's on a Standard or Datacenter Hyper-V server: http://www.brianmadden.com/blogs/gabeknuth/archive/2012/07/13/looking-at-microsoft-windows-server-2012-editions-and-licensing-positive-changes-or-a-tightening-of-the-screws.aspx

There's three types of installs now: Server Core, Minimal Server Interface, Server with Gui. You can now switch between the three anytime after install. Server Core is now the default install.

Server Core: No Server Graphical Shell or Graphical Management Tools and Infrastructures. Roles not available: ADFS, App server, Fax Server, Network Policy and Access, RDS/RDG/RDSH/RDWA, Volume Activation, WDS.

Minimal Server Interface: Removes the Server Graphical Shell, so most desktop UI elements gone. Still has Graphical Management Tools and Infrastructure: Server Manager, MMC, Device Manager, and Powershell.

Server with Gui: Has both the Graphical Management Tools, and the Server Graphical Shell. Full install.

1.1.2 Plan for Server Roles - http://technet.microsoft.com/en-us/library/hh831669

In a nutshell, know the ones that have other objectives in the test, and be familiar with the rest. Here's a quick list:
ADCS, ADDS, ADFS, ADLDS, ADRMS, App Server, Failover Clustering, File and Storage, Group Policy, Hyper-V, Networking, Network Load Balance, Network Policy and Access, Print and Document Services, Remote Desktop Services, Security and Protecting, Telemetry, Volume Activation, Web Server(IIS), WDS, Windows Server Backup, WSUS, Windows System Resource Manager.

1.1.3 Plan for a Server Upgrade 

No 32 bit to 64 bit upgrade
No upgrade from pre-release 2012 to release 2012No switching install types until after upgrade is finished(ie Server Core -> Full Gui)
Upgrade Paths:

1.1.4 Install Server Core
server core is installed by default in 2012. What more do they want here?

1.1.5 Optimize resource utilization by using Features on Demand

Features are stored in a side-by-side store(WinSxS).
Three states for installed features:
Enabled/Installed - Installed and binaries available
Disabled/Staged - Not installed, binaries available
Disabled with payload removed/Absent - Not installed, binaries removed

To put a feature in "Disabled with payload removed" status, you can use the -remove switch with Uninstall-WindowsFeature. To reinstall this feature at a later point, use the -source parameter with Install-WindowsFeature.

 When installing a feature that is missing the payload, windows will try to find the payload in the following order:
1) User provided(ie, -source or providing an alternate source path in Add Roles and Features Wizard)
2) Group Policy: Computer Configuration\Administrative Templates\System\Specify settings for optional component installation and component repair
3)  Windows Update

Other possible sources for the binaries: A share with a full install WinSXS folder copied over, a mounted WIM image(using DISM to mount the WIM image), or a mounted VHD image,

Also see 1.2.3 : add and remove features in offline images

1.1.6 Migrate roles from previous versions of Windows Server

Migration can be done from any version from 2003 SP2 to 2012 to any version 2003SP-2012.
Migration can be done 32 to 64 bit server to 2012.
Migration can be done between Server editions.
Migration can be between physical and virtual
Migration can be between install types.

Migrations are done with Windows Server Migration Tools. Installed from Add Roles and Features wizard, or install-windowsfeature migration