IT Operations and Infrastructure Support

PII (Personally Identifiable Information) must NOT be put in ticket diaries as these are often accessible to unauthorized personnel. PII should be handled through secure, designated channels to protect customer privacy and comply with data protection regulations.

There are four EMT (Emergency Maintenance Team) types: Red (highest severity), Yellow, Orange, and Gray (lower severity). These color codes indicate different levels of urgency and impact. White is not a standard EMT classification type.

An issue must cause a service disruption to be classified as an outage. Not all issues rise to the level of an outage - some may be degraded service, potential issues, or problems that don't significantly impact service availability.

Escalation is appropriate when you have been explicitly asked to do so, when TSG (Technical Support Group) has directed it, or when you have completed all required troubleshooting steps in your instructions. Escalating simply 'because you feel like it' without following proper procedures is not appropriate, as it bypasses established workflows and may unnecessarily burden higher-level support teams.

The correct workflow involves using Octane and TSG (Technical Support Group) as the primary steps. iAdmin and UTS appear to be incorrect or incomplete steps in this process. This question tests knowledge of the standard operating procedures and system hierarchy for handling technical issues in this environment.

Work tracking must be done in official systems: UTS (likely a ticketing or tracking system) and IMC (Incident Management Console or similar). Personal tools like Notepad or Word are inappropriate for official work tracking as they don't provide visibility, accountability, or integration with the team's workflow systems.

IS/OOS (In-Service/Out-of-Service) operations for servers can be performed through ATMS, Vipnet, or IMC. iAdmin is not the correct tool for this specific operation. Option E ('All of the above') is incorrect because iAdmin is not a valid option, even though it's presented as a separate choice.

Replication and mirroring are critical for SQL Server as they provide data redundancy, high availability, and disaster recovery capabilities. 'Yes' and 'Definitely' both affirm the importance, though they differ in emphasis. 'No' and 'Sometimes' are incorrect because these are standard best practices for production SQL Server environments to prevent data loss and minimize downtime.

ATM (or ATMS) and VIPNET are the designated tools for performing IS/OOS (In-Service/Out-of-Service) operations on servers. iAdmin and UTS serve different purposes and are not the correct tools for this specific server state change operation. This tests knowledge of the correct administrative interfaces for server lifecycle management.

A technical bridge does not have multiple notifications to be sent - it is a single communication channel or conference. The correct answer is False. Technical bridges are typically established for specific incidents or discussions and involve one coordinated communication session, not multiple separate notifications.

Alarms in this environment originate from monitoring systems: MOM (Microsoft Operations Manager) and SCOM (System Center Operations Manager). These are enterprise monitoring tools that track system health and generate alerts. Email and Call are communication channels for responding to alarms, not sources of the alarms themselves.

Before escalating tickets to property, approval is required from AOD (likely Authority on Duty), OM (Operations Manager), or ShiftLead. Peers cannot authorize escalation to property level. Option E is incorrect because peers are not valid approvers. This ensures proper chain of command and prevents unnecessary escalations.

All network high priority issues do not follow the standard MOC (Mission Operations Center) internal and external notification process - they have their own specific notification methods. This is an exception to standard procedures due to the critical nature of network high priority incidents, which require specialized handling and communication channels.

For recurring daily issues that show a trend, you should create a PM (Preventive Maintenance) ticket for proper investigation and root cause analysis. Additionally, you should document the pattern. Simply opening request tickets or following up periodically doesn't address the underlying trend. PM tickets trigger structured investigation processes.

It is NOT acceptable to two-way escalate a low priority ticket. Two-way escalation typically involves higher levels of management coordination and is reserved for critical or high-priority issues that require immediate attention across multiple teams. Low priority tickets should follow standard escalation paths if necessary, but do not warrant two-way escalation.

Low priority tickets still require proper resolution or closure procedures. They cannot simply be closed without any action taken, as this would leave the underlying request unaddressed.

High priority tickets require formal escalation procedures to ensure proper visibility and action. Two-way escalation via T0ES to DCS ensures acknowledgment and tracking of critical issues.

Auto Append Requests require tracking elements to ensure proper routing, accountability, and auditability. Making requests without tracking elements would make it impossible to monitor or manage them.

When a DCS Request ticket is returned to a property owner, it does not require two-way escalation. The return to the owner is part of the normal workflow, not an escalation scenario.

Request tickets typically require input from the customer who needs the service or has the issue. The customer provides the necessary details about what they need, which is then processed by the support team.