Computer Networks

SCOM monitors non-Windows devices (like Unix/Linux) through SSH on port 22. The agentless monitoring uses SSH to communicate with the target system. The other options are incorrect protocols/ports for this purpose.

The Management Server communicates with SCOM agents primarily for health heartbeat and data collection. Typical agent communication is lightweight, involving small heartbeat signals and performance data at regular intervals. 500 bytes per second is the standard documented average bandwidth utilization for normal SCOM agent operations.

SCOM agents communicate with management servers on TCP port 5723, which is the default port configured for agent-to-server communication. This differs from port 5720 used for other SCOM communications, and standard ports like 80 or 1433 which are used for web and SQL traffic respectively.

Domain access requests are specifically handled through the MSNAccount system, which manages the authorization and provisioning workflow. MSNAlert, MSN Services, and generic MSN are not the correct channels for domain access requests. MSNAccount provides the proper access control and audit trail.

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.

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.

Network High Priority request tickets typically involve outage-related critical issues and require two-way escalation to GNS (Global Network Services) for proper handling and resolution. They are not treated as normal tickets or directly actioned by engineers without formal escalation.

This is a duplicate of question 151640. Network High Priority request tickets typically involve outage-related critical issues and require two-way escalation to GNS for proper handling and resolution.

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.

CLI (Call-Level Interface) manages the request and response communication flow between client applications and the Teradata database. TDP is a driver protocol, ODBC is a standardized interface, and MOSI is unrelated to request/response handling.

In Teradata database architecture, the Access Module Processor (AMP) is the vproc responsible for retrieving, processing, and storing database records. The Parsing Engine (PE) merely coordinates the request, parses SQL, and creates the execution plan, leaving the actual data manipulation and processing to the AMPs.

DHCP stands for Dynamic Host Configuration Protocol. It's a network management protocol used to dynamically assign IP addresses and other network configuration parameters to devices. The 'Dynamic' reflects that addresses are allocated automatically, 'Host' refers to network devices, and 'Configuration Protocol' describes its function of setting up network settings.

ARP stands for Address Resolution Protocol. It's used to map IP addresses to physical MAC addresses on a local network. The 'Resolution' part refers to resolving (discovering) the hardware address corresponding to a known IP address. This is essential for devices to communicate at the data link layer.

Node Manager communicates with the Administration Server using Secure Socket Layer (SSL) for secure communication. This ensures that administrative commands and server status information are transmitted securely. SSL provides encryption and authentication between Node Manager and the Admin server.

In network architectures like VIPNET, a server farm or pool represents a logical collection of multiple servers grouped together to distribute workloads or handle requests. It does not refer to all property-specific servers or physical switches like DIPs or VIPs.