Answer: C,D 

Explanation: 

C: To import configuration data in Configuration Manager 

1. 

In the Configuration Manager console, click Assets and Compliance. 

2. 

In the Assets and Compliance workspace, expand Configuration Items or Configuration Baselines, and then in the Home tab, in the Create group, click Import Configuration Data. Etc. 

Reference: How to Import Configuration Data in Configuration Manager 

http://technet.microsoft.com/en-us/library/hh691016.aspx 

D: To deploy a configuration baseline 

1. 

In the Configuration Manager console, click Assets and Compliance. 

2. 

In the Assets and Compliance workspace, expand Compliance Settings, and then click Configuration Baselines. 

3. 

In the Configuration Baselines list, select the configuration baseline that you want to deploy, and then in the Home tab, in the Deployment group, click Deploy. 

4. 

In the Deploy Configuration Baselines dialog box, select the configuration baselines that you want to deploy in the Available configuration baselines list. Click Add to add these to the selected configuration baselines list. 

Reference: How to Deploy Configuration Baselines in Configuration Manager 

http://technet.microsoft.com/en-us/library/hh219289.aspx 

Answer: B 

Explanation: 

How to Extend Hardware Inventory in Configuration Manager 

System Center 2012 Configuration Manager hardware inventory reads information about devices by using Windows Management Instrumentation (WMI). WMI is the Microsoft implementation of web-based Enterprise Management (WBEM), which is an industry standard for accessing management information in an enterprise environment. 

In previous versions of Configuration Manager, you could extend hardware inventory by modifying the file sms_def.mof on the site server. 

In System Center 2012 Configuration Manager, you no longer edit the sms_def.mof file as you did in Configuration Manager 2007. Instead, you can enable and disable WMI classes, and add new classes to collect by hardware inventory by using client settings. 

Configuration Manager provides the following methods to extend hardware inventory: 

Enable or disable existing inventory classes - You can enable or disable the default inventory classes used by Configuration Manager or you can create custom client settings that allow you to collect different hardware inventory classes from specified collections of clients. 

Add a new inventory class - You can add a new inventory class from the WMI namespace of another device. 

Import and export hardware inventory classes - You can import and export Managed Object Format (MOF) files that contain inventory classes from the Configuration Manager console. 

Create NOIDMIF Files - Use NOIDMIF files to collect information about client devices that cannot be inventoried by Configuration Manager. 

Create IDMIF Files - Use IDMIF files to collect information about assets in your organization that are not associated with a Configuration Manager client, for example, projectors, photocopiers and network printers. 

Note: 

Reference: How to Extend Hardware Inventory in Configuration Manager 

http://technet.microsoft.com/en-us/library/gg712290.aspx 

Answer:  

Answer: C 

Explanation: 

Create one additional management point that uses HTTPS, and configure research to use it. 

Note: Optional Site System Roles Optional site system roles are site system roles that are not required for the core operation of a Configuration Manager site. However, by default, the management point and distribution point, which are optional site system roles, are installed on the site server when you install a primary or secondary site. Although these two site system roles are not required for the core operation of the site, you must have at least one management point to support clients at those locations. After you install a site, you can move the default location of the management point or distribution point to another server, install additional instances of each site system role, and install other optional site system roles to meet your business requirements. The optional site system roles are described in the following table: A site system role that provides policy and service location information to clients and receives configuration data from clients. You must install at least one management point at each primary site that manages clients, and at each secondary site where you want to provide a local point of contact for clients to obtain computer and user polices. 

Reference: Planning for Site Systems in Configuration Manager 

http://technet.microsoft.com/en-us/library/gg712282.aspx#BKMK_Site_System_Roles 

Answer: B,C 

Explanation: Need to upgrade to Exchange Server 2010 and configure an Exchange connector. 

Reference: Supported Configurations for Configuration Manager - Configuration Manager System 

http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_SupConfigMobileClientReq 

Answer: B,C 

Explanation: The Delete Obsolete Client Discovery Data task deletes obsolete client records from the Configuration Manager site database. A record that is marked obsolete typically was superseded by a newer record for the same client. The newer record becomes the client's current record, and the older record becomes obsolete. When you enable this task, you should configure the schedule to run at an interval greater than the heartbeat discovery schedule. This allows clients to send Discovery Data Records (DDRs) so that the obsolete bit is set correctly. 

