Question 1

In Microsoft Windows print services, how do you correctly configure a printer pool to increase availability and throughput?

Accepted Answer

Introduction / Context: Printer pooling in Windows allows a single logical printer to distribute jobs across several identical printers. This improves availability and reduces wait times without requiring users to choose among many device names. Understanding the correct association is key to configuring a reliable print pool. Given Data / Assumptions: Printers are functionally identical and use the same driver. Clients submit jobs to one shared logical printer. The print server controls job routing to available devices. Concept / Approach: A printer pool is configured by creating one logical printer object and binding it to multiple ports, each port corresponding to a separate physical print device. The operating system automatically dispatches queued jobs to the first available device, balancing load and tolerating individual device outages. Step-by-Step Solution: Install the correct driver once for the logical printer.Enable ‘‘Enable printer pooling’’ in printer properties.Select multiple ports (for example, IP_10.0.0.21, IP_10.0.0.22), each mapping to a different printer.Share the single logical printer; clients print to the shared name and are transparently load-balanced. Verification / Alternative check: Pause one device or unplug it; print jobs continue on the remaining devices, demonstrating higher availability. Check the print queue details to see routing decisions. Why Other Options Are Wrong: One device with multiple logical printers creates user confusion and does not pool capacity. Multiple devices with multiple logical printers is not pooling; it is parallel but manual selection. One port with multiple logical printers is still a single physical device; no pooling occurs. Common Pitfalls: Pooling printers with different models or drivers can cause rendering issues; always use identical devices and drivers. Also verify that finishing options (duplex units, trays) match across devices. Final Answer: Associate multiple physical print devices with one logical printer

Question 2

Within the OSI/TCP-IP model mapping, what is the core responsibility of the transport layer (transport protocol)?

Accepted Answer

Introduction / Context: The transport layer sits between application protocols and the network layer. It segments application data, assigns ports, and may provide reliability, ordering, and congestion/flow control. Understanding its role clarifies how TCP and UDP differ and how applications map to endpoints. Given Data / Assumptions: We model communications using the OSI reference and the TCP/IP suite. Transport protocols include TCP (reliable, connection-oriented) and UDP (connectionless, minimal services). We want the definition that best captures end-to-end logical connections and reliability. Concept / Approach: The transport layer builds logical associations between processes (ports) on hosts, coordinating segmentation/reassembly. TCP provides reliable, ordered delivery, flow control, and congestion control. UDP provides multiplexing and optional checksum without connection state. Presentation (data representation) and session (dialog management) are higher-layer concerns; adapter control is lower-layer (data link/physical). Step-by-Step Solution: Identify end-to-end focus: process-to-process, not merely host-to-host.Match ‘‘reliable transfer’’ and ‘‘connections’’ to TCP’s services.Eliminate options that describe presentation/session or NIC management.Select the transport-centric description. Verification / Alternative check: Examine TCP headers (ports, sequence, acknowledgment numbers) and behavior (retransmissions, sliding windows). This confirms the transport layer’s reliability role, separate from routing (network) and framing (data link). Why Other Options Are Wrong: Presentation/session responsibilities do not belong to the transport layer. Adapter management belongs to the data link/physical layers and drivers. ‘‘None of the above’’ is incorrect because one option correctly describes transport. Common Pitfalls: Confusing TCP (transport) with IP (network) or assuming UDP provides reliability; reliability on UDP must be implemented by the application. Final Answer: Establishes logical end-to-end connections and supports reliable data transfer between communicating computers

Question 3

Windows NT domain trusts: TUNA trusts BASS (one-way). You want user Lisa from BASS to administer the TUNA domain during your absence. Which group configuration enables this cross-domain administration correctly?

Accepted Answer

Introduction / Context: Classic Windows NT domain administration employs well-known group scoping rules and trust relationships. With a one-way trust where TUNA trusts BASS, TUNA may assign permissions to security principals from BASS. Using the correct combination of global and local groups is crucial for least privilege and manageability. Given Data / Assumptions: One-way trust: TUNA trusts BASS (TUNA accepts BASS identities). Goal: allow BASS\Lisa to administer TUNA. We must respect NT group scope semantics (Global vs Local groups). Concept / Approach: Global groups contain user accounts from their own domain; local groups (on a member server or domain local in later models) grant rights on resources. Best practice: put users into a global group in their account domain, then add that global group to a local Administrators group in the resource domain. Because TUNA trusts BASS, TUNA can place a BASS global group into its local Administrators. Step-by-Step Solution: Create BASS\Gbl-Admins and add BASS\Lisa to it.On a TUNA server or in domain local context, add BASS\Gbl-Admins to TUNA's local Administrators.Trust allows TUNA to validate BASS identities and grant rights accordingly.Lisa now has administrative rights in TUNA while the trust is in place. Verification / Alternative check: Log in as BASS\Lisa and open Computer Management on a TUNA server; verify administrative tasks are permitted. Audit group membership to confirm effective rights. Why Other Options Are Wrong: Adding foreign users directly to Domain Admins or using local groups in the wrong domain violates scope rules or least privilege. Nesting a BASS local group into a TUNA global group is not valid; global groups cannot contain accounts from other domains. Common Pitfalls: Confusing global vs local scope nesting rules and granting Domain Admins unnecessarily, which over-privileges the user beyond the specific administrative need. Final Answer: Create a global group in BASS (Gbl-Admins) containing Lisa, and add BASS\Gbl-Admins to the local Administrators group in TUNA

