Ruankao Network Planning Designer (Senior) study guide
Ruankao Network Planning Designer (Senior) · Work through your exam, one topic at a time.
This independent study page provides practice for Ruankao Network Planning Designer (Senior). Its editorial learning areas include Computer architecture, logic and data representation; Computer Network Fundamentals and Architecture; Physical Layer and Data Communication; Data Link Layer and LAN Technologies; Network Layer Protocols and Routing; Transport Layer and Application-Layer Protocols; Network Interconnection and Device Configuration; Network Design and Engineering Practice; Network Operating Systems, Servers and Application Services; Network boundaries and protected communication; Project scope, scheduling and earned-value models; Continuity, backup and technical recovery. The Ruankao Network Planning Designer (Senior) study guide has 12 sections and about 7,547 words.
01Computer architecture, logic and data representation
This domain examines the stored-program machine: how instructions and data share one memory, how the processor fetches and executes them, and how the memory hierarchy and instruction-set design affect performance. Instructions and data share one memory and one set of buses.
713 words, about 4 min02Computer Network Fundamentals and Architecture
The fundamentals domain is the frame everything else hangs on. This chapter develops whether you can place a function, a PDU, a device or a standard at the correct layer, and whether you can compute channel capacity and delay - not whether you can merely recite layer names.
482 words, about 2 min03Physical Layer and Data Communication
This domain covers what actually carries bits: media, line coding, modulation, multiplexing, error detection and the dumb devices that regenerate signals. Questions are typically one-line discriminators plus a Hamming or CRC calculation.
546 words, about 3 min04Data Link Layer and LAN Technologies
This domain tests Ethernet mechanics, switching behaviour, VLANs, spanning tree, wireless LANs and point-to-point link protocols. It is the most configuration-adjacent of the lower-layer domains.
578 words, about 3 min05Network Layer Protocols and Routing
Addressing and routing dominate this domain: subnetting arithmetic, protocol behaviour, and the operational differences between RIP, OSPF and BGP. Expect one or two multi-step subnetting questions.
504 words, about 3 min06Transport Layer and Application-Layer Protocols
This chapter develops connection mechanics, port numbers, and the request/response behaviour of the core services. Port confusion is the most common single source of lost marks across the whole paper.
502 words, about 3 min07Network Interconnection and Device Configuration
This domain is operational: interface setup, routing configuration, ACLs, NAT, firewall policy and wireless controller integration. Questions appear as command snippets where you must spot the missing or wrong line.
498 words, about 2 min08Network Design and Engineering Practice
Design questions test whether you can turn requirements into a hierarchical topology, an addressing plan and a cabling specification that survives inspection. Numbers matter more than prose here.
474 words, about 2 min09Network Operating Systems, Servers and Application Services
Server-side knowledge is tested through role configuration, permissions arithmetic and storage/availability design. Expect a permission-intersection question and a RAID capacity question.
467 words, about 2 min10Network boundaries and protected communication
This domain tests perimeter architecture and the device behaviour that makes segmentation real. Questions tend to be scenario-based: where a host belongs, which rule is needed, and what a given protocol actually protects.
430 words, about 2 min11Project scope, scheduling and earned-value models
Domain 2 tests whether you can define a project precisely, separate it from operations, program, and portfolio, and read an organizational chart to determine how much authority a project manager actually holds. Items often present a short organizational scenario and ask which structure or PMO type it describes, or ask where a given input belongs: enterprise environmental factors or organizational process assets.
1,623 words, about 8 min12Continuity, backup and technical recovery
This domain tests continuity planning: how an organisation keeps critical services running during disruption and how it recovers afterwards. Distinguish the continuity plan from the disaster recovery plan and know the time-based metrics precisely.
730 words, about 4 min