Exam program: Networks and IT infrastructure

IAE-EXAM-NW · version 1.0

Sections, format, sample tasks and scoring rubric of the IAE written exam in the field "Networks and IT infrastructure".

Version 1.0Effective 15 November 2026Exam in English or Russian

01. Who is the exam for?

For network engineers and administrators, system administrators, infrastructure and data center engineers, network architects and IT infrastructure managers. Admission requires a bachelor's degree or higher and at least 3 years of experience in the field (without a degree, at least 5 years). The exam tests calculations and decisions based on data on how networks and equipment work: addressing and segmenting a network, routing and link redundancy, finding a fault from measurement results, servers, data storage and backup, availability and monitoring, changes to a production network, justifying a budget and reporting after an outage. Knowledge of a particular vendor's equipment and software, commands and configuration syntax is not tested: answers are written in words, calculations and diagrams described in text, and the measurement data, equipment specifications and prices needed for the solution are given in the task. Cloud services and delivery pipelines are covered by the "Cloud and DevOps" program, network protection and penetration testing by the "Information security and risk management" program, IT service processes and service level management by the "IT service management (ITSM)" program, and programming by the "Software and data" program.

02. Format

  • 5 questions, one per section, 10 minutes each.
  • 2 cases of 25 minutes from two different sections: network design; operations and troubleshooting; server and compute infrastructure; reliability, monitoring and change management. The cases require calculations with the candidate's own data: the number of addresses and the subnet masks for network segments, link utilization and the bandwidth needed, latency and packet loss from measurement results, the capacity and performance of storage, backup and restore time from the data volume and link speed, the availability of a chain of equipment and downtime per year, the cost of options over the service life.
  • 1 question about the project from the candidate's questionnaire, 10 minutes.
  • Up to 2 hours in total, in one sitting. Pasting is disabled, and each candidate gets their own case data.

03. Sections and weights

  • Network design - 20 %: addressing and dividing a network into IPv4 and IPv6 subnets (the fourth and sixth versions of the IP protocol, with addresses of 32 and 128 bits), the mask and the prefix, the number of addresses in a subnet, the reserve for growth and the remainder of the address block, VLANs (virtual local area networks: logical segments that separate the traffic of a group of ports and devices from other devices on the same switches) and segmentation by department and purpose, static and dynamic routing between segments at the level of principles, choosing a path by metric and convergence (the time routers take to find a new path after a link fails), redundancy of links and equipment, calculating the bandwidth of links from the number of users and the traffic profile given in the task.
  • Operations and troubleshooting - 20 %: diagnosis by the layers of the network model (physical, data link, network, transport and application layers), latency, packet loss and jitter (the variation in delay between consecutive packets) and their acceptable values for voice and video given in the task, DNS (the service that finds the IP address of a host by its name) and DHCP (the service that assigns IP addresses and network settings to devices automatically), exhaustion of the DHCP address pool and name resolution errors, analysis of symptoms from the data given in the task: logs, interface error counters, link utilization, results of connectivity checks and route traces, the order of testing hypotheses by the cost of each check and the number of causes it rules out, recording the course of the diagnosis.
  • Server and compute infrastructure - 20 %: servers and virtualization, the number of virtual machines per server by processors and memory and the reserve for the failure of one server, data storage: RAID (combining several disks into one array, with or without redundancy), the usable capacity of an array, IOPS (input/output operations per second) and the lower write performance of arrays with parity, backup and recovery: RPO (recovery point objective: the longest acceptable time between the last backup and a failure, that is, the acceptable data loss) and RTO (recovery time objective: the acceptable time to restore operation after a failure), full and incremental backups (only the changes since the previous backup are copied), backup and restore time from the data volume and link speed, restore tests, capacity planning by the growth of load and data volume, power and cooling of racks at the level of calculations with the data given in the task: power draw, the power reserve of the supply, runtime on an uninterruptible power supply and heat output.
  • Reliability, monitoring and change management - 20 %: availability in percent and downtime per month and per year, the availability of components in series (the product of availabilities) and in parallel (one minus the product of unavailabilities), a single point of failure (a component whose failure stops the whole system) and its removal, monitoring of links, servers and storage, alert thresholds at which the on-call engineer has time to act before a failure, and the number of false alerts, change management on the technical side: the maintenance window and its length, the rollback plan and the time for a rollback within the window, checks after a change, equipment inventory and documentation: network diagrams, the addressing plan, the vendor support dates of equipment.
  • Professional practice - 20 %: justifying a decision and a budget, comparing options by total cost of ownership (purchase, maintenance, power and replacement over the service life given in the task), the report to management and users after an outage: what happened, how long it lasted, who was affected, what was done and what will change, work with vendors and telecom providers at the level of the service level agreement (SLA) requirements given in the task, comparing the actual availability of a link with the contracted one and calculating the credit under the contract formula, honest reporting of outages and risks, the candidate's own project.