Question 4

A department of 15 engineers needs team-only access to shared data, with frequent staff changes and no single designated admin. Which Windows workgroup/domain model best fits this scenario?

Accepted Answer

Introduction / Context: Choosing between a workgroup and a domain hinges on administrative centralization, policy needs, and scale. In small teams with fluid membership and no appointed administrator, minimizing central dependencies while still controlling access to shared data can be practical. Given Data / Assumptions: Team size is small (about 15 engineers). Frequent arrivals and departures make centralized account lifecycle management challenging. Data must be accessible only to team members (not the entire organization). No single administrator is identified to manage a domain infrastructure. Concept / Approach: A workgroup allows local control on each machine, ad-hoc file sharing, and NTFS permissions to restrict access to the team. While domains provide stronger centralized control (Group Policy, centralized authentication), they require domain controller management and clear administrative roles. For this scenario’s constraints, a workgroup satisfies the ‘‘no single admin’’ requirement while still enabling engineers to protect and share resources locally. Step-by-Step Solution: Create local accounts (or use shared credentials) limited to team members on the file host(s).Configure NTFS/share permissions so only those accounts access the team data.Delegate routine tasks to individual engineers for their own computers.Revoke departing members by removing their local accounts from the share host(s). Verification / Alternative check: Test access from a non-team machine/user; permissions should deny entry. Confirm that team members can read/write as required. Assess administrative overhead versus a small domain—if later growth occurs, migrating to a domain may be justified. Why Other Options Are Wrong: Single/master domain models centralize administration and require defined admins; not aligned with ‘‘no single administrator’’ constraint. A complete trust mesh is complex and unnecessary; it does not inherently solve access control better than a simple workgroup for such a small team. Common Pitfalls: Using the same local password across many machines can be risky. Document procedures for onboarding/offboarding to keep permissions current. Final Answer: A workgroup mode, with each engineer administering his or her own computer

Question 5

You are adding a dial-up remote access server to a TCP/IP network. The data link protocol must support secure authentication for users. Which protocol should you choose for the dial-up link?

Accepted Answer

Introduction / Context: Dial-up remote access historically relied on data link protocols that framed IP packets over serial lines. Security requirements include authenticating the user before granting network access. Different protocols offer different levels of built-in authentication support. Given Data / Assumptions: Transport is a serial dial-up line terminating on a remote access server. IP is the network protocol in use. Secure authentication (for example, CHAP) is required. Concept / Approach: PPP (Point-to-Point Protocol) encapsulates network protocols over serial links and includes Link Control Protocol (LCP) for negotiating options and Authentication Control Protocols supporting PAP, CHAP, MS-CHAP, and EAP. SLIP predates PPP and has no standard authentication or configuration negotiation. DLC is an IBM protocol not suited for IP dial-up authentication, and PPTP is a VPN tunneling method that itself commonly runs over PPP sessions. Step-by-Step Solution: Identify need: data link encapsulation with built-in user authentication.Map to PPP features: LCP negotiation + CHAP/MS-CHAP/EAP support.Eliminate SLIP (no authentication), DLC (not appropriate), and note PPTP runs on top of PPP.Choose PPP as the secure dial-up data link protocol. Verification / Alternative check: Historical RAS configurations on Windows/Unix default to PPP with CHAP/MS-CHAP. Packet traces show PPP LCP authentication exchanges prior to IPCP (IP Control Protocol) address assignment. Why Other Options Are Wrong: SLIP: No authentication or option negotiation. PPTP: A tunneling protocol that typically encapsulates PPP; not the base serial link protocol. DLC: Not designed for IP dial-up and lacks the needed authentication frameworks. Common Pitfalls: Confusing application/VPN protocols with link protocols. Ensure strong authentication (for example, MS-CHAPv2/EAP) and consider encryption at higher layers if needed. Final Answer: PPP

Question 6

Evaluate the statement: “Most routers can also act as bridges.” Is this generally true in networking practice?

Accepted Answer

Introduction / Context: Routers and bridges (switches) operate at different layers of the networking stack: routers at Layer 3 (network), bridges/switches at Layer 2 (data link). Although some modern devices are ‘‘multifunction’’ (for example, home gateways combining routing, switching, and access point functions), the statement about “most routers” is misleading in classical networking terms. Given Data / Assumptions: ‘‘Router’’ refers to a Layer-3 device that forwards packets between IP subnets. ‘‘Bridge’’ refers to a Layer-2 device that forwards frames based on MAC addresses. Enterprise/classical context is assumed rather than consumer all-in-one devices. Concept / Approach: Routers and bridges serve distinct roles. A router does not inherently perform transparent bridging between interfaces; it routes between different subnets. Conversely, a bridge does not perform Layer-3 forwarding. While some platforms support both features (for example, bridge groups, BVI interfaces), that capability is model-specific and not universal across “most” routers, especially historically. Step-by-Step Solution: Differentiate L2 and L3 functions: bridging vs routing.Recognize that typical routers route IP and do not bridge frames by default.Note exceptions exist (integrated services routers, home gateways), but they do not define “most routers”.Conclude the general statement is false. Verification / Alternative check: Review router interface configuration defaults: interfaces are routed ports, not switchports; bridging requires explicit configuration or specific hardware modules (switching blades) not present on all routers. Why Other Options Are Wrong: ‘‘True’’ overgeneralizes from combo devices to the entire router category. ‘‘Only when STP is disabled’’ and ‘‘Only on wireless routers’’ are unrelated caveats that mischaracterize bridging. ‘‘None of the above’’ is incorrect because the correct evaluation is “False”. Common Pitfalls: Assuming consumer ‘‘Wi-Fi routers’’ (which include a switch and AP) reflect professional router capabilities. In enterprise environments, routing and switching roles are often distinct. Final Answer: False

Question 7

Regarding Dynamic Host Configuration Protocol (DHCP), which statement correctly describes a core benefit of using DHCP on IPv4 networks?

Accepted Answer

Introduction / Context: Dynamic Host Configuration Protocol (DHCP) automates IPv4 client configuration by leasing IP addresses and related parameters (subnet mask, default gateway, DNS). It is central to scalable network operations, especially where devices frequently join or leave the network. Given Data / Assumptions: Clients require IP parameters without manual entry. Address conflicts and configuration typos must be minimized. We compare DHCP to older or alternative mechanisms. Concept / Approach: DHCP assigns addresses from managed scopes and tracks active leases, ensuring that two devices are not handed the same address simultaneously. It also reclaims addresses after lease expiry, supporting address reuse. While DHCP evolved from BOOTP, it is not identical; it adds leasing, options, and dynamic allocation beyond BOOTP’s static mapping model. Step-by-Step Solution: Clients broadcast a discovery; a DHCP server offers an address from a free pool.The client requests the offer; the server acknowledges and records the lease.During the lease, the server will not assign that address to another client.On lease expiry or release, the address returns to the pool for reuse. Verification / Alternative check: Monitor a DHCP server’s scope utilization and conflict detection logs; observe that duplicate allocation is prevented and leases are recycled. Use ‘‘ipconfig /renew’’ or ‘‘dhclient’’ to test the process. Why Other Options Are Wrong: ‘‘same as BOOTP’’: Incorrect; DHCP extends BOOTP with leasing and many options. ‘‘static allocation only’’: DHCP supports dynamic, automatic, and manual (reservation) modes. ‘‘addresses can never be reused’’: False; leases explicitly allow reuse after expiration. Common Pitfalls: Relying on APIPA (169.254.0.0/16) when DHCP fails; this does not prevent conflicts across subnets. Always ensure proper scope sizing and avoid overlapping scopes across multiple DHCP servers without coordination. Final Answer: helps prevent conflicts between assigned IP addresses

Question 8

On legacy ISA-bus PCs, you are installing network adapters in 20 computers. What configuration rule must be followed regarding hardware interrupts (IRQs) when installing the adapters alongside other add-in cards?

Accepted Answer

