Your company has a private cloud that is managed by using a System Center 2012 Operations
Manager infrastructure.
You plan to create a distributed application named DistributedApp1.
You need to ensure that a folder for DistributedApp1 is available from the Monitoring workspace in
the Operations Manager console.
What should you do?

A.
Add the OperationsManagerAppMonitoring object to DistributedApp1.

B.
Save DistributedApp1 as a new management pack.

C.
Add the OperationsManagerMonitoringView object to DistributedApp1.

D.
Save DistributedApp1 in the Default Management Pack.

Explanation:
The Default Management Pack file contains common elements such as views at the top level of the
Monitoring workspace.
This is an unsealed management pack file so that you can create views and folders at this level.
It should not be used for any other purpose.

For creating elements such as monitors and rules, create a new management pack file.
Selecting a Management Pack File
http://technet.microsoft.com/en-us/library/hh457560.aspx
The Default management pack that ships with
OpsMgr 2007 is used to store very specific information for the management group.
It is a widely known best practice to NOT write any custom rules, monitors, groups, views, or
overrides to this MP.
Even customers who know this – and try to enforce this across their organizations….
will still inadvertently get junk in their default MP…. they will save things here by accident, or by
granting access to advanced operators who aren’t educated on this topic.
The main problem with doing so…. is that we will build a dependency for this MP on any MP it
references….and therefore we wont ever be able to delete those management packs, until we clean
this Default MP up, and start enforcing best practices.
http://blogs.technet.com/b/kevinholman/archive/2008/11/11/cleaning-up-the-default-mp.aspx