Learn About Microsoft System Center Operations Manager 2007

These questions are based on 70-400: TS: Microsoft System Center Operations Manager 2007, Configuring
A Self Test Software Practice Test

Objective: Configure System Center Operations Manager 2007.
Sub-objective: Manage roles.

Multiple answer, multiple-choice

You have the System Center Operations Manager 2007 environment. You are the Management Pack author, and you are creating a task that works with the credentials of the Operations Manager. A group of users added to the Operators user role will need to run this task.

What should you do? (Choose all that apply. Each answer represents part of the solution.)

A. Add the users to the local administrators group.
B. Create a Run As Profile and associate it with the task.
C. Add the users to the Report Security Administrator user role and create a Run As Profile with the appropriate credentials.
D. Create a Run As Account configured with the credentials of Operations Manager.
E. Add the users to Advanced Operators user role.

Answer:
B, D

Tutorial:
The following steps should be performed to ensure users in the Operators role will be able to run the task with the credentials of the Operations Manager:

1. Create the Run As Profile and associate it with the task module.
2. Create a Run As Account by the Operations Manager 2007 administrator and configure it with the credentials required to run the ask.
3. Add the Run As Account to the Run As Profile that will be used by the task.

You should not add users to the local administrators group. The users would not be able to run the task, even with local administrative privileges, because the task cannot be run without the credentials of the Operations Manager.

You should not add users to the Report Security Administrator user role and create a Run As Profile with the appropriate credentials. The Report Security Administrator user role is used to enable integration of SQL Reporting Services security with the Operations Manager roles. In addition, the credentials to run the task are configured in Run As Account, not Run As Profile.

You should not add users to the Advanced Operators user role. Membership in this role would not enable these users to run the desired task. In this scenario, the task requires credentials of Operations Manager.

Reference:

Microsoft TechNet > TechNet Library > System Center > System Center Operations Manager 2007 > Operations Manager 2007 Online Help > Operations Console > Administration Pane > About the Administration Pane in Operations Manager 2007 > Security > Run As Profiles and Run As Accounts in Operations Manager 2007

Objective: Deploy and configure Management Packs.
Sub-objective: Create a self-tuning threshold.

Single answer, multiple-choice

You are the systems administrator for your company. You configure System Center Operations Manager 2007 to create a static threshold monitor and a Self-Tuning Threshold monitor. You want to create a parent monitor and a static monitor and a Self-Tuning Threshold monitor as its child monitors. The parent monitor must reflect the healthiest state of any of the child monitors. What should you do?

A. Create a Windows Services Unit monitor.
B. Create a Correlated Windows Event Unit monitor.
C. Create an aggregate rollup monitor.
D. Create a dependency rollup monitor.

Answer:
C

Tutorial:
You should create an aggregate rollup monitor to achieve the objective in this scenario. With the use of Self-Tuning Thresholds in Operations Manager 2007, you can monitor a computer's counter activities, such as processor utilization, which eliminates the requirement of manually configuring thresholds for alerts. Operations Manager 2007 can be used to create and update a performance baseline, which represents normal activity for the counter.

Self-tuning monitors require a learning period, which is the time period during which Operations Manager 2007 automatically establishes a baseline. This baseline represents a computer's expected and regular activity. The established baseline accurately reflects the use of the IT infrastructure, such as an increase in-processor utilization for a specific date and time.

An aggregate rollup monitor in Operations Manager 2007 is used to display the dependency rollup, a state of a unit or any other aggregate rollup monitors that are targeted to an object. Aggregate rollup monitors typically are used for grouping multiple monitors into one single group that can later be used to set up a health state and generate an alert. An aggregate rollup monitor in Operations Manager 2007 consists of series of child monitors, where one aggregate rollup monitor is designated as the parent monitor.

You can configure the state of an aggregate rollup monitor to reflect the best-case or worst-case state of the child monitors. The best-case state shows the best aggregate state of any of the child monitors, whereas the worst-case state shows the worst aggregate state of any of the child monitors. You can create an aggregate rollup monitor by navigating to Operations Console > Authoring > Management Pack Objects > Monitors > Create Monitor > Aggregate Rollup Monitor.

You should not create a Windows services unit monitor to achieve the objective in this scenario. A Windows services-unit monitor measures whether the service is running.

You should not create a correlated Windows event-unit monitor to achieve the objective in this scenario. A correlated Windows event-unit monitor defines a health state of two dissimilar events that may occur within a short span of time.

