Computer Networks

During AIX boot phase 2, cfgmgr runs the configuration methods for devices, which for network interfaces triggers the execution of rc.net to initialize TCP/IP. The rc.net script is called by the network device's configure method, not directly by init or inittab entries.

To ensure a net.tcp WCF service starts and runs continuously from boot, hosting in a managed Windows Service is the standard practice. While IIS 7.0 with WAS supports net.tcp, it starts services on-demand rather than starting them automatically at server boot unless specifically configured (like alwaysRunning, but the simple choice here is hosting in a Windows Service). Hosting in WPF is incorrect for headless background execution.

TransportWithMessageCredential mode combines SSL transport security with message credentials. The message sub-element must specify clientCredentialType (like UserName) for proper configuration. Option D uses 'MessageWithTransportCredential' which is not a valid security mode name.

wsHttpBinding supports multiple security modes including Transport, Message, and TransportWithMessageCredential. Message security can use Windows credentials or issued tokens (from an STS). The question correctly identifies issued token authentication as a supported option. Transport security with Windows is also supported, but Message with issued tokens is the best answer listed.

In WCF 4.0, default protocol mapping assigns basicHttpBinding to the http scheme, wsHttpBinding to the secure http scheme, and webHttpBinding to rest. The other options are incorrect because they represent non-default configurations or distinct bindings.

The mesg command controls whether other users can send messages to your terminal using write or wall commands. mesg n (no) restricts incoming messages, while mesg y (yes) allows them. This is a basic Unix/Linux command for terminal privacy. Options A, B, and C (mesp, mesn, mesk) are not standard Unix commands.

Remote Access Trojans (RATs) typically connect back to the attacker using Dynamic DNS Update Clients (DUC). Since attackers' systems often have dynamic IP addresses, DUC services (like no-ip) maintain a consistent hostname that updates automatically when the IP changes. Port forwarding is required but doesn't actively maintain the connection; backtrack is a Linux distribution for testing; php scripts may be attack vectors but not the connection mechanism itself.

DDoS (Distributed Denial of Service) shells/bots utilize multiple flooding protocols to overwhelm targets. UDP flooding is common due to UDP's connectionless nature; TCP flooding exploits the TCP handshake process (SYN floods); HTTP flooding targets web applications with legitimate-looking HTTP requests. DOS is not a specific flooding technique but the overall attack category.

no-ip.com is a well-known Dynamic DNS Update Client (DUC) service. It provides free and paid dynamic DNS services that allow users with dynamic IP addresses to have a static hostname that automatically updates when their IP changes. While other services like dyn.com also exist, no-ip.com is specifically recognized as a DUC provider in the context of RAT and malware callbacks for maintaining stable connections to dynamic-IP systems.

The inetd (internet super-server) daemon controls network services including POP3 mail service. inetd listens on multiple ports and spawns the appropriate service daemon (like pop3d) when a connection is requested, making it the controlling daemon.

In Apache Axis, incoming messages on the server side flow through three layers: Transport (HTTP, SMTP, etc. listeners receive the request) → Global (common handlers for all services process security, logging) → Service (specific service handlers execute business logic). This layered architecture allows cross-cutting concerns to be handled before service-specific processing.

The MQOutput node is designed to write messages to WebSphere MQ queues, which clients can then read. The question specifically asks about sending messages to clients that connect via Websphere MQ Enterprise Transport - this is the primary purpose of the MQOutput node. MQInput is for receiving from queues, MQGet retrieves a single message programmatically, and MQReply sends responses specifically to reply-to queues.

In Apache Axis, the client-side message path flows from the Service (where the application invokes the service), through Global handlers (which process all messages), and finally to the Transport layer (which handles the actual HTTP/SOAP transmission). This is the correct sequence for outbound messages on the client side.

The Filter Node is specifically designed to route messages based on their content. It evaluates conditions against message properties and directs messages to different output terminals based on those conditions. The Collector Node aggregates data, Label Node adds metadata, and neither performs content-based routing.

The default port for the Web services hub is 7333. This is a standard configuration setting for web services in certain systems.