Computer Networks

Secure Shell (SSH) is a cryptographic network protocol for secure data communication. The standard TCP port for SSH is 22, used for secure logins, file transfers (scp, sftp), and port forwarding/tunneling.

Simple Network Management Protocol (SNMP) is used for network device management. SNMP agents listen on UDP port 161 for queries and commands from managers. SNMP traps (notifications) are sent to port 162.

Domain Name System (DNS) resolves domain names to IP addresses. DNS uses both TCP and UDP on port 53. UDP is used for standard queries due to its low overhead, while TCP is used for zone transfers and larger responses.

Network Time Protocol (NTP) is used to synchronize computer clocks over packet-switched networks. NTP uses UDP port 123 for time synchronization between network devices. Accurate timekeeping is critical for authentication, logging, and distributed systems.

SCSI-1 defined three primary layers: Application Layer (initiates commands), SCSI Command Layer (encapsulates CDBs), and SCSI Protocol Layer (handles signaling). The Programming Interface Layer was NOT formally defined in SCSI-1. This layer, which provides standardized APIs for applications to interact with SCSI devices, was introduced in later SCSI specifications (SCSI-2 and beyond). SCSI-1 focused on basic command and protocol definitions without formal programming interface standards.

The SCSI architectural model for distributed communication comprises exactly three layers: the SCSI Application Layer (client commands), SCSI Transport Layer (transport services), and Interconnect Layer (physical transport). Since all three options A, B, and C are valid layers in the standard SCSI model, the correct answer is 'None of the Above' - there is no fourth layer that would make any of these incorrect.

By default, SCSI devices initialize communication using asynchronous data transfer because it requires no negotiation or hardware capability agreement. If both devices support synchronous transfer, they negotiate it during the startup phase. Asynchronous is the default fall-back state for compatibility.

The Service Delivery Subsystem resides at the Interconnect Layer in the SCSI architectural model, handling the physical and logical transport of data between devices. The Application Layer handles client commands, and the Transport Layer provides transport services, while the Interconnect Layer implements the actual delivery mechanism through the SDS.

The SCSI Architecture Model (SAM) for distributed communication has exactly three layers: Application Layer (highest), Transport Layer (middle), and Interconnect Layer (lowest, physical). Since options A, B, and C are all valid SCSI layers, none of them is 'not a layer.' The double-negative construction makes this tricky, but 'None of the Above' correctly indicates that all listed options ARE actual layers.

SCSI-1 defined the core architectural layers: Application Layer, Command Layer, and Protocol Layer. The Programming Interface Layer was introduced in later SCSI specifications (SCSI-2 and beyond) to provide a standardized interface between applications and the SCSI device driver. This layer did not exist in the original SCSI-1 standard.

SCSI defaults to asynchronous data transfer mode, where each byte/word transfer requires handshaking signals (REQ/ACK) before the next can begin. Synchronous transfer is an optional negotiated mode that allows multiple data transfers per handshake cycle, improving throughput. 'Semi-synchronous' is not a standard SCSI transfer mode. The default is asynchronous for maximum compatibility.

The Service Delivery Subsystem resides at the Interconnect Layer, which is the lowest layer in the SCSI Architecture Model. This layer handles the physical and logical interconnection between SCSI devices, including cables, connectors, signaling protocols, and bus arbitration. The Application Layer handles command processing, and the Transport Layer manages data delivery.

TIBCO iProcess uses RPC (Remote Procedure Call) protocol for communication between Workspace clients and the Engine server. RPC enables two-way communication where clients can invoke procedures on the server. TCP-IP is the transport layer but RPC is the application protocol used. FTP, HTTP, and HTTPS are not used for this purpose.

RTE (Remote Terminal Emulator) protocol is specifically used in LoadRunner for testing terminal emulator and mainframe applications. HTTP is for web applications and RMI is for Java distributed objects.

Server.Transfer is faster than Response.Redirect because it executes entirely on the server without a round-trip to the client browser. Response.Redirect sends a 302 response to the browser, which then makes a new request to the target URL, incurring additional network latency. Server.Transfer simply transfers execution to another page on the same server.