04. Sample tasks

Question. An office has the IPv4 address block 10.20.8.0/22. The network is divided into four segments, each with its own subnet: sales (220 hosts), warehouse (96), accounting (40) and servers (20). The host counts include the gateway and the network devices of the segment, and in each subnet two addresses are not assigned to hosts (the network address and the broadcast address). Each segment needs a 25 % reserve for growth, and the host count with the reserve is rounded up. Subnets are allocated from the start of the block in descending order of size. For each segment, determine the prefix and the mask, the number of host addresses, the network address and the broadcast address. Calculate how many addresses of the block remain and in which subnets they can be allocated, and compare with the variant without a reserve for growth. Explain why subnets are allocated in descending order of size, and calculate how many /64 subnets fit in the IPv6 /56 prefix assigned to the same office.

Case. A branch office is connected to the head office by a 100 Mbit/s link. On Tuesday evening the branch replaced its access switch and moved 60 phones to a separate voice VLAN. Since Wednesday, users have complained about dropped calls between 08:00 and 09:30, and complaints about the slow accounting system in the same hours have been coming in for 2 weeks. Between 08:00 and 09:30 the link is 98 % utilized, packet loss is 3 %, the one-way latency to the head office is 95 ms and jitter is 42 ms; after 09:30 the utilization is 55 %, packet loss 0.1 %, latency 20 ms and jitter 5 ms. The requirements for voice: one-way latency at most 150 ms, jitter at most 30 ms, packet loss at most 1 %. One call takes 100 kbit/s in each direction, and up to 40 calls run at the same time at peak. Before the switch was replaced, all voice packets entered the link marked as priority traffic; after the replacement, the share of such packets is 0 %. The branch file server (6 TB of data) is backed up over the same link to the head office in the window 22:00-06:00, and the backup speed is capped at 80 Mbit/s; volumes are in decimal units (1 GB = 8,000 Mbit). Over 3 months the daily backup of changes has grown to 400 GB (it was 180 GB), and on Wednesday and Thursday the backup finished at about 09:30. Management requires an RPO of 24 hours and an RTO of 8 hours for the file server. Separate the symptoms by cause: which are linked to the switch replacement and which to the backup; compare the measurements with the voice requirements, and name how to confirm each explanation. Calculate how much backup data fits in the window, what speed is needed for 400 GB and when, at the current growth, the backup will no longer fit in a day. Check the RTO for restoring the whole server over the link, and propose a solution for the backup and for voice, with calculations. Write a message to the branch users and to management: what is known in figures, what has been done, what is proposed and when the next update will come.

The figures and circumstances of the cases are different for each candidate.

05. Scoring rubric

Each task is scored on four criteria, and the total is converted to 100 points taking the section weights into account.

  • Correctness of the solution - 40 %.
  • Reasoning behind decisions - 25 %.
  • Risks and constraints - 20 %.
  • Clarity of the answer - 15 %: structure and precise wording. Grammar and style do not reduce the score if the meaning is clear.

