JNCDS-WAN

This page documents JNCIA-Design, the associate-level credential in the Juniper design track, exam code JN0-1103. The published source describes only that certification. If you were searching for a different design exam, confirm the code and objectives on the certification site before booking, because the objectives, question count and time limit shown here belong to JN0-1103.

The exam is 65 multiple-choice questions with a 90-minute limit, delivered in English only through Pearson VUE. There is no hands-on lab component. Pass/fail status is available immediately after you finish. Practise reading a full scenario description quickly, because design questions often bury the deciding constraint in the last sentence.

No prerequisite certification is listed. Juniper recommends Design Fundamentals training plus practice exams and exam prep webinars, but states these resources are not required and do not guarantee a pass. Candidates with beginner-level exposure to network design, theory and best practices are the intended audience, so formal design experience helps but is not mandated.

Neither the passing score nor the exam fee is published in the source material this page is built from, so no figure is given here. Check the current Juniper certification page and the Pearson VUE registration flow, where the price for your region and any bundled training-credit options are displayed before you pay.

The retake policy is not stated in the available source, so verify the current waiting period and fee rules at registration rather than relying on secondhand reports. Practically, review your score report section by section, since a design exam usually exposes one or two weak domains rather than uniformly low performance across all six.

Juniper certifications are valid for three years, after which recertification is required. Plan your study and exam date with that clock in mind, and check the recertification page for the current options, such as passing a higher-level exam or retaking the current one, so the credential does not lapse unexpectedly.

Work from general to specific: start with customer network design requirements, since the life-cycle approach, proposal boundaries and capacity planning frame every later decision. Then take security and reliability and management, which cut across all network types. Finish with campus and branch LAN, campus and branch WAN, and data center design, where those principles get applied to concrete architectures.

Common weak spots are the parts that feel adjacent to configuration: WLAN design phases, RF coverage patterns and co-channel contention, plus IP fabric underlay and overlay design, routing protocol selection and scaling. Another frequent miss is treating network management and automation objectives as filler; separation of production and management traffic, configuration backups and remote console access are examinable design decisions.

No. The objectives ask you to identify roles of routers, switches, security platforms, WLAN and SDN and network management products, and to choose appropriate designs, not to write Junos configuration. Knowing what each family is for and where it fits in a topology matters more than command syntax, so prioritise trade-offs and architecture over CLI drills.