This page is C172’s help desk: the honest read on the course and the exact support behind it. The course: Network and Security Foundations, 3 CUs, in WGU's IT legacy code territory.
What C172 actually grades
The legacy-generation foundations code still live on older Degree Plans while D315 carries new enrollments. Same subject territory, different course build, and the difference matters: materials and assessment expectations belong to your code, not the subject.
How we help in this course
C172 holders get era-correct support, no D315 shortcuts pasted over a legacy rubric. If your Degree Plan shows this code, send that row as-is; the desk confirms the current expectations same-day and the work proceeds against exactly what your version requires.
Service terms are the site standard: performance-assessment work drafts in 24 to 48 hours, aspect-mapped to the current rubric with a walkthrough, revised free until the evaluation reads Competent and the course posts Passed; exam sections get preparation only, cut-score study plans, practice items, and a go or wait call, never a sit-in.
Task manuals for this course
Per-task manuals for C172, Task 1, Task 2, and exam-blueprint notes where they apply, publish as each identity verifies against the current course build; the chat desk knows live coverage same-day, and the service itself never waits on a manual.
In C172 right now?
Send the Degree Plan row and the rubric or preassessment report. First premium sample free, back in 24 to 48 hours.
A legacy row deserves era-correct handling
Holding C172 in 2026 means your Degree Plan is running the older build of the foundations course, and the only support worth buying is support aimed at that build: expectations confirmed for your version same-day, materials matched to it, and nothing borrowed from the newer build's playbook unless your version genuinely shares it. The code on your row is the contract, and the desk reads it literally. Version drift shows up in small, expensive ways, a topic weighted differently, an assessment framed another way, materials reorganized, and every one of them punishes study time spent on the wrong build. Era-correctness is not pedantry; it is the entire value of course-specific support.
Scoping an older code without guesswork
Send the row exactly as your plan displays it, plus whatever rubric or assessment detail is visible to you. Written work drafts to Competent on the aspects your version defines; exam preparation builds toward your exam's cut score with practice in its formats, and the proctored session stays yours to sit. Delivery and revision terms match the site standard either way, 24 to 48 hours and free until it clears. If your plan migrates you to the newer code mid-degree, the desk carries the transition rather than restarting you.
Prove it on the version you actually hold
The free first sample applies to legacy codes at full strength: one deliverable or prep plan built against C172 as it exists on your plan today. If a service cannot demonstrate era-correctness on a free order, it was never going to manage it on a paid one, and that is a useful thing to learn for nothing. Legacy students get full service, not leftover service.
Turning scored aspects into a section plan
WGU keeps the scoring detail for a course inside your Course of Study rather than the public catalog, so the first move in C172 is to open your own rubric and count what is there. Every aspect an evaluator scores is judged on its own against a three point scale, and a score of 2 in each aspect passes the task. Nothing averages out: a careful diagram does not lift a thin vulnerability section.
Where your course is measured by a performance assessment, that aspect list is your outline. Give each scored aspect its own heading, worded close to the rubric's own language, so scoring the document means reading down the page instead of hunting through it.
The word budget, worked. Suppose your rubric shows seven scored aspects and the directions ask for roughly 2,100 words. Reserve 150 for an opening that names the scenario and the question and 150 for a closing, leaving 1,800 for the scored body. Seven into 1,800 is about 257 words each, which is a warning line rather than a target. Weight it instead: three descriptive aspects at 200 words takes 600, two analytical aspects at 320 takes 640, two design or mitigation aspects at 280 takes 560. Those add to exactly 1,800. An aspect answered in 80 words almost always stated a conclusion with no evidence. One that swells past 600 has eaten its neighbour, and the starved neighbour is what fails.
A structure that fits a network analysis document
Written deliverables in a foundations networking course tend to take the shape of a technical report addressed to someone who has to approve a change, not an essay addressed to an instructor. Where your task directions specify a structure or supply a template, those directions win. Otherwise the shape below maps onto how networking aspects are usually worded.
| Section | What belongs in it | How it gets read |
|---|---|---|
| Scope and scenario | The organization, the sites involved, the question the report answers | Fixes the boundary every later aspect is judged against |
| Current state | Components, media, addressing, how traffic moves today | Scored for describing this network, not a generic one |
| Classification and topology | Which of LAN, WAN, WLAN, PAN, SAN, CAN, MAN or VPN applies where, and the topology each segment uses | Scored on correct use of the terms, where loose vocabulary costs points |
| Protocols | The protocols in play, the layer each sits at, why this scenario needs them | Scored for justification, not textbook definitions |
| Vulnerabilities and mitigations | Named weaknesses tied to real components, each with a control and its trade off | Where thin reports die; a threat list attached to nothing is not analysis |
| Diagram and sources | A labelled visual consistent with the prose, plus standards and scenario files cited | An uncited borrowed figure is a return |
Keep the diagram and the prose in one conversation. If the narrative describes three subnets and the drawing shows two, the evaluator has to decide which is the submission, and the safe decision is to send it back.
Evidence craft when the evidence is a standard
Networking writing has a sourcing problem essay courses do not. Half your evidence is a specification and half is vendor documentation written to sell something. A security claim supported by a datasheet has cited an advertisement.
- Prefer the neutral authority. Protocol behaviour belongs to its specification, an addressing rule to the body that publishes it, a control to a recognised framework rather than a vendor page.
- Name the version. Wireless security, cipher suites and routing behaviour all changed between versions, and a claim with no version attached cannot be checked.
- Separate what the scenario told you from what you inferred. If the brief never states a link speed, say you assumed it and why, then hold the assumption steady.
- Cite the scenario itself, and keep quoted standards text short. Figures that appear from nowhere read as invented, and submitted files pass through WGU's similarity check.
What separates Competent from a report sent back
Work at WGU is recorded as Competent or Not Competent, with no letter grades and no ordinary GPA, and because each aspect is scored alone a return is usually local. A networking report rarely comes back because the writer misunderstood networks. It comes back because one aspect asked for two things and got one.
- Every scored aspect has a visible home, and the heading borrows the rubric's own noun instead of a synonym.
- Every named weakness has a named control, and every control points back at the weakness it answers.
- The diagram and the narrative agree on device count, segment names and addressing.
- Nothing technical is asserted without a source, and nothing sourced is left uninterpreted.
Performance assessment work can be revised and resubmitted with no grade penalty, so a return is a delay rather than a disaster. The cost is time, and in a six month flat rate term time is the whole budget: courses closed per term decides the effective cost of each one. Where C172 sits alongside a proctored objective assessment, the boundary is plain. Proctored exams are yours to sit. We prepare only, and we never ask for portal credentials.
Six mistakes that cost time in C172
- Defining protocols instead of applying them. A paragraph on what a protocol does earns nothing alone. The aspect wants why this scenario needs it and what breaks without it.
- Using the classifications loosely. Calling a site link a LAN, or a remote tunnel a WAN, is the fastest way to lose an accuracy aspect in a course built on those categories.
- Listing threats with no attachment point. Each weakness has to land on a component, protocol or configuration that exists in the scenario.
- Proposing controls with no cost. Every mitigation gives something up. A control described with only benefits reads as a sales pitch and scores like one.
- Studying the wrong build. C172 is banner ITEC 2102 and the current D315 is ITEC 2112 under the same title. Material aimed at the newer build feels right and is wrong enough to cost a week.
- Writing to the prompt sentence rather than the rubric aspect. The prompt often folds two scored aspects into one sentence. The rubric is the specification.
Three questions C172 students ask
Is C172 the same course as D315?
Do I need networking experience before C172?
Can you take my proctored exam for this course?
Where C172 sits in WGU's programs
The July 2026 catalog places this code in 1 current WGU program. Open a program page for the complete standard path and term positions. The live Degree Plan remains authoritative after transfer credit, substitutions, and mentor planning.
The assessments, one by one
The public catalog does not publish this course's PA/OA identity or task count. WGU Tutors publishes at most one PA manual per course and only from a WGU-controlled public rubric. Until that source exists, PA help begins from the student's real Course of Study and OA support remains preparation only.