Reference: Delete Obsolete Client Discovery Data Task Overview 

https://technet.microsoft.com/sv-se/library/Bb632879.aspx 

Answer: C 

Explanation: The Publishing Status shown in the Active Directory Forests list view is a status summary of all sites in the hierarchy. The status will show 'Failed' if any sites in the hierarchy failed to publish to the forest. To view published site information, open Active Directory Users and Computers, connect to a domain controller in the forest, and go to View-> Advanced Features. Site and management point information is published under the System-> System Management node. 

Reference: Active Directory Forest Discovery and Publishing in Configuration Manager 2012 Beta 2 

http://blogs.technet.com/b/configmgrteam/archive/2011/03/30/active-directory-forest-discovery-and-publishing-in-configuration-manager-2012-beta-2.aspx 

Answer: D 

Explanation: 

* 

Configuration item settings of the type Windows Management Instrumentation (WMI), registry, script, and all mobile device settings in Configuration Manager let you automatically remediate noncompliant settings when they are found. 

* 

A detection method in Configuration Manager contains rules that are used to detect 

whether an application is installed on a computer. This detection occurs before the configuration item is assessed for compliance. To detect whether an application is installed, you can detect the presence of a Windows Installer file for the application, use a custom script, or select Always assume application is installed to assess the configuration item for compliance regardless of whether the application is installed. 

Reference: Introduction to Compliance Settings in Configuration Manager 

http://technet.microsoft.com/en-us/library/gg682139.aspx 

Answer: E 

Explanation: 

DCMAgent.log Client log file Records high-level information about the evaluation, conflict reporting, and remediation of configuration items and applications. 

Reference: http://technet.microsoft.com/en-us/library/hh427342.aspx 

Technical Reference for Log Files in Configuration Manager 

Answer: D 

Explanation: 

http://technet.microsoft.com/en-us/library/gg682082.aspx How to Deploy Applications in Configuration Manager Before you can deploy an application in Microsoft System Center 2012 Configuration Manager, you must create at least one deployment type for the application. http://technet.microsoft.com/en-us/library/gg682174.aspx 

How to Create Deployment Types in Configuration Manager 

Steps to Create a Deployment Type 

Step 1: Start the Create Deployment Type Wizard. 

Step 2: Specify whether you want to automatically detect or to manually define the 

deployment type information. 

Step 3: Specify the content options for the deployment type. 

Step 4: Configure the detection methods to indicate the presence of the application. 

Step 5: Specify the user experience options for the deployment type. 

Step 6: Specify the requirements for the deployment type. 

Requirements are used to specify the conditions that must be met before a deployment 

type can be installed on a client device. 

Step 7: Specify the dependencies for the deployment type. 

Step 8: Confirm the deployment type settings and complete the wizard. 

Step 9: Configure additional options for the deployment types that contain virtual 

applications. 

http://technet.microsoft.com/en-us/library/gg682174.aspx#BKMK_Step61 

Step 6: Specify Requirements for the Deployment Type 

1. On the Requirements page of the Create Deployment Type Wizard, click Add to open the Create Requirement dialog box, and add a new requirement. 

2. From the Category drop-down list, select whether this requirement is for a device or a user, or select Custom to use a previously created global condition. When you select Custom, you can also click Create to create a new global condition. 

Important: If you create a requirement of the category User and the condition Primary Device, and then deploy the application to a device collection, the requirement will evaluate as false. 

3. From the Condition drop-down list, select the condition that you want to use to assess whether the user or device meets the installation requirements. The contents of this list will vary depending on the selected category. 

4. From the Operator drop-down list, choose the operator that will be used to compare the selected condition to the specified value to assess whether the user or device meets in the installation requirement. The available operators will vary depending on the selected condition. 

5. In the Value field, specify the values that will be used with the selected condition and operator whether the user or device meets in the installation requirement. The available 

values will vary depending on the selected condition and the selected operator. 

6. Click OK to save the requirement rule and exit the Create Requirement dialog box. 

7. On the Requirements page of the Create Deployment Type Wizard, click Next. http://technet.microsoft.com/en-us/library/gg682048.aspx How to Create Global Conditions in Configuration Manager In System Center 2012 Configuration Manager, global conditions are rules that represent business or technical conditions that you can use to specify how an application is provided and deployed to client devices.