Monitoring and Management with SCOM (40%): Dive deep into day-to-day enterprise monitoring logic. This domain focuses on authoring and managing synthetic transactions, configuring rules, building sophisticated monitors (unit, aggregate, and dependency), fine-tuning alerting thresholds, establishing notification workflows, and leveraging management packs to oversee distributed IT services, operating systems, and core applications.

SCOM Administration and Maintenance (35%): Focus on long-term lifecycle management and performance optimization. Key areas include implementing role-based access control (RBAC), managing SCOM user profiles, configuring long-term data retention within the SQL Server Data Warehouse, generating operational reports, performing database grooming, executing disaster recovery protocols, and diagnosing complex agent communication or server-side performance bottlenecks.

B) Mutual X.509 Certificate authentication via Port 5723

C) Active Directory Trust authentication via Port 1433

D) NTLMv2 fallback authentication via Port 80

E) Symmetric Pre-Shared Key (PSK) authentication via Port 443

F) Token-based OAuth2 authentication via Port 8080

Explanation for Option B (Correct): When a SCOM agent or gateway server resides outside the Active Directory Kerberos trust boundary (such as in an untrusted DMZ), mutual X.509 certificate authentication must be established. SCOM natively uses port 5723 (TCP) for all operational communication between agents, gateways, and management servers.

Explanation for Option A (Incorrect): Kerberos authentication is the default mechanism used by SCOM, but it strictly requires that both the management server and the monitored agent reside within the same trusted Active Directory forest or across a functioning forest trust, which is not the case for an untrusted DMZ.

Explanation for Option C (Incorrect): Active Directory Trust cannot be configured as an authentication mechanism itself, and port 1433 is reserved for Microsoft SQL Server communication, which should never be exposed directly to a DMZ gateway.

Explanation for Option D (Incorrect): SCOM does not support raw NTLMv2 for agent-to-management server communication channels, and port 80 is used for unencrypted HTTP traffic, not secure operational monitoring data.

Explanation for Option E (Incorrect): SCOM does not utilize symmetric pre-shared keys for infrastructure authentication, and port 443 is typically reserved for standard web traffic or cloud attachment via the Operations Management Suite, not native SCOM protocol transport.

Explanation for Option F (Incorrect): Token-based OAuth2 is not supported for native on-premises SCOM agent-to-gateway or gateway-to-management server channel validation, and port 8080 is a non-standard web alternative.

B) Increase the script interval to a higher value, implement a cookdown strategy if multiple workflows use the script, and ensure the script uses the native SCOM API for output object handling

C) Move the Operational Database to an SSD storage tier to decrease script execution time

D) Change the management server workflow settings to run all scripts inside the SQL Data Warehouse instance

E) Disable the health service on the affected management server and rely entirely on agentless polling

F) Force the monitor to execute under the secure "SCOM Bootstrap Account" profile exclusively

Explanation for Option B (Correct): Running complex PowerShell scripts every 30 seconds induces high CPU overhead due to script initialization costs. Increasing the interval gives the system breathing room. Furthermore, "cookdown" allows SCOM to run a single data source script once and distribute the returned property bag data to multiple workflows simultaneously, radically lowering system strain.

Explanation for Option A (Incorrect): Converting a unit monitor into an aggregate monitor changes the structural hierarchy of health state rollups but does not modify the underlying script execution frequency or runtime performance of the resource-intensive workflow itself.

Explanation for Option C (Incorrect): Upgrading database storage performance speeds up transaction log writes and data processing, but it does not address the local CPU bottleneck caused by script engine instantiation on the management server.

Explanation for Option D (Incorrect): SCOM monitoring workflows and scripts execute locally via the MonitoringHost.exe process on management servers or agents; they cannot be offloaded to run directly inside the SQL Data Warehouse engine.

Explanation for Option E (Incorrect): Disabling the health service on the management server stops all monitoring workflows entirely, rendering the server useless rather than solving the specific application management pack issue.

Explanation for Option F (Incorrect): Altering the RunAs account profile changes the security context under which the script runs, but it does nothing to optimize resource consumption or stop the high-frequency execution pattern causing the CPU spike.

B) Run the dwstat command line utility directly on the SQL Server hosting the Operational database

C) Execute the StandardDatasetGroomingSettingUpdate stored procedure or use a dedicated Data Warehouse write action tool to modify the specific dataset retention settings in the OperationsManagerDW database

D) Delete the performance tables manually using SQL Server Management Studio (SSMS) drop queries

E) Reinstall the SCOM Reporting Server component and select the custom retention timeframe during setup

F) Edit the global registry keys on the root management server emulator under the health service paths

Explanation for Option C (Correct): Data Warehouse retention settings are not exposed via the standard SCOM console user interface. Adjusting dataset retention (such as performance data, alerts, or state changes) requires interacting directly with the OperationsManagerDW database metadata, typically by executing specific stored procedures or using specialized management pack authoring tools designed to configure dataset variables safely.

Explanation for Option A (Incorrect): The Administration pane of the Operations Console only controls grooming for the Operational Database (OperationsManager), which handles short-term data (typically 7 days by default), not the long-term Data Warehouse.

Explanation for Option B (Incorrect): There is no standard utility named dwstat capable of altering internal database dataset retention parameters across the Operations Manager engine.

Explanation for Option D (Incorrect): Manually dropping or truncating tables within the SQL Server database bypasses SCOM logic, corrupts database integrity constraints, breaks internal reporting systems, and invalidates product support.

Explanation for Option E (Incorrect): Reinstalling the SCOM Reporting Server only resets the SQL Server Reporting Services (SSRS) instances and web interfaces; it does not alter the storage structures or retention settings housed within the separate Data Warehouse database.

Explanation for Option F (Incorrect): Registry keys on the management servers control local processing variables, buffer sizes, and connection timeouts, but they do not control dataset retention parameters inside the centralized SQL Data Warehouse database.

This is a huge original question bank

You get support from instructors if you have questions

Each question has a detailed explanation

Mobile-compatible with the Udemy app