Introduction / Context: ISA-bus era PCs relied on manual configuration of hardware interrupts (IRQs), I/O port addresses, and DMA channels for add-in cards such as network interface cards (NICs), sound cards, modems, and SCSI adapters. This question checks whether you know the fundamental rule that prevents interrupt conflicts that can freeze systems or cause intermittent device failures. Given Data / Assumptions: Each computer has multiple ISA adapters installed (NIC plus other cards). ISA cards commonly use fixed or jumper-selectable IRQ lines. Plug and Play support is limited or absent; the OS cannot reliably arbitrate conflicting IRQs. We are configuring each individual PC; cross-machine IRQ settings do not interact over the LAN. Concept / Approach: An IRQ line is a hardware signal a device raises to get CPU attention. On classic ISA systems, two devices sharing the same IRQ typically contend for service, causing missed interrupts and driver instability. Therefore, within a single PC, every active device must occupy a unique IRQ. Network-wide uniformity of IRQs is meaningless because interrupts are local to each host’s motherboard. Step-by-Step Solution: Identify the scope: configuration occurs per computer, not across all PCs.Recall ISA limitations: no robust shared-interrupt scheme; sharing produces conflicts.Rule: assign each device in the same PC a distinct IRQ (e.g., NIC on IRQ 10, modem on IRQ 3, COM1 on IRQ 4, LPT1 on IRQ 7).Validate: after unique assignments, run diagnostics and check Device Manager (or DOS utilities) to confirm no conflicts. Verification / Alternative check: Practical tests show that two ISA devices on the same IRQ lead to dropped packets (for NICs), lockups, or failure to initialize drivers. Unique IRQ assignments eliminate these symptoms. Why Other Options Are Wrong: All same IRQ (per PC): Causes immediate interrupt conflicts. All NICs same IRQ across network: Irrelevant; IRQs are local per motherboard. All NICs different IRQs across network: Also irrelevant between separate machines. None of the above: Incorrect because unique per-PC IRQs are required. Common Pitfalls: Confusing per-machine configuration with network-wide standards; believing drivers will “share” ISA IRQs safely; ignoring serial/parallel defaults (COM1 IRQ 4, COM2 IRQ 3, LPT1 IRQ 7) when assigning the NIC. Final Answer: All adapters in a computer, including the network adapter, must be set to different IRQs

Question 9

Windows NT domains: in a one-way trust where RESEARCH trusts TESTING, a user in the TESTING\Testers global group needs access to a share on a Windows NT Advanced Server in RESEARCH. What action enables access?

Accepted Answer

Introduction / Context: Classic Windows NT domain trusts distinguish between account domains (hold user and global groups) and resource domains (host servers and shares). A one-way trust of RESEARCH → TESTING (RESEARCH trusts TESTING) allows RESEARCH servers to authenticate users and groups from TESTING, but access still depends on explicit permissions granted on the resource. Given Data / Assumptions: Trust direction: RESEARCH trusts TESTING (RESEARCH accepts TESTING identities). User is a member of TESTING\Testers global group. Guest accounts are disabled in both domains. Target: a shared directory on a RESEARCH server. Concept / Approach: With a one-way trust, the resource domain must assign access control entries (ACEs) to accounts or groups from the trusted domain. Global groups from the account domain (TESTING) are best practice for permission assignment in the resource domain (RESEARCH). The user does not need to log on to RESEARCH; logging on to TESTING provides credentials that RESEARCH can validate via the trust relationship. Step-by-Step Solution: Confirm trust direction allows RESEARCH to recognize TESTING identities.Add TESTING\Testers to the ACL of the shared directory on the RESEARCH server with the required permissions.User logs on to TESTING as usual; access is granted based on the ACL containing the TESTING group.No change to domain membership or Guest status is necessary. Verification / Alternative check: Windows NT domain design guidelines recommend “Global groups from account domain into local groups on resource domain, then assign permissions,” confirming the approach works without cross-domain logon changes. Why Other Options Are Wrong: No action: Wrong because permissions must be granted on the RESEARCH share. Grant permissions and require logon to RESEARCH: Unnecessary; trust provides cross-domain authentication. None of the above: Incorrect because assigning permissions to the Testers group in RESEARCH is sufficient. Common Pitfalls: Misreading trust direction; assuming users must log on to the resource domain; granting rights to individual users instead of using global groups. Final Answer: The Testers group must be assigned permissions to the shared directory on the Windows NT Advanced Server in the RESEARCH domain

Question 10

Domain trust design: all users belong to the ACE account domain; most resources are in PUBS and CAD resource domains. With the fewest trusts, how can you let ACE users access all resources?

Accepted Answer

Introduction / Context: In classic Windows NT multi-domain models, a common pattern is one account domain for users and passwords and multiple resource domains for servers and shares. You minimize the number of trusts by having each resource domain trust the account domain, so all resources can authenticate users from the single account domain. Given Data / Assumptions: Users reside in ACE (account domain). Resources reside in PUBS and CAD (resource domains). Goal: minimal trust relationships while enabling access. One-way trust semantics: if X trusts Y, then X accepts Y’s accounts for authentication. Concept / Approach: To allow ACE users to access PUBS and CAD, each resource domain must accept (trust) ACE. This requires two one-way trusts: PUBS → ACE and CAD → ACE. No need for ACE to trust PUBS/CAD because ACE does not need to accept their identities. Permissions are then granted to ACE global groups on resources in PUBS and CAD. Step-by-Step Solution: Identify account vs. resource domains.Set one-way trusts from each resource domain to the account domain.Assign ACLs in resource domains to ACE global groups.Verify access by logging on to ACE and reaching PUBS/CAD shares. Verification / Alternative check: The well-known “master account domain/resource domain” design prescribes exactly this trust direction to centralize users and decentralize resources with minimal trusts. Why Other Options Are Wrong: ACE trusts PUBS/CAD: That would let ACE accept identities from resource domains, which is unnecessary and does not help PUBS/CAD accept ACE users. Cross or mixed trusts: Add complexity without benefit in this scenario. None of the above: Incorrect because the minimal two trusts are clearly defined. Common Pitfalls: Reversing trust direction; creating redundant bidirectional trusts; granting permissions to users directly instead of groups. Final Answer: Establish one-way trusts: PUBS trusts ACE; CAD trusts ACE