You should not create a dependency rollup monitor to achieve the objective in this scenario; this type of rollup monitor is used to roll up health states from any target linked by a hosting relationship or a containment relationship. The Management Packs define the hosting and containment relationships for a target. With the combination of aggregate rollup and unit monitors, you can monitor the health status of every target.

Reference:

TechNet > TechNet Library > System Center > System Center Operations Manager 2007 > Security > Operations Manager 2007 Online Help > Operations Console > Authoring Pane > How to Create Monitors > How to Create an Aggregate Rollup Monitor in Operations Manager 2007

TechNet > TechNet Library > System Center > System Center Operations Manager 2007 > Security > Operations Manager 2007 Reference > Wizards > Operations Manager 2007 Create a New Aggregate Rollup Monitor Wizard


Objective:
Build and deploy custom Management Packs.
Sub-objective: Create monitors and rules.

Single answer, multiple-choice

You are working in a System Center Operations Manager 2007 environment. You are creating a single threshold monitor to check free disk drive space. You have set the threshold to 2 GB and the interval to 30 minutes. You want an alert to be generated when someone adds or removes 2 GB of data. What should you do?

A. Create an average threshold monitor.
B. Create a simple threshold monitor.
C. Create a Self-Tuning Threshold monitor.
D. Create a delta threshold monitor.
E. Create a dependency rollup monitor.

Answer:
D

Tutorial:
To accomplish the task in this scenario, you should create a delta threshold monitor. A delta threshold monitor is used to measure a change. For example, if you set the threshold limit to 2 GB and a time interval of 30 minutes, the delta threshold monitor will generate an alert if 2 GB of data is added or removed from the disk drive every 30 minutes. You can create a delta threshold monitor by navigating to Operations Console > Authoring > Management Pack Objects > Monitors > Create a new Monitor.

A delta threshold monitor is part of the single threshold monitors. A single threshold monitor can be used to define only one limit. If the performance counter goes above or below the threshold limit, an alert is generated or the state of the monitor changes. The following types of single threshold monitors are supported in Operations Manager 2007:

• Simple threshold monitor: This measures the value of a performance counter against the threshold limit specified by you. If the performance counter goes above or below the threshold limit, an alert is generated or the state of the monitor changes.
• Average threshold monitor: This measures the value of a performance object by comparing it with a defined fixed limit. The average threshold monitor takes the most recent number of samples and calculates the average value of these samples to check whether the threshold has been exceeded or not.
• Delta threshold monitor: This measures the change.
• Consecutive samples over threshold monitor: This generates alerts only if the performance counter exceeds the threshold a specific number of times in succession over a given period of time. This monitor is useful in preventing false alarms when there are sudden increases in a performance counter.

You should not create a Self-Tuning Threshold monitor to achieve the objective in this scenario. By using Self-Tuning Thresholds in Operations Manager 2007, you can monitor a computer's counter activities, such as processor utilization, thereby eliminating the need to manually configure thresholds for alerts. Operations Manager 2007 can be used to create and update a performance baseline, which represents normal activity for the counter.

You should not create a dependency rollup monitor to achieve the objective in this scenario. This type of rollup monitor is used to roll up health states from any target linked by a hosting relationship or a containment relationship. The Management Packs define the hosting and containment relationships for a target. With the combination of aggregate rollup and unit monitors, you can monitor the health status of every target.

Reference:

Microsoft TechNet > TechNet Library > System Center > System Center Operations Manager 2007 > Operations Manager 2007 Online Help > Operations Console > Authoring Pane > About the Authoring Pane > Management Pack Objects > Monitors > Static Threshold Unit Monitors in Operations Manager 2007

Objective: Maintain System Center Operations Manager.
Sub-objective: Create views.

Single answer, multiple-choice

You are the system administrator for your company. You manage a System Center Operations Manager 2007 network environment. You deploy Operations Manager 2007 agents manually on multiple application servers in your Active Directory domain. You discover that none of the agent installations were successful. You receive an error message that indicates that the new installations of manual agents have been rejected. You want to ensure the Operations Manager 2007 agents are installed successfully on all application servers. What should you do?

A. Disable the Reject new manual agent installation option.
B. Enable the Review new manual agent installations in pending management view option.
C. Disable the Auto-approve new manually installed agents option.
D. Disable the Override global Management Server settings option.

Answer:
A

Tutorial:
You should disable the Reject new manual agent installation option to achieve the objective in this scenario. From the Security tab in the Management Server Properties dialog box, you can configure various security settings for all agent-managed computers in your Operations Manager 2007 environment. The following settings can be configured under the Security tab:

• Reject new manual agent installation. When this option has been enabled, Operations Manager 2007 rejects all new manually installed agents. Enabling this option is useful when you want to reject the manual installation of the Operations Manager 2007 agents on a computer. You can allow the manual installation by disabling this option. This setting can be enabled only when the Override global Management Server settings option has been enabled.
• Review new manual agent installations in pending management view. When this option has been enabled, Operations Manager 2007 reviews all new manually installed agents. This setting must be enabled to ensure the new manually installed agent appears in the Pending Management view in the Operations Console. This setting can be enabled only when the Override global Management Server settings option has been enabled.
• Auto-approve new manually installed agents. When this option has been enabled, Operations Manager 2007 automatically approves all new manually installed agents. This setting can be enabled only when the Override global Management Server settings option and the Review new manual agent installations in pending management view option have been enabled.
• Override global Management Server settings. When this option has been enabled, Operations Manager 2007 allows global server settings to be overridden.
• Allow this server to act as a proxy and discover managed objects on other computers. When this option has been enabled, Operations Manager 2007 allows Management Server to act as a proxy.

 

You should not enable the Review new manual agent installations in pending management view option to achieve the objective in this scenario. When this option has been enabled, Operations Manager 2007 reviews all new manually installed agents. This setting must be enabled to ensure the new manually installed agent appears in the Pending Management view in the Operations Console.

You should not disable the Auto-approve new manually installed agents option to achieve the objective in this scenario. Enabling this option allows Operations Manager 2007 to automatically approve all new manually installed agents. Disabling this option would not achieve the objective in this scenario.

You should not disable the Override global Management Server settings option to achieve the objective in this scenario. When this setting has been enabled, global server settings in Operations Manager 2007 can be overridden. The Reject new manual agent installation option can only be enabled when the Override global server settings option has been enabled under the Security tab.

Reference:

TechNet > TechNet Library > System Center > System Center Operations Manager 2007 > Operations Manager 2007 Reference > Dialog Boxes in Operations Manager 2007. Management Server Properties Dialog box > Security Tab > Operations Manager 2007 Management Server Properties Dialog Box: Security Tab

Objective: Configure client monitoring.
Sub-objective: Configure Agentless Exception Monitoring (AEM).

Single answer, multiple-choice

You are working in a System Center Operations Manager 2007 environment. You have deployed a Root Management Server, a Microsoft SQL Server 2005 database server and a Management Server on the network.

When you attempt to run a custom application on the SQL Server 2005 database server, you receive an error message related to the application. You want the error reports created on the Microsoft SQL Server to be sent to the Operations Manager 2007 Management Server. What should you do?

A. Configure an agent to act as a watcher node.
B. Configure Agentless Exception Monitoring (AEM).
C. Use the Windows Service template to generate a synthetic transaction.
D. Create an OLE DB Data Source monitoring synthetic transaction.

Answer:
B

Tutorial:
You should configure AEM to accomplish the objective in this scenario. AEM is used to monitor the operating system and application errors within a network environment. AEM is used in scenarios when you want the error reports created on Microsoft applications to be sent to the Operations Manager 2007 Management Server. After the report is sent to the Management Server, Operations Manager 2007 will display views and reports on the error data. AEM can be accessed in Operations Manager 2007 by navigating to Operations Console > Monitoring Pane > Agentless Exception Monitoring.

You should not create an OLE DB Data Source monitoring synthetic transaction to accomplish the objective in this scenario. The OLE DB Data Source template is used in System Center Operations Manager 2007 to generate a synthetic transaction to monitor the availability of databases. This template is used in System Center Operations Manager 2007 when you want to check the availability of databases or to monitor databases required by the company users. For example, if servers in your company communicate with the SQL Server database server, the OLE DB Data Source template can be used to check the availability of databases in the event that the SQL Server database fails.

You should not use the Windows Service template to generate a synthetic transaction. The Windows Service Management Pack template is used to monitor the availability of services related to Windows.

You should not configure an agent to act as a watcher node to accomplish the objective in this scenario. Watcher nodes are selected when a synthetic transaction is created. Watcher nodes are created to perform the actions of a synthetic transaction. For example, if you want to query a database or connect to a Web site, you can assign an agent to act as a watcher node. You can also perform a comparison of data to check performance by designating more than one watcher node.

Reference:

TechNet > TechNet Library > System Center > System Center Operations Manager 2007 > Operations Manager 2007 Online Help > Operations Console > Monitoring Pane > About the Monitoring Pane > Agentless Exception Monitoring

Like what you see? Share it.Google+LinkedInFacebookRedditTwitterEmail
cmadmin

ABOUT THE AUTHOR

Posted in Archive|

Comment: