Question 1

Routing basics in computer networks: evaluate the statement below and choose the most appropriate assessment.  Statement: “A route is a path between two network segments.”

Accepted Answer

Introduction / Context: Networking fundamentals hinge on precise terminology. The term “route” is widely used in IP networking, enterprise LANs, and the Internet to mean a selected path that packets take from one network or subnet to another. This question checks whether you can recognize the accepted definition of a route without confusing it with unrelated concepts like switching paths inside the same segment or media-specific constraints. Given Data / Assumptions: The statement defines a route as a path between two network segments (for example, two IP subnets). Routers forward packets between segments, often guided by a routing table. No specific routing protocol (e.g., OSPF, BGP, RIP) is required to validate the definition. Concept / Approach: In IP, a “network segment” typically maps to a Layer 3 subnet or VLAN interface. A “route” identifies the next hop (or interface) that advances a packet toward a destination segment. Routes may be directly connected, statically configured, or learned dynamically. The core essence remains: a route represents a path used for inter-network forwarding, not intra-segment switching. Step-by-Step Solution: Recognize that routes operate at Layer 3 (IP layer) and interconnect segments/subnets.Understand that a route expresses a path (often via one or more routers) toward a destination network.Conclude the statement corresponds with standard definitions used in textbooks and router CLIs. Verification / Alternative check: Router command outputs (e.g., “show ip route”) list destination networks and next hops, explicitly indicating paths between segments, corroborating the definition. Why Other Options Are Wrong: Invalid statement: contradicts widely accepted Layer 3 terminology.Ambiguous without a protocol: definitions do not depend on a specific protocol.Valid only for wireless / only for IPv6: routing concepts apply across media and versions (IPv4 and IPv6). Common Pitfalls: Confusing a “route” with a Layer 2 switch path or with physical cabling; a route is logical and protocol-driven. Final Answer: Valid statement.

Question 2

Repeaters and traffic propagation: evaluate the statement below and choose the most appropriate assessment.  Statement: “A drawback of repeaters is that traffic generated on one segment is propagated onto the other segments.”

Accepted Answer

Introduction / Context: Repeaters and hubs operate at the physical layer. They regenerate and forward every symbol they receive, regardless of the frame’s ultimate destination. Understanding this limitation is important when designing collision domains and troubleshooting broadcast storms or excessive background traffic on shared media. Given Data / Assumptions: “Repeater” refers to devices that extend a segment by regenerating signals (e.g., classic Ethernet repeaters or hubs). They do not inspect MAC addresses or apply filtering logic. Segments interconnected by a repeater become one shared collision/broadcast domain. Concept / Approach: Because a repeater lacks Layer 2 intelligence, it blindly forwards bits to all attached segments. Any unicast, broadcast, or collision activity on one side repeats across the other side(s). This behavior contrasts with bridges and switches, which forward selectively based on MAC learning, and with routers, which segment broadcast domains at Layer 3. Step-by-Step Solution: Identify device role: a repeater regenerates signals without filtering.Infer that all frames/energy on one side are propagated to other sides.Conclude that the stated drawback accurately describes repeater behavior. Verification / Alternative check: Network design guidelines recommend replacing repeaters/hubs with switches to contain traffic and mitigate collision/broadcast issues, confirming the practical consequence stated. Why Other Options Are Wrong: Invalid statement: contradicts physical-layer forwarding behavior.Media or duplex qualifiers: propagation is inherent and not restricted to fiber or full-duplex.Token Ring only: repeaters behave similarly across media; the statement is not ring-specific. Common Pitfalls: Assuming repeaters filter like switches; they do not. Confusing “media converters” (also L1) with bridges (L2). Final Answer: Valid statement.

Question 3

Windows NT administration: what is User Manager for Domains primarily used for in a Windows NT domain environment?

Accepted Answer

Introduction / Context: Windows NT distinguished between tools for account/group management and tools for machine membership and file permissions. “User Manager for Domains” was the central console for managing domain user and group accounts and their related properties such as logon scripts and profile paths. Identifying the correct administrative function avoids confusion with Server Manager and file system tools. Given Data / Assumptions: Environment: classic Windows NT domains (PDC/BDC model). We focus on the role of “User Manager for Domains.” Other administrative tasks exist but are handled by different tools. Concept / Approach: User Manager for Domains manages domain accounts and their attributes. It does not join computers to a domain (that is done on the workstation/server itself or via Server Manager) and does not change NTFS ACLs (done in File Manager/Explorer or via command-line ACL tools). System policies are edited with “System Policy Editor,” not created by User Manager, although User Manager can store profile and script paths in account properties. Step-by-Step Solution: Identify which task aligns with account property management.Logon scripts are assigned per user/group in account properties.Therefore, User Manager for Domains is used to assign logon scripts. Verification / Alternative check: In the user’s properties dialog, the “Logon script” and “Profile path” fields confirm this functionality. Why Other Options Are Wrong: Adding a workstation: performed during OS networking setup or via Server Manager, not User Manager.Creating profiles/system policies: System Policy Editor and file server storage handle that; User Manager only points to them.Changing NTFS permissions: done in file system ACL tools, not User Manager.None of the above: incorrect because assigning logon scripts is correct. Common Pitfalls: Assuming one MMC/console does everything; NT split responsibilities among multiple tools. Final Answer: Assigning a logon script to a user or a group of users.

Question 4

Structured cabling (UTP Cat 5): within a 100 m channel, what is the typical maximum length recommended for a work-area patch cable from the wall outlet to the PC?

Accepted Answer

Introduction / Context: TIA/EIA-568 structured cabling guidelines define a 100 m maximum channel length for copper twisted-pair Ethernet (typically 90 m permanent link plus up to 10 m of patch cords). Within that budget, a common design practice is to allocate a short work-area patch from the outlet to the device, ensuring margin for the telecom room patch cords as well. Given Data / Assumptions: Category: UTP Cat 5 (applies similarly to Cat 5e/6 concepts). Total Ethernet channel length target: 100 m. Permanent link: approximately 90 m from patch panel to outlet. Work-area patch cable: short length to the PC at the desk. Concept / Approach: A widely used rule-of-thumb assigns roughly 5 m total for patching (for example, 2 m in the telecom room and up to 3 m in the work area). Keeping the work-area patch around 3 m maintains compliance and preserves flexibility for moves/adds/changes without exceeding the 100 m channel maximum. Step-by-Step Solution: Start with the 100 m channel budget.Reserve ~90 m for the permanent link.Allocate remaining ~10 m to patch cords: commonly ~2 m TR + ~3 m work area, leaving additional slack for jumpers.Therefore, 3 meters is the typical recommended maximum for the wall-to-PC patch. Verification / Alternative check: Many enterprise cabling standards and vendor design guides present examples with 90 m permanent links and 3 m end-user cords to maintain channel performance. Why Other Options Are Wrong: 1 meter: feasible but overly restrictive; 3 m is the common recommendation.6 or 9 meters: risk exceeding the 100 m channel when combined with other patching.None of the above: incorrect because 3 meters is the accepted practice. Common Pitfalls: Confusing permanent link limits with patch cord allowances, or forgetting both ends’ patching must fit within the 10 m budget. Final Answer: 3 meters.

Question 5

Windows NT domain administration scenario: you created a new domain local group “R-Editors” in the RESEARCH domain. The LAB domain trusts the RESEARCH domain. From where can you assign access permissions to resources using the R-Editors group with l…

Accepted Answer

Introduction / Context: Windows NT distinguished global, local, and domain local groups, each with particular scopes. Domain local groups (created in a domain) are intended to be used to assign permissions on resources in that same domain’s computers. Correctly choosing where to perform the ACL assignment helps avoid scope and trust confusion. Given Data / Assumptions: R-Editors is a domain local group in the RESEARCH domain. LAB trusts RESEARCH (LAB users can be granted access to RESEARCH resources if desired). We want to assign permissions to resources using R-Editors. Concept / Approach: Domain local groups can be used to assign permissions only within their own domain. Therefore, you typically perform ACL changes on a machine that is a member of the RESEARCH domain (for example, a Windows NT Workstation or Server in RESEARCH). Trust direction (LAB trusts RESEARCH) does not move the scope of the domain local group; it only affects which accounts can be added or authenticated for access. Step-by-Step Solution: Identify R-Editors as domain local (scope limited to RESEARCH resources).Choose a workstation/server joined to RESEARCH to set ACLs.Assign permissions using R-Editors on resources residing in RESEARCH. Verification / Alternative check: NT domain best practices: “Global groups for users, Domain Local groups for permissions, and place Global into Local” (AGDLP) pattern confirms the usage within the same domain. Why Other Options Are Wrong: LAB domain machines: cannot apply a RESEARCH domain local group to LAB resources.BDC in LAB: same scope problem as above.BDC in RESEARCH: possible if managing server ACLs, but the question asks broadly; any RESEARCH workstation is sufficient.None of the above: incorrect because RESEARCH workstations are correct. Common Pitfalls: Confusing group scope (global vs local) and trust direction; assuming trusts let you use domain local groups across domains for permissions—they do not. Final Answer: Any Windows NT Workstation in the RESEARCH domain.

Question 6

Windows NT trusts: which statement best describes a trust relationship in classic Windows NT domain architecture?

Accepted Answer

Introduction / Context: Classic Windows NT domains (pre–Active Directory) used trusts to allow users in one domain to be authenticated for resources in another domain. Understanding the directionality and creation of trusts is crucial for exam scenarios and for troubleshooting cross-domain access issues. Given Data / Assumptions: Trusts exist between domains, not between individual workstations. Trusts in Windows NT are non-transitive and one-way unless two complementary trusts are created. Administrative rights are not automatically conferred by a trust; access still depends on group membership/ACLs. Concept / Approach: In Windows NT, an administrator would use Server Manager for Domains to establish a trust. A single trust is one-way (A trusts B or B trusts A). To enable mutual trust, separate trusts must be created in both directions. Trusts facilitate authentication but do not themselves grant privileges; permissions are still assigned explicitly via groups and ACLs. Step-by-Step Solution: Identify creation tool: Server Manager for Domains.Recall trust characteristics: one-way, non-transitive.Dispel myths: trusts do not auto-assign administrative privileges. Verification / Alternative check: Microsoft documentation for Windows NT domains describes “one-way, nontransitive trusts,” and shows configuration steps using Server Manager for Domains, confirming the chosen statement. Why Other Options Are Wrong: Bi-directional by default: false; requires two trusts.Between workstations: false; trusts are domain-to-domain.Automatic admin rights: false; access remains controlled by ACLs and group membership.None of the above: incorrect because option A is accurate. Common Pitfalls: Assuming trusts equal permissions; mixing up NT’s one-way trusts with modern AD forest trusts which may be transitive. Final Answer: It is created using Server Manager for Domains and is a one-way relationship unless explicitly configured both ways.

Question 7

Cabling history: in which LAN cabling system are BNC T-connectors and 50-ohm terminators required on the bus?

Accepted Answer

Introduction / Context: Early Ethernet implementations used a coaxial bus topology before the widespread adoption of twisted-pair star wiring. Recognizing which variant required BNC T-connectors and end-of-line terminators is a common historical networking question and helps diagnose legacy installations still in service. Given Data / Assumptions: We compare LAN cabling types: 10Base2, Token Ring, 10Base-T, FDDI. Focus is on the presence of T-connectors and terminators. Coaxial bus topologies require proper termination to avoid reflections. Concept / Approach: 10Base2 (Thin Ethernet) uses RG-58 coaxial cable with BNC T-connectors to attach NICs to the bus and 50-ohm terminators at both ends to prevent signal reflections. Token Ring typically uses MAUs with shielded twisted pair; 10Base-T uses star topology with UTP and has no coax terminators; FDDI employs fiber dual-rings, again without BNC T-connectors or 50-ohm terminators. Step-by-Step Solution: Identify the only coax bus among the options: 10Base2.Recall BNC T-connectors attach NICs inline on the bus.Confirm need for 50-ohm terminators at both physical ends. Verification / Alternative check: Vendor guides and certification materials depict 10Base2 with T-connectors and terminators, reinforcing the selection. Why Other Options Are Wrong: FDDI: fiber dual-ring; no BNC T-connectors.Token Ring: uses MAUs; not a coax bus with BNC T’s.10Base-T: UTP star; no coax terminators.None of the above: incorrect, because 10Base2 fits exactly. Common Pitfalls: Confusing 10Base5 (thick coax/vampire taps) with 10Base2; both used coax and termination, but T-connectors specifically identify 10Base2. Final Answer: Thin Ethernet (10Base2).

Question 8

Interconnecting dissimilar LANs: in a building with both Ethernet and Token Ring networks, which device enables communication between the different LAN architectures and protocols?

Accepted Answer

Introduction / Context: Mixed environments may include LANs with different media access methods and frame formats (e.g., Ethernet vs. Token Ring). To share resources across these systems, you may need a device that can translate or interoperate across different protocols/architectures—not merely forward frames unchanged. Given Data / Assumptions: Ethernet and Token Ring differ at Layer 2 (frame formats, media access). Some scenarios require protocol translation, name service mediation, or application-layer adaptation. Goal: enable communications between dissimilar LANs, not just extend the same LAN type. Concept / Approach: A gateway performs protocol conversion and higher-layer mediation so endpoints on different LAN architectures can interoperate. In contrast, a bridge forwards frames within the same Layer 2 protocol family; a router forwards at Layer 3 but does not translate between incompatible Layer 2 protocols by itself; a repeater operates at Layer 1 and cannot resolve protocol differences. Therefore, the correct choice for “dissimilar LANs using different protocols” is a gateway. Step-by-Step Solution: Identify that the LANs are dissimilar at Layer 2.Eliminate L1/L2 devices that only forward signals/frames.Select “Gateway” for protocol/architecture translation. Verification / Alternative check: Historical solutions included multi-protocol gateways and application gateways to integrate Ethernet and Token Ring segments for file/print services. Why Other Options Are Wrong: Bridge: same-protocol Layer 2 forwarding; not cross-architecture translation.Router: IP-layer forwarding only; does not address L2 incompatibilities by itself.Repeater: signal regeneration only.None of the above: incorrect because “Gateway” fits. Common Pitfalls: Assuming routers solve all interconnection problems; routers do not convert frame formats or application protocols. Final Answer: Gateway.

Question 9

