All MCQs

The loopback address routes packets internally to the local machine without using an external network link.
It is useful for testing network services and local client-server communication.

A socket is a communication endpoint identified by addressing information and a transport protocol.
It supports local or networked process communication depending on the socket family.

A message queue preserves message boundaries and decouples sending from immediate receiving.
The kernel manages the queue and its access rules.

A half-duplex pipe provides one directional data path at a time.
Two pipes may be used when independent two-way communication is required.

A named pipe appears as a file-system object and can connect processes without a parent-child relationship.
An anonymous pipe is usually inherited through process creation.

An ordinary pipe provides a byte-stream channel often used between related processes such as a parent and child.
It is not a memory-protection or storage-allocation structure.

A zero-capacity link stores no waiting messages, so send and receive must synchronize directly.
This interaction is commonly called a rendezvous.

Bounded-capacity buffering permits only a fixed number of queued messages.
A sender may have to wait when all available buffer slots are occupied.

A blocking receive suspends the caller when no suitable message is available.
The process becomes runnable again after a matching message arrives.

A nonblocking send lets the sender continue after submitting the message.
Delivery or reception may complete later depending on buffering and IPC semantics.

A blocking send suspends the sender until the system or receiver has accepted the message as defined.
A nonblocking send returns control without waiting for that condition.

Indirect communication associates messages with a mailbox, port, or message queue.
Processes communicate by referring to that shared communication object.