IT Operations Tools and Systems

In MSChange, to find the resources assigned to deploying a change, you navigate to the Dates and Resources tab and look at Assigned Resource. This tab combines scheduling (dates) with personnel assignment (resources). Option D is incorrect because it points to 'unassigned' Resource, and options A and C don't specify the correct combined tab.

In MSChange, the rollback plan (used when a change fails) is found in Deployment Details -> Rollback Plan. A rollback plan specifically outlines how to reverse or undo a failed deployment. Option B uses Release Details which is incorrect, and options C and D within Deployment Details point to different plans (Release and Backup) that are not specifically for handling failures.

In MSChange, the URL to find all active changes for all properties is http://ocimres/change/. Option A uses HTTPS which is incorrect, and options C and D have incorrect paths ('chng/' and 'changed/' instead of 'change/'). This is a straightforward URL recollection question testing knowledge of the specific internal tool path.

In MSChange, when you need to make a change to a service or property to resolve an active incident, you must complete an Emergency RFC (Request for Change). Emergency RFCs are specifically designed for urgent changes required to fix incidents or restore service. Normal RFCs and Standard RFCs are for planned, non-urgent changes that go through the standard approval and scheduling process.

When an incident is discovered to be caused by a change, ITIL best practices require linking the two records to establish traceability. Attaching the incident to the Request for Change (RFC) documents the impact and helps track change-related issues. It does not get attached to Problem records (which are for unknown root causes) nor escalated automatically.

The MSChange workflow uses the Impact tab to manage incident relationships. Clicking 'Create Incident' from the Impact tab establishes the proper linkage between the RFC and the incident record. This is the designated path within the tool's interface for this action.

ATMS uses the 'unsuppress' command with the /servername flag followed by the server name. This matches the pattern of other ATMS commands where the full parameter name is used. The colon separates the flag from the value.

ATMS (Advanced Server Management Tool) is the command-line interface tool designed for checking server states including Out of Service (OOS) and In Service (IS) status. This is consistent with the other ATMS-related questions in this set.

The ATMS command to mark a server as Out of Service is 'oos /servername:SERVERNAME'. This follows the standard ATMS syntax pattern where the action comes first, followed by the full parameter name with a colon separator.

When an object is marked 'Asset Only' in iAdmin, it means the monitoring system tracks the asset's existence but does not actively monitor it. Alarms generated for this object are ignored rather than deleted, restored, or escalated. The object remains in inventory but produces no alerts.

The ATMS command to mark a server as In Service (IS) is 'is /servername:SERVERNAME'. This follows the established ATMS syntax pattern with the colon separating the flag from the server name value.

The ATMS command to suppress a server is 'suppress /servername:SERVERNAME'. This uses the full command 'suppress' (not the abbreviated 'supp') and the /servername flag with colon separator, consistent with other ATMS commands.

OLA Watcher provides a Filter button in the interface that allows users to filter displayed tickets based on various criteria. This is the standard UI pattern for filtering in this tool, accessed directly through a labeled button.

In OLA Watcher, an orange ticket indicates a SLA breach - the ticket has exceeded its agreed-upon response or resolution time. This color coding provides immediate visual indication of tickets requiring urgent attention. Green typically means within SLA, and other colors may represent different states.

Standard server suppression has time limits (typically 72 hours maximum). To suppress an asset for longer periods, a maintenance ticket must be created. This provides proper documentation and approval for extended maintenance windows, unlike regular on-hold or WIP tickets.

In iAdmin search functionality, the asterisk (*) serves as a wildcard character that matches any sequence of characters. This allows for flexible searching when you need to find items that match a pattern rather than an exact string. Option A correctly identifies the asterisk as the wildcard character.

MOG stands for Monitored Object Group, which is a collection of monitored objects that can be managed together in monitoring systems. Option B correctly identifies this standard terminology used in network and application monitoring contexts. Option A incorrectly suggests 'Ground' instead of 'Group'.

In UTS (Universal Ticketing System), after making changes to a ticket, users must click the 'Save Ticket' button to persist those changes. This is standard UI behavior for transaction systems - changes are not committed until explicitly saved. Options B (OK), C (Cancel), and D (Delete) perform different actions.