Windows NT domain administration: from a Windows NT Workstation with local accounts in the SYCON domain, you want administrative rights on all Windows NT Advanced Servers in that domain with minimal effort. What is the best approach?

Accepted Answer

Introduction / Context: Centralized administration is a core advantage of Windows NT domains. Rather than touching every server, you can use domain groups to grant rights across the domain. Understanding the scope of the “Domain Admins” global group saves time and ensures consistent privilege assignment. Given Data / Assumptions: You are in the SYCON domain. You seek admin rights on all Windows NT Advanced Servers (domain members). Minimal administrative overhead is desired. Concept / Approach: Adding a domain user account to the Domain Admins group grants administrative privileges on all domain member servers/workstations by default policy, avoiding per-machine changes. Adding a local workstation account (non-domain) to Domain Admins is invalid; adding your account to each server’s local Administrators group works but is labor-intensive and error-prone. Step-by-Step Solution: Open User Manager for Domains on any Windows NT Advanced Server.Open the Domain Admins group and add your domain user account.Log off/on to refresh tokens; verify admin access across servers. Verification / Alternative check: Microsoft guidance on group scopes and default privileges confirms that Domain Admins confer administrative rights on domain members. Why Other Options Are Wrong: Local workstation account in Domain Admins: not a domain security principal; not valid.Per-machine additions: possible but not minimal administration.Per-server Administrators group: same problem—too manual.None of the above: incorrect because adding to Domain Admins is correct. Common Pitfalls: Confusing local vs. domain accounts; forgetting to re-authenticate to receive new group tokens. Final Answer: Add your user account to the Domain Admins group on any Windows NT Advanced Server in the SYCON domain.

Question 10

Locking down application access in Windows NT: the administrator wants users to run only approved programs. Which action best achieves this using mandatory user profiles and shell restrictions?

Accepted Answer

Introduction / Context: In classic Windows NT environments, administrators often used mandatory profiles and shell restrictions (Program Manager/Explorer policies) to limit what users could execute. The goal is to provide only approved applications and block ad-hoc execution mechanisms like the Run dialog or file browsing tools that expose arbitrary executables. Given Data / Assumptions: Mandatory profiles enforce read-only, centrally defined settings at logon. Disabling the Run command removes a common path to launch unauthorized executables. Removing File Manager (or restricting Explorer) limits file-system browsing for .EXE files. We want a maintainable approach without heavy per-file ACL micromanagement. Concept / Approach: A mandatory profile combined with shell restrictions targets the user interface entry points to unwanted software. This approach is scalable and minimizes administrative overhead. While NTFS permissions are important, a blanket “Deny All” is risky and brittle. Deleting system executables is unsupported and may break administrative workflows or updates. Step-by-Step Solution: Create a tested mandatory profile on a share and rename the .USR to .MAN.Use System Policy Editor to disable the Run command and restrict control panels and shell menus as needed.Remove File Manager from visible groups or restrict Explorer; publish only approved program groups.Assign the profile path to users in User Manager for Domains and test. Verification / Alternative check: After applying, users should only see sanctioned program groups and no Run dialog; attempts to browse to executables should be blocked by UI restrictions and NTFS where appropriate. Why Other Options Are Wrong: Lock all program groups: too coarse; may block necessary tools and lacks targeted control.Deny All on files: creates maintenance burdens and potential lockouts.Delete WINFILE.EXE: unsupported and risky; security by deletion is fragile.None of the above: incorrect because the mandatory profile plus Run restriction is effective. Common Pitfalls: Relying solely on UI restrictions without NTFS; forgetting to store the profile on a resilient share; not testing with a non-admin user. Final Answer: Create a mandatory user profile that disables the Run command; assign it to all users and remove File Manager from the Main group.

Question 11

In computer networking, classic Layer-2 bridges (and modern switches acting as multiport bridges) perform frame forwarding and filtering. Do such bridging devices inherently introduce a small processing delay into the network path compared with an u…

Accepted Answer

