Microsoft Operations Center (MOC) Incident Management

RACI is a standard project management acronym defining four key roles in decision-making processes: Responsible (does the work), Accountable (owns the decision), Consulted (provides input), and Informed (is notified of outcomes). The other options are plausible-sounding but incorrect expansions.

In Microsoft support operations, a QoS ticket represents customer feedback - either appreciation or negative feedback about service quality. The other options describe general network QoS concepts (Quality of Service, traffic prioritization) which are unrelated to Microsoft's specific ticketing terminology.

Microsoft's FY11 CSAT target required scores above 65% to avoid penalties. This was a specific contractual threshold in that fiscal year. The higher percentages (75%, 85%) represent aspirational targets but weren't the penalty avoidance threshold.

TCS delivers Microsoft support services from three key locations: Redmond (Washington, USA), Hyderabad (India), and Pune (India). These are established TCS delivery centers for Microsoft projects. Other options substitute different Indian cities that aren't the primary Microsoft service delivery locations.

QoS tickets are typically classified using High, Medium, and Low priority levels during triage. Severity levels (Sev 0-2) and priority numbers (Pri 1-3) are different classification systems used in incident management, not QoS triage.

A negative QoS ticket indicates the team failed to deliver expected quality of service. This is a performance metric where negative values represent below-par performance, not exceeding expectations.

MOC (Managed Operations Center) typically manages around 450 properties. This is a factual figure about infrastructure scale.

In the organizational hierarchy, if EOC represents a tower structure, then BOS represents a property group. This appears to be testing knowledge of organizational structure terminology.

Incident Engineering is responsible for providing accurate and timely status updates on incidents to both internal and external stakeholders. This is their core communication function during incident management.

Hi-Pri team manages coordination and communication for emergency and crisis situations affecting supported services. They handle high-priority incidents requiring immediate attention.

Hi-Pri management is responsible for taking notes throughout an incident and providing updates into UTS (Universal Ticketing System). This ensures proper documentation and tracking of incident progress.

Tier 0 support refers to automated systems that resolve incidents without human intervention. This is the first line of defense in IT service management, using automation to handle common issues.

The average volume of alarms expected monthly is approximately 200,000. This represents the typical alarm load in a large-scale IT operations environment.

iAdmin is the CMDB (Configuration Management Database) used in MOC. It tracks and manages configuration items and their relationships in the infrastructure.

The ticket creation process starts from the Alarm Console, followed by cutting a ticket, then TSG matching, severity classification, and finally assigning to severity queue. Option C has the correct sequence.

User and group management is performed through MSNAccounts, which is the designated system for managing user identities and group memberships in the environment.

Managed Automation service focuses on reducing incidents through strategic automation portfolio development and management. Option A correctly captures the proactive aim of incident reduction. CRON jobs (B) and infrastructure preparation (C) are tactical implementation details, not the strategic aim.

The New Property On-boarding service function specifically supports properties engaging MOC (Microsoft Operations Center) for incident management. This is the correct pairing. GFS (B) and WO (C) are not the correct incident management partners for this service function.

The network infrastructure spans 27 datacenters globally. This is a factual detail about the scale of GFS network operations. The other options (21, 15, 25) are incorrect counts.