06. Result

  • Pass mark - 70 of 100.
  • Result in 5 business days. Those who pass receive an IAE Certified Professional certificate in the field "Networks and IT infrastructure", valid for 3 years; scores by section are in a separate report.
  • The certificate confirms that the candidate passed the written exam under this program. It is not a license or an accreditation and does not replace the network and IT infrastructure certificates of equipment vendors or other organizations. Employers and authorities make hiring and other decisions about the candidate under their own rules.
  • Retake 30 days after the first failed attempt and 60 days after the second, with no more than 3 attempts in 12 months.
  • Full terms: the Exam terms page.
  • The Credentialing Council reviews the program at least once a year.

07. What is not covered?

  • The IAE exam is not an exam of equipment and software vendors or of other organizations that certify network and IT infrastructure specialists, is not affiliated with them and does not replace their exams. The topics and tasks of the IAE exam do not repeat the syllabi of those exams. The names of certifications and organizations belong to their owners.
  • Cloud services, infrastructure as code and build and delivery pipelines are covered by the "Cloud and DevOps" program. In this exam, availability and recovery are calculated for the organization's own equipment and communication links; if a cloud service is part of a task, its availability and speed are given in the task.
  • Network protection, firewall rules, penetration testing and information security risk management are covered by the "Information security and risk management" program. In this exam, network segmentation is assessed by addressing and traffic, and the security requirements for segments are given in the task.
  • IT service processes, including service level management, the service desk and change approval, are covered by the "IT service management (ITSM)" program. In this exam, a change is assessed on the technical side (the maintenance window, the rollback plan, checks after the work), and the SLA requirements for a vendor or telecom provider are given in the task.
  • Programming, including automation scripts, is covered by the "Software and data" program. In this exam, no code is written: the steps are described in words.
  • The design of a building's power supply and cooling and checks against the electrical safety and building codes of a particular country are not covered. The supply capacity and the specifications of uninterruptible power supplies and cooling for rack calculations are given in the task.
  • Work with the equipment and software of a particular vendor, its commands and configuration syntax are not tested. Answers are written in words, calculations and diagrams described in text, equipment specifications and measurement data are given in the task, and calculations are done by hand or on a calculator.

08. Preparation

  • The practice exam runs in the same interface: 2 questions from different sections, a 15-minute case and a project question.
  • Review the calculations: the number of addresses and the subnet mask by prefix length, dividing an address block into subnets of different sizes and the remainder of the block, the number of IPv6 subnets by prefix length, link utilization and the bandwidth needed for a number of users and simultaneous calls; comparing latency, packet loss and jitter with the requirements given in the task; the number of virtual machines per server with a reserve for the failure of a server, the usable capacity and IOPS of RAID arrays of different levels, backup and restore time by data volume and link speed, checking the RPO and RTO, the growth of data volume and the capacity reserve, the power draw and heat output of a rack, the runtime on an uninterruptible power supply; the availability of components in series and in parallel, downtime in minutes per month and per year, the length of the work and of a rollback in the maintenance window; the total cost of ownership of options over the service life, the SLA credit under the terms given in the task.
  • Formulas are given in the task when needed, as are equipment specifications and the acceptable values of latency and packet loss. A calculator is enough for the calculations, and reference materials may be used.
  • Answer by the points of the task: the method or formula, the calculation on your own figures, the decision, risks and what needs to be checked. Describe a network diagram in text: segments, addresses, equipment and the links between them. Pasting is disabled, so the answer is typed.
  • Prepare the project description for the questionnaire: your role, the network or system and its size (the number of sites and users), the task, measures before and after (for example, availability or time to restore), the decisions taken, the result in figures. Do not include confidential employer data (network diagrams and addresses, equipment configurations, figures the company does not publish) or users' personal data: the result can be given as a percentage of the starting level. The project question is based on this description.
  • Text from AI services and help from other people are not allowed.

Exam

Book the exam

The questionnaire takes 15 minutes. Admission decision in 1 business day.

Candidate questionnaire

Received

Admission decision within one business day

FieldNetworks and IT infrastructure
DurationUp to 2 hours
Result5 business days