Introduction / Context: Understanding how bridges and switches affect latency is a foundational networking topic. A bridge examines incoming frames, consults its MAC address table, and decides whether to forward, filter, or flood. This processing, along with store-and-forward buffering or cut-through behaviors, adds a small but measurable delay compared with a simple shared medium. Recognizing this helps with performance tuning and realistic expectations when adding devices to a path. Given Data / Assumptions: The device is a Layer-2 bridge or an Ethernet switch (a multiport bridge). The device performs MAC learning and forwarding decisions. Frames may be buffered for store-and-forward operation, error checking, or congestion management. Concept / Approach: A bridge must at minimum read enough of the frame header to determine the output port. In store-and-forward mode, it receives the entire frame and checks FCS before forwarding, inherently adding latency proportional to frame length and line rate. Even cut-through switching, which forwards after reading the destination MAC, incurs serialization and lookup delay. Therefore, bridging adds a small processing delay compared with a passive medium, though the delay is typically sub-millisecond on modern hardware. Step-by-Step Solution: Identify operations: header inspection + forwarding decision → non-zero processing time. Account for buffering: store-and-forward introduces full-frame latency; cut-through still has partial-frame delay. Include queueing: under load, output-port contention adds additional queueing delay. Conclude: bridges introduce small delays relative to a shared passive medium → the statement is correct. Verification / Alternative check: Empirical tests with back-to-back latency measurements show a few microseconds to tens of microseconds of added delay per switch hop, depending on architecture, speed (Fast/Gigabit/10G), and features (QoS, ACLs). Passive components (cables, unmanaged splitters on older media) do not make forwarding decisions and thus do not add comparable processing delay. Why Other Options Are Wrong: Incorrect: contradicts the inevitable processing/serialization delay in bridges. Only on wireless links: bridging delay is independent of wireless; it occurs on wired links too. Only with VLANs: VLAN tagging adds minimal overhead; bridging delay exists even without VLANs. Only on half-duplex: duplex mode does not eliminate lookup/buffer delays. Common Pitfalls: Assuming “negligible” means “zero”; ignoring queueing delay under congestion; confusing propagation delay (speed of signal in cable) with processing delay (device time to make decisions). Final Answer: Correct

Question 12

