You need to centrally manage software updates for all of the servers by using Configuration Manager

Your network contains a System Center 2012 Configuration Manager environment that contains six
servers configured as shown in the following table:

Server5 and Server6 are in the perimeter network, while Server1, Server2, Server3, and Server4 are
in the internal network.

Administrators currently apply software updates to servers manually.
You discover that Server4 was never updated.
You need to centrally manage software updates for all of the servers by using Configuration
Manager.
What should you do first?

A.
Install a management point on Server5.

B.
Configure IIS to support only HTTPS on Server6.

C.
Install a management point on Server2.

D.
Install Network Load Balancing (NLB) on Server3.

E.
Install an enrollment proxy point on Server6.

F.
Configure IIS to support only HTTP on Server3.

G.
Configure the Exchange connector on Server3.

H.
Install Network Load Balancing (NLB) on Server6.

I.
Install a PXE-enabled protected distribution point on Server5.

J.
Install the Windows Cluster service on Server3.
K.
Install a PXE-enabled protected distribution point on Server4.
L.
Install the Windows Cluster service on Server6.
M.
Install Windows Server Update Services (WSUS) on Server3.
N.
Install a protected distribution point on Server1.
O.
Install a software update point on Server3.

Explanation:
http://technet.microsoft.com/en-us/library/gg682168.aspx
Introduction to Software Updates in Configuration Manager
Software updates in System Center 2012 Configuration Manager provides a set of tools and
resources that can help manage the complex task of tracking and applying software updates to client
computers in the enterprise. An effective software update management process is necessary to
maintain operational efficiency, overcome security issues, and maintain the stability of the network
infrastructure. However, because of the changing nature of technology and the continual
appearance of new security threats, effective software update management requires consistent and
continual attention.
http://technet.microsoft.com/en-us/library/gg712312.aspx
Configuring Software Updates in Configuration Manager
…
Step 1: Install and Configure a Software Update Point
The software update point is required on the central administration site and on the primary sites in
order to enable software updates compliance assessment and to deploy software updates to clients.
The software update point is optional on secondary sites. The software update point site system role
must be created on a server that has WSUS installed. The software update point interacts with the
WSUS services to configure the software update settings and to request synchronization of software
updates metadata. When you have a Configuration Manager hierarchy, install and configure the
software update point on the central administration site first, then on child primary sites, and then
optionally, on secondary sites. When you have a stand-alone primary site, not a central
administration site, install and configure the software update point on the primary site first, and
then optionally, on secondary sites. Some settings are only available when you configure the
software update point on a top-level site. There are different options that you must consider
depending on where you installed the software update point.
You can add the software update point site system role to an existing site system server or you can
create a new one. On the System Role Selection page of the Create Site System Server Wizard or Add
Site System Roles Wizard, depending on whether you add the site system role to a new or existing
site server, select Software update point, and then configure the software update point settings in
the wizard.
…
Further information:
A WSUS service will simplify and automate software updates for all servers from a single
management interface.