Question 11

Two Ethernet LANs are connected by a router (TCP/IP). A newly added client can only access hosts on its own side of the router, while all other hosts intercommunicate normally. What is the most likely cause?

Accepted Answer

Introduction / Context: When a single new client can reach only same-subnet hosts but not remote subnets across a router, a layer-3 addressing or masking problem on that client is the prime suspect. Routers forward between different IP networks; incorrect masks cause wrong on-link/off-link decisions and failed default-gateway use. Given Data / Assumptions: Two Ethernet networks connected by a router. All other hosts communicate properly across the router. The new client can reach only local hosts. Physical links and router are functioning for everyone else. Concept / Approach: The subnet mask determines which IPs are considered local. If the mask is too wide or mismatched, the client may believe remote hosts are on its local subnet, sending ARP requests instead of packets to the default gateway. Those ARPs fail across the router boundary, breaking remote connectivity, while local connectivity remains fine. Step-by-Step Solution: Compare the client’s IP/mask/gateway to a working host on the same LAN.If the mask differs (e.g., /16 instead of /24), correct it to match the site plan.Flush ARP cache or renew DHCP lease; test remote pings via the router.Confirm that default gateway is reachable and being used for off-subnet traffic. Verification / Alternative check: Packet capture on the client shows ARPs for remote IPs when the mask is wrong; after fixing the mask, traffic goes to the gateway MAC and routing succeeds. Why Other Options Are Wrong: Termination/repeater faults: Layer-1/2 issues would affect multiple hosts, not only the new client. Defective router NIC: Others would fail too; symptoms are isolated to one client. None of the above: The wrong mask neatly explains the behavior. Common Pitfalls: Blaming DNS; DNS may resolve, but reachability fails due to incorrect on-link decision from the bad mask. Final Answer: Incorrect subnet mask on your client computer

Question 12

You installed Windows NT Server as a Backup Domain Controller (BDC) but accidentally joined the wrong domain name during setup. What is the correct remediation?

Accepted Answer

Introduction / Context: In Windows NT domain architecture, a Backup Domain Controller (BDC) is tightly bound to its domain at installation. Unlike a stand-alone server or member server, you cannot simply rename the domain affiliation of a BDC post-install. This question tests knowledge of immutable domain bindings in NT 4.0 era setups. Given Data / Assumptions: Server role: Backup Domain Controller. Wrong domain name specified during setup. Goal: associate the BDC with the correct domain. Concept / Approach: A BDC maintains a secure trust relationship, SAM database synchronization, and role metadata bound to a specific domain. NT does not support switching a BDC to another domain via GUI, registry edits, or repair utilities. The supported method is to reinstall NT Server and join the correct domain during setup so that security identifiers and replication partnerships are established properly. Step-by-Step Solution: Back up necessary data (if any) that resides locally.Perform a clean reinstall of Windows NT Server.During setup, choose “Backup Domain Controller” and enter the correct domain name.Verify replication from the Primary Domain Controller after the install. Verification / Alternative check: Microsoft deployment guidance for NT domains explicitly states that BDC domain membership cannot be changed after installation without reinstalling, confirming this remedy. Why Other Options Are Wrong: Control Panel / Registry / Emergency Repair Disk: None can rebind a BDC to a different domain; attempts lead to inconsistent security and replication state. None of the above: Incorrect because reinstall is correct. Common Pitfalls: Trying to hack the registry to change domain affiliation; promoting to PDC or demoting is not supported in NT 4.0 like modern Active Directory. Final Answer: Reinstall Windows NT Server

Question 13

Why does a high volume of broadcast traffic degrade overall LAN performance?

Accepted Answer