Your 10BASE2 (thin coax) Ethernet segment is already at 185 m (the maximum standard segment length). You plan to add another 100 m of the same cable, bringing the total to 285 m. The network protocol in use is NetBEUI (irrelevant to the physical lay…

Accepted Answer

Introduction / Context: 10BASE2 (thin Ethernet, RG-58 coax) has a strict maximum segment length of 185 m between terminators. Exceeding this without regeneration leads to attenuation and collision-domain issues. When you need more distance on the same physical medium and wish to remain within the same collision domain, a physical-layer device is the correct tool. Given Data / Assumptions: Existing 10BASE2 segment length: 185 m (already at the limit). Desired additional length: 100 m → total 285 m. No desire to change collision domains or perform Layer-2/Layer-3 segmentation. Upper-layer protocol (NetBEUI) does not affect the physical constraint. Concept / Approach: A repeater (or an active hub for the appropriate medium) regenerates and reshapes the signal, effectively starting a new compliant segment while preserving one collision domain. T-connectors are only passive taps in 10BASE2 chains. Routers and gateways segment at higher layers and are unnecessary if you only need to extend the same segment physically. A bridge would create a new collision domain and requires appropriate media interfaces; the simplest, standards-aligned solution for same-medium extension is a repeater placed between segments, observing Ethernet’s repeater and segment-count rules. Step-by-Step Solution: Recognize the 185 m limit for a single 10BASE2 segment. To add distance on the same medium, use a Layer-1 device that regenerates bits → repeater. Ensure proper terminators and T-connectors at segment ends and host taps. Conclude: Add a repeater between the two coax segments. Verification / Alternative check: 10BASE2 design guidelines allow multiple segments interconnected by repeaters, within the classic Ethernet repeater rules. This maintains timing for CSMA/CD and keeps collisions detectable across the extended shared medium. Why Other Options Are Wrong: T-connector: passive; cannot extend beyond the 185 m limit. Router/Gateway: unnecessary segmentation and protocol handling for a simple physical-layer extension. Bridge: introduces a new collision domain; not required if the goal is one continuous 10BASE2 domain. Common Pitfalls: Confusing passive tap hardware with active signal regeneration; forgetting terminators (50-ohm) at both ends of each coax segment; overlooking repeater count and topology rules in classic Ethernet. Final Answer: Repeater

Question 13

In structured cabling and campus backbones, fibre-optic cable is often chosen to address which primary requirement when copper Ethernet reaches its physical limits?

Accepted Answer

Introduction / Context: Choosing between copper and fibre is a design decision driven by distance, bandwidth, and environmental factors. Unshielded twisted pair (UTP) Ethernet links are typically limited to about 100 m per channel. When links need to span floors, buildings, or noisy conduits shared with power or telephone cabling, fibre-optic media become the preferred choice due to low attenuation and immunity to electromagnetic interference (EMI). Given Data / Assumptions: Standard copper Ethernet (e.g., 1000BASE-T) is constrained to ~100 m per run. Backbone and inter-building links often exceed 100 m and traverse EMI-prone environments. Designers want reliable, high-bandwidth connectivity without repeaters every 100 m. Concept / Approach: Fibre offers orders-of-magnitude longer runs (hundreds of meters to tens of kilometers, depending on multimode or single-mode) and excellent EMI immunity because it carries light rather than electrical signals. This makes it ideal for building risers, campus backbones, and long horizontal runs that copper cannot support economically or reliably. While fibre prices have fallen, claiming it is “always cheaper” than UTP is inaccurate once optics and transceivers are included. Desktop drops within one room remain economical with copper, and dial-up analog WAN traffic is unrelated to fibre backbones. Step-by-Step Solution: Identify the limiting factor for copper: 100 m distance and EMI susceptibility. Match the requirement to fibre benefits: long reach + EMI immunity. Eliminate options that are cost myths or irrelevant use cases. Select “Overcome distance limitations and electromagnetic interference.” Verification / Alternative check: Standards such as 1000BASE-SX/LX and 10GBASE-SR/LR specify distances far beyond copper limits. Real-world deployments place fibre in risers and between buildings specifically to address distance and EMI, confirming the rationale. Why Other Options Are Wrong: Cheaper in all cases: false; optics and transceivers add cost. Desktop wall outlets: copper is typically sufficient and economical for short runs. Dial-up analog lines: unrelated to fibre-based Ethernet backbones. Provide power over fibre: standard fibre does not deliver electrical power (PoE is for copper). Common Pitfalls: Assuming fibre is always more expensive or always cheaper; overlooking EMI in shared conduits; forgetting transceiver compatibility (SFP/SFP+ types, connector and modal considerations). Final Answer: Overcome distance limitations and electromagnetic interference

Question 14

In classic Microsoft Windows NT environments, what does the Directory Replicator service primarily allow administrators to do across machines?

Accepted Answer

Introduction / Context: Before the advent of modern DFS Replication and Active Directory, Windows NT included a Directory Replicator service to distribute files—commonly logon scripts or shared tools—from a designated export server to import computers on the network. Understanding its scope prevents confusion with account database replication and full partition mirroring. Given Data / Assumptions: The service predates Active Directory and DFSR. It synchronizes directories/files from a server to other machines. It is not the mechanism for account database replication (that is PDC ↔ BDC replication). Concept / Approach: The Directory Replicator service is a file replication facility. Administrators configure an export path on a Windows NT Server; designated import computers (often workstations or member servers, potentially in workgroups) receive updated files. This mechanism was commonly used to distribute logon scripts and common utilities. It does not replicate the Security Accounts Manager (SAM) database, does not mirror entire partitions, and is unrelated to Active Directory (which did not exist in NT 4.0). Step-by-Step Solution: Identify the entity replicated: directories/files, not accounts. Identify direction: from server export share to import machines. Note independence from domain membership in many setups. Select the option that matches this purpose. Verification / Alternative check: Microsoft documentation from the Windows NT era describes the Directory Replicator’s export/import model, with scheduled replication of specified directories to remote systems—especially for distributing logon script files across sites. Why Other Options Are Wrong: PDC to BDC account replication is handled by SAM replication, not the Directory Replicator. Partition mirroring is a storage/backup function, not provided by this service. Workstation→server copy is not the core design of the Directory Replicator. Active Directory replication pertains to Windows 2000 and later, not NT 4.0. Common Pitfalls: Confusing different “replication” terms; assuming it handles security principals; forgetting that domain controllers and file replication were separate subsystems in NT. Final Answer: Copy directories and files from a Windows NT Server to Windows NT Workstation computers that may not be domain members

Question 15

You must cable an Ethernet network in an older building with limited workspace. The new cable must share conduit with existing telephone wiring, and some runs will be up to 135 m. Which medium is best suited to meet distance and interference constra…

Accepted Answer

Introduction / Context: Ethernet media choices depend on distance, bandwidth, and electromagnetic environment. Standard copper Ethernet channels are limited to ~100 m and are susceptible to EMI, particularly when sharing conduits with telephone or power cables. Fibre-optic cabling addresses both constraints by providing longer reach and immunity to electrical interference. Given Data / Assumptions: Shared conduit with telephone cabling → increased EMI risk. Required run length up to 135 m → beyond common copper Ethernet limit. Desire for reliable performance without intermediate active devices. Concept / Approach: Fibre uses light instead of electrical signals, so it is immune to EMI and crosstalk from adjacent conductors. Multimode fibre with appropriate transceivers supports 1 Gbps and higher over hundreds of meters, easily covering 135 m. CAT1 is for voice only and unsuitable for Ethernet. CAT3 is limited and still constrained to ~100 m for older Ethernet variants. 10BASE5 thick coax is bulky, obsolete, and impractical for shared conduit in modern installs. Step-by-Step Solution: Extract constraints: EMI + 135 m distance. Map constraints to media: fibre solves both; copper does not without repeaters. Eliminate voice-grade and obsolete media (CAT1, thick coax). Choose fibre-optic cable as the best fit. Verification / Alternative check: Standards such as 1000BASE-SX/LX recommend fibre for building risers and campus links; many codes also prefer fibre in shared conduits due to its immunity and safety profile compared with high-frequency copper signaling near telecom circuits. Why Other Options Are Wrong: CAT1: voice only; unsuitable for Ethernet. CAT3: legacy 10 Mbps support and still limited to ~100 m; EMI remains a concern. 10BASE5: obsolete, bulky, and not aligned with modern structured cabling. Flat silver satin: unshielded voice cord; not standards-compliant for Ethernet. Common Pitfalls: Attempting to exceed 100 m copper limits without active devices; underestimating EMI in shared conduits; ignoring transceiver selection and connector types (LC/SC) when planning fibre runs. Final Answer: Fibre-optic cable

Question 16

You want to prevent anyone from logging on with the default built-in “Administrator” account on a Windows NT Server, without breaking system functions that expect an administrative identity. What is the recommended mitigation?

Accepted Answer

Introduction / Context: The well-known “Administrator” account is a common target for brute-force attacks. On legacy Windows NT systems, best practice was to reduce exposure without breaking built-in expectations for an administrative identity. One classic mitigation is to rename the account, optionally creating a disabled decoy named “Administrator.” Given Data / Assumptions: You must keep administrative capabilities intact for system operations. Windows NT permits renaming the built-in Administrator account. Account lockout policies typically do not apply to the built-in Administrator in NT. Concept / Approach: Renaming obscures the default username targeted by automated attacks. Deleting the account is unsupported and dangerous. Disabling the built-in Administrator can break recovery paths and services that rely on it. Lockout policy does not protect this account reliably in NT. Therefore, the pragmatic and supported step is to rename it and manage strong passwords; optionally create a disabled honeypot account named “Administrator” to detect attempts. Step-by-Step Solution: Open User Manager for Domains (or local User Manager). Locate the built-in Administrator account. Rename it to a non-obvious identifier and set a strong password. Optionally create a disabled decoy account named “Administrator.” Verification / Alternative check: Security baselines for legacy Windows environments consistently recommended renaming the Administrator account, alongside enforcing complex passwords and auditing logon attempts, confirming this as a sound mitigation for NT-era systems. Why Other Options Are Wrong: Delete: unsupported and risks system instability. Lock out: built-in Administrator typically bypasses lockout in NT. Disable: removes a critical recovery path and may break services. Remove from Administrators: cannot; the account defines the role. Common Pitfalls: Relying solely on renaming without strong passwords; forgetting to audit and restrict network logon rights; exposing the account via SMB/Remote Registry unnecessarily. Final Answer: Rename the Administrator account to a non-obvious name and use a decoy

Question 17

In Windows NT domain administration, which action is Server Manager specifically used for among the following choices?

Accepted Answer

Introduction / Context: Windows NT networks predate Active Directory and used Primary/Backup Domain Controllers (PDC/BDCs) with SAM database replication. Server Manager was the central MMC-style tool of its era for managing servers, shares, services, and certain domain operations. Knowing what Server Manager could and could not do is a common certification topic. Given Data / Assumptions: Environment: Windows NT 4.0-era domains. Server Manager provided management of domain controllers and could trigger replication. Some tasks listed belong to other tools or later technologies. Concept / Approach: Server Manager could force synchronization of the SAM database between the PDC and BDCs. It did not directly control OS shutdown/restart (that was done locally or via different utilities), and it did not “demote” a PDC in the AD sense—rather, you could promote a BDC to PDC, which implicitly made the old PDC a BDC. Auditing configuration was handled in User Manager for Domains and Local Security Policy. Active Directory forests did not exist in NT 4.0. Step-by-Step Solution: List candidate actions and map each to the correct NT-era tool. Identify the action uniquely associated with Server Manager → force domain synchronization. Select that option as the answer. Verification / Alternative check: Contemporary documentation shows Server Manager’s ability to manage trusts, shares, and domain controller roles, including triggering replication, aligning with the selected option. Why Other Options Are Wrong: PDC demotion: not an explicit “demote” action; role change occurred via promoting a BDC. Shutdown/restart: not Server Manager’s primary function. Enable auditing: done via User Manager for Domains/Policies. Active Directory forests: not applicable to NT domains. Common Pitfalls: Transposing Windows 2000+ AD concepts back onto NT; assuming Server Manager handled all OS-level operations. Final Answer: Synchronize the domain (force replication between PDC and BDCs)

Question 18

Consider a legacy 10BASE-T Ethernet hub (shared half-duplex). Do all attached ports share one collision domain so that the aggregate bandwidth is shared, and is it therefore correct that “the fewer ports a hub has, the less bandwidth available per p…

Accepted Answer

Introduction / Context: Hubs create a single shared collision domain where one station transmits at a time. While this means bandwidth is shared, the statement that “the fewer ports, the less bandwidth per port” is logically flawed. The number of physical ports does not mechanically reduce the per-port line rate; rather, effective throughput per host depends on actual traffic contention among active transmitters. Given Data / Assumptions: Device type: classic Ethernet hub (multiport repeater), not a switch. Duplex mode: half-duplex with CSMA/CD. All ports participate in one collision domain. Concept / Approach: On a hub, all stations share the medium. The nominal line rate per port (e.g., 10 Mbps for 10BASE-T) does not change with the number of ports. What changes is the probability of collisions and the time each host must wait to transmit as the number of active talkers increases. Thus, while more active hosts can reduce observed throughput, the blanket claim tying per-port bandwidth to the mere count of hub ports is incorrect. Step-by-Step Solution: Acknowledge: hubs share a single collision domain → shared bandwidth. Clarify: per-port line rate stays constant (e.g., 10 Mbps). Explain: contention and collisions—not port count per se—impact effective throughput. Conclude: the composite statement is incorrect. Verification / Alternative check: Measurements on lightly loaded hubs show hosts can achieve near line rate when alone; as simultaneous transmitters increase, aggregate throughput approaches but does not exceed the hub’s total capacity, divided by contention—independent of how many unused ports exist. Why Other Options Are Wrong: Correct: would wrongly imply port count sets per-port bandwidth. Only true on full-duplex/STP/jumbo frames: irrelevant to hub operation; hubs are half-duplex and do not run STP. Common Pitfalls: Confusing hubs with switches (which provide dedicated bandwidth per port); assuming idle ports reduce available bandwidth to used ports. Final Answer: Incorrect

Question 19

You plan to install a new internal CD-ROM drive in a Windows NT system and want to verify there will be no IRQ conflicts beforehand. Which built-in tool should you use to inspect current hardware resources (IRQs, I/O ports, DMA)?

Accepted Answer

Introduction / Context: On Windows NT, hardware resource conflicts such as IRQ overlaps can cause device malfunctions. The system includes a diagnostics utility that inventories hardware and shows assigned resources so administrators can plan safe installations without guesswork. Given Data / Assumptions: Target OS: Windows NT Workstation/Server. Goal: view current IRQ, I/O, DMA assignments before adding hardware. Need: a tool that reports hardware resources, not software configuration. Concept / Approach: Windows NT Diagnostics (WINMSD) enumerates devices and lists resource usage including IRQs, I/O ranges, DMA channels, and memory. This is the correct tool to assess potential conflicts. Other listed utilities either manage servers and domains (Server Manager), control service startup types (Devices), install software (Add/Remove Programs), or manage disks/partitions (Disk Administrator)—none of which display IRQ assignments comprehensively. Step-by-Step Solution: Launch WINMSD (Windows NT Diagnostics). Navigate to the Hardware/Resources sections to review IRQs and I/O mappings. Identify available, non-conflicting IRQs for the new CD-ROM controller if needed. Proceed with installation based on the resource map. Verification / Alternative check: WINMSD was the canonical NT-era tool used by administrators to troubleshoot blue screens or device failures caused by resource conflicts, confirming its role for pre-installation checks. Why Other Options Are Wrong: Server Manager: focuses on server/domain management. Devices: sets service startup; does not inventory IRQs in detail. Add/Remove Programs: installs/removes software only. Disk Administrator: partition and volume management. Common Pitfalls: Assuming Plug and Play will resolve everything automatically on NT (limited PnP support); forgetting to check motherboard documentation for reserved IRQs. Final Answer: Windows NT Diagnostics (WINMSD)

Question 20

IP subnetting rule of thumb: when multiple network segments are interconnected by routers, must each routed segment (subnet) have a unique network/subnet address to ensure correct forwarding?

Accepted Answer

Introduction / Context: IP routing depends on unique network identifiers so that routers can determine which interface to use for forwarding. Overlapping or duplicate subnet addresses cause ambiguous routes and traffic black holes. This principle applies equally to private and public addressing, and regardless of the routing protocol in use. Given Data / Assumptions: Multiple network segments are connected via routers. Each segment is intended to be a distinct broadcast domain. Routing tables map destination prefixes to next hops/interfaces. Concept / Approach: Each routed segment must have a unique prefix (network/subnet address). Routers build forwarding entries keyed by these unique prefixes. If two segments share the same subnet address, a router cannot uniquely map destinations to the correct interface, resulting in misdelivery or dropped packets. This rule holds whether you use static routes, RIP, OSPF, EIGRP, or BGP, and whether the addresses are from private (RFC 1918) or public ranges. Step-by-Step Solution: Define segments: each is a Layer-3 subnet. Assign a unique network/subnet address to each segment. Ensure routers advertise and learn non-overlapping prefixes. Verify end hosts have gateway and mask consistent with their segment. Verification / Alternative check: Labs demonstrate that overlapping subnets prevent correct ARP or route selection on multi-interface routers; renumbering to unique subnets immediately resolves the issue, validating the uniqueness requirement. Why Other Options Are Wrong: Incorrect: contradicts fundamental IP routing behavior. Only for public ranges: uniqueness is required internally as well. Only with static routes/OSPF: protocol choice does not remove the need for unique prefixes. Common Pitfalls: Accidentally reusing subnets across VPNs without NAT; split-horizon problems masked by NAT; forgetting to update DHCP scopes after renumbering. Final Answer: Correct

Windows NT Questions