Question No: 132 – (Topic 8)

Your company has a private cloud that contains a System Center 2012 R2 infrastructure. You have a management server named Server1 that has Operations Manager installed.

You have a management server named Server2 that has Virtual Machine Manager (VMM) installed.

You need to monitor network devices by using Operations Manager. The solution must meet the following requirements:

->Only provide the health status of devices located on physical networks.

->Only include devices that are one hop away from a managed host.

->Only include devices that are part of the private cloud.

What should you use?

The Fabric Health Dashboard

The Microsoft System Center Advisor (SCA)

The Network Vicinity Dashboard

The Application Summary Dashboard

Answer: A

Question No: 133 – (Topic 8)

Your company has a private cloud that contains a System Center 2012 R2 infrastructure.

You run applications virtually by using Hyper-V hosts. Each application has a dedicated virtual machine on a Hyper-V host.

The Microsoft Monitoring Agent is deployed to all physical servers. Currently, all of the physical servers are monitored for memory, CPU, and disk space use.

You need to monitor the memory, CPU, and disk space use of each application server.

What should you do?

Deploy the Microsoft Monitoring Agent to each virtual machine.

Configure a new notification subscription for each Hyper-V host.

Deploy the Configuration Manager client to each virtual machine.

Configure a new channel for each virtual machine.

Answer: A Explanation:

Bad question IMO. The thing to know here is that the SCOM Agent is now called the Microsoft Monitoring Agent. In order to monitor VMs, you need to install the SCOM agent (MMA) to the guest, not the host.

Switches and routers are among the most common kinds of nodes you will discover. The node dashboard provides details on the health of a particular device.

The upper portion of the node dashboard consists of the network vicinity view for that node, as well as quot;speedometerquot; gauges for node availability today, yesterday, in the last week, and in the last month.

(Periods of time that were not monitored are counted as quot;availablequot; in the availability statistics, so newly discovered devices will not appear to have had outages in the gauges.) The lower portion of the node dashboard includes a list of all interfaces on the node that are being monitored.

From this view, you can manually override the automatic selections of which interfaces are monitored by SCOM.

Also, by right-clicking on specific interfaces, you can pivot to performance or reporting views that drill down into the near term or long term history of an interface.

In Figure B, the Interface Packet Analysis report for quot;PORT 4 on quot;switch1 during the previous week appears in a second window.

Question No: 136 DRAG DROP – (Topic 8)

Your company has a private cloud that is managed by using a System Center 2012 infrastructure.

The private cloud contains 200 servers that run Windows Server 2008 R2. All of the servers are managed by Operations Manager.

The private cloud contains an application named App1 that is deployed on-demand to several servers. The servers that run the application are identified by a registry value set during the application#39;s installation.

You create a monitor that targets all of the servers.

You need to modify the monitor to only affect the servers that have the application installed.

Which three actions should you perform in sequence? (To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.)

In Operations Manager 2007, you can create attributes to define a commonality within a group of objects that you want to monitor.

After you create an attribute, you can create a group whose members are only objects that have the commonality described in your attribute.

For example, if you want to monitor a set of servers that all have a common registry value, you create an attribute based on that registry value.

To find the servers that have that registry value, you create a group that has a dynamic inclusion rule for only those servers that have the newly created attribute and target the group only to the server object type.

Operations Manager then checks the registry of each server to see whether that registry value exists.

If it does, that server is added as a member of the group.

When you create an attribute, you must select an object type as a target for it. Operations Manager adds the new attribute to the existing list of attributes for that object type.

If the target you select is from a sealed management pack, the object type also is sealed and the new attribute cannot be added.

Instead, Operations Manager creates a new object type to which it adds the new attribute. By default, this new object type is named after the original object type with _Extended appended to the original name.

This new object type contains all the attributes of the original object type, in addition to the attribute you are creating.

You can view existing attributes in the Monitoring area of the Operations console.

If the attributes are defined within a sealed management pack, you can view the properties of the attribute but you cannot change them.

The properties of an attribute include information about where the attribute information is stored, such as the registry or through WMI.

You can create a new attribute for any monitored object, and you can change most of the properties of an attribute that you create.

Specify which TCP/IP port that the WSUS website listens on for connections (for example, port 8530).

Enter credentials for connecting to the WSUS server.

The account must have administrator rights on the WSUS server.

If necessary, select the Use Secure Socket Layer (SSL) to communicate with the WSUS server and client#39;s check box.

Click Add.

The WSUS server will be added to VMM, followed by initial synchronization of the updates catalog.

Depending on how many update classifications and products you chose when you installed the WSUS server, this operation can take a long time, depending on such factors as network traffic and the load on the WSUS server.

To find out the status of the operation, monitor the status of the Add Update Server and Synchronize Update Server jobs in the Jobs window or in the Jobs workspace.

Note

After you enable update management in VMM, you should manage the WSUS server only through VMM, unless you are using a WSUS server in a Configuration Manager environment.

To verify that the WSUS server was added to VMM successfully:

In the Fabric workspace, on the Fabric pane, expand Servers, and click Update Server.

The results pane should display the WSUS server.

In the Library workspace, on the Library pane, expand Update Catalog and Baselines, and then click Update Catalog.

The results pane should display the updates that were downloaded during WSUS synchronization.

Question No: 138 – (Topic 8)

Your company has a datacenter in Los Angeles that contains a private cloud. The private cloud contains a System Center 2012 infrastructure.

The System Center 2012 infrastructure contains the following:

->Service Manager

->Orchestrator

->Operations Manager

You plan to configure the private cloud to meet the following requirements:

->Integrate runbooks to Service Manager requests.

->Automate administration tasks by using runbooks.

->Provide end users with the ability to perform administrative tasks.

You need to configure the private cloud to meet the requirements. What should you do from Service Manager?

Register a data source.

Register the Orchestrator Integration Packs.

Create a channel.

Select the sync folder for the Orchestrator connector.

Answer: B

Question No: 139 – (Topic 8)

Your company has a private cloud that is managed by using a System Center 2012 Operations Manager infra structure.

Question No: 140 – (Topic 8)

You manage a System Center 2012 R2 deployment that contains the servers configured as shown in the following table.

You have a Microsoft Azure subscription. All three servers have the Azure PowerShell module installed.

You need to ensure that you can run Azure PowerShell cmdlets from Runbook Tester. What should you do?

From Server2, deploy the Integration Pack for Windows Azure to Server1.

On Server1, add the Run.NET Script activity. Add the Import-Module Azure cmdlet to the first line of the script.

On Server1, add the Run.NET Script activity. Invoke C:\Windows\System32\WindowsPowerShell\v1.0\PowerShell.exe in the first line of the script.

From Server2, deploy the integration pack for Representational State Transfer (REST) to Server1.

Answer: B

Explanation: An Integration Module is a package that contains a Windows PowerShell Module and can be imported into Automation. Windows PowerShell Modules contain cmdlets that can be used in Automation runbooks. Products and services such as Operations Manager and Azure have modules that include cmdlets specific to their operation.