Introduction / Context: Broadcasts are frames addressed to all nodes on a broadcast domain (e.g., IPv4 ARP requests or certain service announcements). While essential for some protocols, excessive broadcasts create CPU and bus overhead on every endpoint and on Layer-2 infrastructure, reducing effective throughput for useful unicast traffic. Given Data / Assumptions: A shared Ethernet or switched LAN with one or more broadcast domains. High broadcast rates caused by chatty protocols, misconfiguration, or storms. Endpoints must receive Layer-2 broadcasts by design. Concept / Approach: Unlike unicast, which is delivered only to the addressed host, broadcasts are delivered to all hosts in the VLAN/broadcast domain. Each host’s NIC and OS networking stack must interrupt, DMA, or otherwise handle the broadcast frame long enough to decide whether to pass it up or drop it. This per-host processing scales linearly with the number of endpoints and directly competes with normal application traffic for CPU and interrupt time. Step-by-Step Solution: Recognize that broadcast frames are replicated to every port in the broadcast domain.Each station’s NIC receives and the OS processes the frame header, increasing CPU/interrupt load.Switches also must flood broadcasts to all ports in the VLAN, consuming fabric bandwidth.As broadcast rate rises, cumulative overhead rises for every node, degrading perceived performance. Verification / Alternative check: Monitoring tools (SPAN/mirror ports) show rising CPU on endpoints and elevated switch counters (broadcast storms). Limiting broadcasts or segmenting VLANs restores performance, confirming causality. Why Other Options Are Wrong: Acknowledgements are not required for Layer-2 broadcasts; Ethernet does not solicit per-host ACKs. Transmission lockout until ACK: Not how Ethernet works. Automatically routed to every segment: Routers block broadcasts between subnets by default. None of the above: Incorrect because endpoint processing is the real reason. Common Pitfalls: Assuming switches “eat” broadcasts; they must flood within the VLAN. Confusing broadcast with multicast or unicast flooding behavior. Final Answer: Every computer on the network must process each broadcast message

Question 14

IRQ planning: given a PC with COM1 on IRQ 4 (mouse), a modem on COM2 using IRQ 3, a SCSI host adapter on IRQ 5, and a sound card on IRQ 11, which supported IRQ could you assign to the new network interface card without conflicts?

Accepted Answer

Introduction / Context: Legacy PCs required careful manual assignment of IRQs to avoid conflicts between ISA devices. This scenario asks you to choose a free interrupt for a NIC when several common IRQs are already taken by serial ports, a SCSI controller, and a sound card. Given Data / Assumptions: COM1 (mouse) uses IRQ 4. COM2 (modem) uses IRQ 3. SCSI host adapter uses IRQ 5. Sound card uses IRQ 11. NIC supports IRQs: 2, 3, 4, 5, 9, 10, 11. Standard LPT1 uses IRQ 7; IDE uses 14/15 (not conflicting here). Concept / Approach: Pick an IRQ not already used. 4 and 3 are busy (serial ports), 5 is busy (SCSI), and 11 is busy (sound). IRQ 2 historically cascades to IRQ 9 on AT-class machines; many configurations prefer avoiding 2/9 unless planned carefully. IRQ 10 is commonly free and a traditional choice for NICs, ensuring no overlap with existing devices. Step-by-Step Solution: Eliminate IRQs already occupied: 3, 4, 5, 11.Consider IRQ 2/9 mapping: may work, but can conflict with other devices using 9; conservative choice avoids it.Select IRQ 10 as free and supported by the NIC.Verify by boot tests and diagnostics for interrupt sharing errors. Verification / Alternative check: Historical configuration guides list IRQ 10 as a common, conflict-free selection for network cards when 3/4/5/7/11 are taken. Why Other Options Are Wrong: 2: Often tied to 9; may create hidden conflicts. 4: Already used by COM1. 5: Used by SCSI adapter. None of the above: Incorrect because IRQ 10 is suitable. Common Pitfalls: Overlooking the IRQ 2↔9 cascade; forgetting default serial/parallel assignments; choosing an IRQ used by Plug and Play devices. Final Answer: 10

Question 15

Cabling a 10Base2 Ethernet: donated adapters are 10Base2 (thin Ethernet) and some ARCnet coax cards. Which coaxial cable type should be used to wire a reliable 10Base2 Ethernet segment?

Accepted Answer

Introduction / Context: 10Base2 (thin Ethernet) specifies a bus topology using 50-ohm coaxial cable. Using the correct cable type and connectors is essential for reliability. ARCnet used different media options historically, often 93-ohm coax, so mixing standards or using TV coax leads to errors and CRC failures. Given Data / Assumptions: Goal: operate 10Base2 Ethernet, not ARCnet. Proper cable impedance for 10Base2: 50 ohms. Environment: short school network with donated cards and cables. Concept / Approach: 10Base2 requires RG-58 A/U (50-ohm) coax with BNC connectors, T-pieces at each NIC, and 50-ohm terminators at both segment ends. Using 75-ohm TV coax such as RG-59 causes signal reflections and severe errors. RJ-11 and RJ-45 describe modular connectors, not coax cable, and are irrelevant for 10Base2 bus wiring. Step-by-Step Solution: Identify Ethernet variant: 10Base2 thin Ethernet.Match required impedance: 50-ohm coax ⇒ RG-58 A/U.Install with correct topology: T-connector at each NIC, terminators at both ends.Avoid mixing with ARCnet or RG-59 (75-ohm). Verification / Alternative check: Signal integrity checks and collision/error counters improve markedly when 50-ohm RG-58 A/U replaces 75-ohm cable, confirming specification compliance. Why Other Options Are Wrong: RG-59 A/U: 75-ohm TV coax; wrong impedance. RJ-11/RJ-45: Connector types for twisted pair; not coax and not 10Base2 bus medium. None of the above: Incorrect because RG-58 A/U is correct. Common Pitfalls: Using RG-59 from CCTV/TV spares; forgetting both-ends termination; placing T-connectors incorrectly. Final Answer: RG-58 AU

