Day objective — consolidate all six MEF-NF domains, drill terminology, score yourself on the 20-question practice engine, and convert weak domains into a concrete revision plan.
Domain Recap — the Whole Map
One sentence per domain. If any sentence doesn't feel obvious yet, the linked panel is your revision target.
Distribution of this course's teaching time — a sound revision proportion. For the official exam blueprint and current question counts, always check MEF's certification portal before booking.
| Domain | The one sentence | Revise at |
|---|---|---|
| IP / WAN prerequisite | Addresses are hierarchical, forwarding is longest-prefix match, OSPF builds the map that fills the table | Day 1 · 1.3, 1.6, 1.8 |
| Transformation & NaaS | Cloud-speed business needs API-speed networks: standardized services + automation = NaaS under MEF 3.0 | Day 2 · 2.1–2.2 |
| SDN | Separate control from forwarding, centralize the brain, program flows via OpenFlow/NETCONF beneath REST intents | Day 2 · 2.4–2.7 |
| NFV / Telco Cloud | Functions become software (VNF→CNF) deployed by MANO (NFVO/VNFM/VIM) on shared cloud infrastructure | Day 3 · 3.1–3.4 |
| Carrier Ethernet | Four EVC topologies (E-Line/LAN/Tree + E-Access) built from UNI/ENNI/EVC with CIR/EIR bandwidth profiles | Day 3 · 3.5–3.7 |
| L2/L3 Services | The provider either bridges your frames (you route) or routes your packets (they route) — pick by control vs convenience | Day 3 · 3.8 |
| SD-WAN | An app-aware, policy-driven L3 overlay (SWVC over TVC/UCS) standardized by MEF 70.1, secured toward SASE/ZT | Day 4 · 4.1–4.4 |
| LSO | Seven reference points automate design→activation→assurance→billing; Sonata & Interlude cross provider boundaries | Day 4 · 4.5–4.7 |
- Enablers vs products vs fabric — SDN/NFV enable, services are sold, LSO automates: the narrative thread of every scenario question
- Follow one order end-to-end — intent → POQ → Quote → Order → MANO instantiates → SDN wires → SOAM assures: if you can tell this story, you own the syllabus
Exam Format & Approach
MEF-NF is a foundations-level, multiple-choice certification exam covering the domains of this course. Here is how to approach it — and how to register.
- Definition recall — "Which reference point connects SP BUS to Partner BUS?"
- Best-fit scenario — "4 sites, any-to-any L2, leaf isolation not required → which service?"
- Distinguish siblings — EPL vs EVPL · VNF vs CNF · Sonata vs Interlude · CIR vs EIR
- Order the stack — layers, MANO blocks, LSO verticals
- Answer in MEF vocabulary, not vendor slang (say SWVC, not "fabric")
- Acronym pairs are the classic traps — drill the flashcards in 5.3
- Watch qualifiers: committed vs excess, subscriber vs operator, intra- vs inter-provider
- Book via the official MEF certification portal (proctored online delivery)
- Confirm current question count, duration and pass mark on the portal — they are revised periodically
- Bring nothing but vocabulary: it's closed-book, foundations-level
Name the domain first
Every stem belongs to one domain. Classifying it instantly eliminates cross-domain distractors.
Find the discriminating word
"between operators" → ENNI/Sonata/Interlude. "no SLA" → yellow/EIR. "rooted" → E-Tree. One word usually decides.
Eliminate the sibling trap
Wrong answers are usually the concept's nearest sibling (VNFM for NFVO). Say the definition of your pick before committing.
Flag, don't stall
Foundations exams reward coverage. Mark hard ones, sweep back at the end.
- Question styles — recall, scenario best-fit, sibling discrimination, stack ordering
- Key terminology — the exam is largely a vocabulary precision test; drill 5.3 until instant
- Registration process — official MEF portal; verify current format details there before booking
Key Terminology Flashcards
Click a card to flip it. If the definition surprises you, that acronym goes on your study plan. These twelve carry the highest exam weight per second of revision.
User Network Interface — the demarcation between subscriber and service provider responsibility. Where SLAs are measured.
External Network-Network Interface — demarcation between two operators composing one service. S-VLAN hand-off.
Ethernet/Operator Virtual Connection — EVC associates UNIs end-to-end (subscriber view); OVC is one operator's segment (wholesale unit).
Committed rate = green, SLA-backed. Excess rate = yellow, best-effort, no SLA. Beyond both = red, dropped at ingress (MEF 10.4).
SD-WAN Virtual Connection — the L3 service joining SD-WAN UNIs; forwards app flows per policies over TVCs.
Tunnel Virtual Connection rides one Underlay Connectivity Service (broadband, LTE/5G, MPLS, Carrier Ethernet).
Management & Orchestration = NFVO (network services) + VNFM (function lifecycle) + VIM (infrastructure resources).
Virtualized Infrastructure Manager — allocates NFVI compute/storage/network. OpenStack classically; Kubernetes for CNFs.
Network as a Service — connectivity consumed like cloud: standardized services, API lifecycle (order→assure), subscription economics.
Inter-provider business reference point: SP BUS ↔ Partner BUS. APIs: POQ, Quote, Order, Inventory, Billing, Tickets.
Inter-provider orchestration reference point: SP SOF ↔ Partner SOF — operational control of the partner-delivered service.
Product Offering Qualification — "can you deliver this product at this location?" Green/yellow/red serviceability + alternatives.
- Sibling pairs to drill — EPL/EVPL · EVC/OVC · CIR/EIR · NFVO/VNFM · Sonata/Interlude · Legato/Presto · SASE/ZT
- Numbers to keep — MEF 6.3 (E-services), 10.4 (attributes), 61.1 (IP), 70.1 (SD-WAN), 55.1 (LSO), 117 (SASE), 118 (ZT)
Practice Exam Engine
Twenty questions across all domains, in exam style: one defensible answer, plausible distractors, instant explanation. Your per-domain score feeds the study plan in 5.5.
Each opens that day's lab panel: pick a length (10 → everything), drill single topics, and read the explanation on every answer. The per-domain result bars tell you exactly which panel to revisit. Suggested exam gate: ≥80% on a 40-question run of each day.
- Self-assessment — ≥80% overall and no domain below 60% = book the real exam459 questions total in this course4 × per-day mastery quizzes + this 20-Q exam
- Wrong answers are gold — each explanation names the panel that teaches it; go there before retaking
Personalized Study Plan
Take your practice-exam domain bars and turn them into a plan: weakest domain first, one revision block per domain, re-test after each block.
| Weak in… | Revisit (panels) | Primary reading | Hands-on booster |
|---|---|---|---|
| IP & Routing | 1.3 · 1.6 · 1.8 | RFC 2328 §1–4 (OSPF concepts), any CIDR primer | Redo Lab 1 solo — no notes, 45 min budget |
| NaaS & SDN | 2.2 · 2.4 · 2.5 | MEF 3.0 framework overview; ONF OpenFlow whitepaper | Lab 2: swap ONOS↔ODL and repeat the re-route |
| NFV & Telco Cloud | 3.1 · 3.2 · 3.3 | ETSI NFV architectural framework (the MANO figure) | Lab 3 part 1 with a second NF (vFW next to vRouter) |
| Carrier Ethernet & L2/L3 | 3.5 · 3.6 · 3.7 · 3.8 | MEF 6.3 service definitions; MEF 10.4 attribute list | Re-run the token-bucket sim; design an E-Tree variant of Lab 3 |
| SD-WAN & LSO | 4.3 · 4.6 · 4.7 | MEF 70.1 (SWVC attributes); MEF 55.1 (reference points) | Lab 4: add an Inventory query to your collection |
Days 1–2 · Heal the weakest domain
One domain, its panels, its lab booster. Nothing else.
Days 3–4 · Second-weakest + flashcards daily
The 12 cards of 5.3 every morning until every flip is boring.
Day 5 · Full practice retake
Fresh run of 5.4. Any domain still <60% → repeat its block, postpone booking.
Days 6–7 · Story rehearsal + book it
Tell the end-to-end order story (5.1) out loud, spec numbers included. Then register on the MEF portal.
- Self-assessment — practice-engine bars are your syllabus coverage map; trust them over gut feel
- Reading recommendations — read specs for the figures and attribute tables, not cover-to-cover
- Retention rule — every revision block ends by re-explaining the concept to the rubber duck (or a colleague)
You can now order a network like software
IP plans, OSPF, SDN flows, CNFs, E-services, SD-WAN policies and Sonata calls — all built by your own hands this week. Go get the certificate.