Question 16

What is the standard data rate supported by Category 5 (Cat 5) UTP cabling in Fast Ethernet deployments?

Accepted Answer

Introduction / Context: Structured cabling categories define electrical characteristics that enable certain Ethernet speeds over twisted pair. Category 5 (Cat 5) cabling was widely deployed with 100Base-TX (Fast Ethernet) and remains a baseline for understanding LAN speed support over copper. Given Data / Assumptions: Medium: unshielded twisted pair (UTP) Category 5. Deployment: typical office Fast Ethernet. Maximum segment length per standard: 100 meters for 100Base-TX. Concept / Approach: 100Base-TX uses two twisted pairs within Cat 5 cable, employing MLT-3 signaling and 4B/5B coding to achieve 100 megabits per second over distances up to 100 meters. While Cat 5e/6 support higher rates (e.g., 1 Gbps+), classic Cat 5 is historically associated with 100 Mbps Fast Ethernet as its standard-rated data rate. Step-by-Step Solution: Identify the Ethernet standard tied to Cat 5: 100Base-TX.Recall nominal throughput: 100 megabits per second.Confirm cable length and pairs used adhere to the standard.Select 100 Mbps as the appropriate rating. Verification / Alternative check: Certification testers for Cat 5 verify parameters (NEXT, attenuation) aligned with 100 Mbps service; links lit at 100 Mbps on legacy switches validate the rating. Why Other Options Are Wrong: 10 Mbps: That is 10Base-T’s rate, typically supported even by lower categories. 4 Mbps / 2 Mbps: Legacy token ring or proprietary rates, not Cat 5’s Fast Ethernet rating. None of the above: Incorrect because 100 Mbps is correct. Common Pitfalls: Confusing Cat 5 with Cat 5e (often used for 1 Gbps). The question asks the standard rating historically tied to Cat 5. Final Answer: 100 Mbps

Question 17

You must interconnect two separate 10Base-T Ethernet networks located in different buildings about 1,000 meters apart. Which physical media is most appropriate for a reliable link at this distance?

Accepted Answer

Introduction / Context: 10Base-T specifies twisted-pair copper with a maximum segment length of 100 meters. Building-to-building links at 1 km require a medium with far lower attenuation and immunity to electrical interference and lightning potential differences. Fiber-optic links are the industry standard for campus interconnects of this distance. Given Data / Assumptions: Distance ≈ 1,000 meters between buildings. Need to link two 10Base-T Ethernet networks reliably. Outdoor/OSP considerations (grounding, surge) favor non-conductive media. Concept / Approach: Twisted pair and 10Base-T copper are limited to 100 m without active devices. Coaxial 10Base2/10Base5 is obsolete and also distance-limited and electrically conductive. Fiber provides high bandwidth, low loss over kilometers, and galvanic isolation between buildings, reducing surge and ground loop risks. IR wireless is highly line-of-sight sensitive and weather-dependent, unsuitable for dependable backbone links. Step-by-Step Solution: Eliminate copper options that exceed standard distance limits.Prefer galvanic isolation and low attenuation for interbuilding links.Select fiber-optic cable with appropriate transceivers (e.g., 10Base-FL/FX media converters).Install with proper termination and protection for outdoor runs. Verification / Alternative check: Campus networks universally use multimode or single-mode fiber for 300 m–10 km spans; successful deployments confirm fiber as the best practice for ~1 km. Why Other Options Are Wrong: Type 1 STP: Token Ring cabling; copper distance limits and interbuilding grounding issues. RG-58 A/U: 10Base2 thin Ethernet; distance and reliability constraints. Wireless infrared: Weather/line-of-sight constraints; not robust for 1 km enterprise backbones. None: Incorrect because fiber is the correct medium. Common Pitfalls: Trying to daisy-chain copper switches across buildings; ignoring electrical code and surge risks of metallic cabling between facilities. Final Answer: Fiber-optic cable

Question 18

In the OSI reference model, Microsoft NetBEUI (NetBIOS Extended User Interface) primarily provides services at which layers, conceptually aligning with how the protocol manages conversations between endpoints?

Accepted Answer

Introduction / Context: In classic Microsoft networking, NetBEUI (NetBIOS Extended User Interface) underpins NetBIOS sessions and datagrams. Understanding where NetBEUI fits in the OSI model clarifies why it is non-routable and how it supports application conversations. This question tests the mapping between protocol functions and OSI layers, especially the roles of the transport and session layers in managing reliable exchanges and dialogs. Given Data / Assumptions: NetBEUI supports NetBIOS name service, datagrams, and sessions inside small LANs. OSI mapping is conceptual (Microsoft stacks do not implement OSI literally). Routing across IP subnets is not provided by NetBEUI. Concept / Approach: Transport-layer duties include segmenting, sequencing, and error recovery; session-layer duties include establishing, maintaining, and terminating conversations (sessions). NetBEUI provides reliable transport for NetBIOS over small Ethernet/Token Ring LANs and manages session-type exchanges, so its functions are best described as spanning the transport and session layers conceptually. It does not provide network-layer routing and is not limited to MAC/LLC-only forwarding. Step-by-Step Solution: Identify what NetBEUI does: supports NetBIOS name resolution, datagrams, and sessions.Map these to OSI: reliable data movement (transport) and dialog control (session).Eliminate network-layer choices because NetBEUI is non-routable.Select 'transport and session' as the best conceptual fit. Verification / Alternative check: Legacy Windows networking texts describe NetBEUI as a small, fast, non-routable transport for NetBIOS that handles sessions (for example, file/print sharing) inside a LAN—aligning with transport/session responsibilities. Why Other Options Are Wrong: Network and transport: NetBEUI does not implement routing across subnets. Physical and data link / MAC and LLC: too low-level; NetBEUI sits above these to manage sessions. None of the above: incorrect because transport and session is a correct mapping. Common Pitfalls: Confusing NetBEUI with NetBIOS over TCP/IP (NBT). NBT rides on IP and is routable; NetBEUI alone is not. Final Answer: transport and session

Question 19

On Microsoft Windows 95, what should Peter install to administer Windows NT domain user accounts remotely from his Windows 95 workstation?

Accepted Answer

Introduction / Context: In mixed Windows 95/Windows NT environments, administrators often need to manage domain users and groups from client machines. Microsoft provided remote administrative utilities for Windows 95 so that domain tasks could be performed without installing Windows NT on the admin PC. Given Data / Assumptions: Peter uses Windows 95 (not NT). He wants to administer user accounts in a Windows NT domain. We assume standard Microsoft tooling of the era is available. Concept / Approach: Windows 95 cannot natively run the full NT administrative consoles, but Microsoft released the Client-based Network Administration Tools (also known as the Windows 95 Admin Tools). These include remote-capable versions or stubs that communicate with domain controllers, enabling tasks such as user and group administration without upgrading the client OS to NT. Step-by-Step Solution: Recognize the platform limitation: Windows 95 is not Windows NT.Identify the supported method: install the Client-based Network Administration Tools.Use the tools to connect to the NT domain and administer accounts.Avoid unnecessary OS upgrades; tools suffice for the task. Verification / Alternative check: Historic Microsoft deployment guides list the Windows 95 Admin Tools package allowing remote management of NT domains, including user/group administration. Why Other Options Are Wrong: User Manager for Domains alone is not natively installable on Windows 95 without the admin tools set. Installing NT Server/NT Workstation changes the OS—overkill when admin tools solve the problem. None of the above is incorrect because the client-based tools are the intended solution. Common Pitfalls: Assuming you must upgrade to NT just to manage accounts; the admin tools were designed for precisely this use case. Final Answer: install the Client-based Network Administration Tools on his computer

Question 20

On a Windows NT Server that is a Backup Domain Controller (BDC), Maria receives 'Unable to log on locally' when attempting to sign in to install software. What should be configured to allow her to log on at the console?

Accepted Answer

Introduction / Context: Windows NT uses user-rights assignments to control who can sign in at the console ('Log on locally'). On domain controllers (including BDCs), this right is usually restricted to Administrators and certain operator groups. If a user lacks that right, NT will explicitly deny the local logon attempt. Given Data / Assumptions: The computer is a Backup Domain Controller (BDC), not a standalone server. Maria needs to log on at the console to install software. The error indicates a rights problem, not a password or account lockout issue. Concept / Approach: Granting the 'Log on locally' right is done via User Manager for Domains → Policies → User Rights. Best practice is to add the user to (or create) a group that already has that right (for example, Administrators or Server Operators) rather than granting rights directly to individual users, which eases administration and auditing. Step-by-Step Solution: Open User Manager for Domains on a domain controller.Navigate to Policies → User Rights → 'Log on locally'.Add a suitable group (or add Maria to such a group) so that she inherits the right.Have Maria log on again; the console sign-in should succeed. Verification / Alternative check: Run 'whoami /priv' or check effective group membership and rights to confirm the 'Log on locally' right is present. Why Other Options Are Wrong: Defining a 'local account' on a domain controller is not applicable; DCs use domain accounts only. Control Panel toggles or environment variables do not grant security rights. None of the above is incorrect because the rights assignment is the correct remedy. Common Pitfalls: Granting broad rights directly to users instead of roles; always prefer group-based assignments. Final Answer: In User Manager for Domains, assign Maria to a group that has the right to log on locally

Windows NT Questions