D303 Azure Fundamentals carries the banner number ITCL 2100 and is worth 3 competency units. It covers cloud concepts, the core Azure services, the management tools that operate them, general and network security features, identity, governance, privacy and compliance, and Azure cost management with service level agreements. D303 and ITCL 2100 are one requirement, not two. It is a breadth course: the point is not to become expert in any one service but to know what each thing is for and which one a described problem calls for.
Breadth courses reward organized memory, not intuition
The difficulty in D303 is volume rather than depth. There are many services, several management tools, multiple identity and governance features and a pricing model with its own vocabulary, and none of it is individually hard. What defeats students is trying to absorb it as a list. The material is only manageable when it is organized by the question it answers.
Four organizing questions will hold most of the syllabus. What kind of thing is this: compute, storage, networking, database, identity or a management layer? What problem does it solve that the neighboring service does not? What does it cost, and what drives the cost up? And what promise does the provider make about it, which is the service level agreement question. A service you can answer all four questions about is learned. A service whose name you recognize is not.
The boundary between similar services is where most confusion lives. Several compute options overlap. Several storage tiers exist for reasons that only make sense once you know the access pattern each assumes. Governance features and identity features sound alike and do different jobs. Studying the differences rather than the definitions is the single change that moves people through this course fastest.
Cost management and service level agreements are worth real attention because they are the parts students skip. Both are conceptually simple and both generate questions, since they are how the shared responsibility of cloud actually shows up on a bill and in a contract.
WGU reports this course as Competent or Not Competent rather than by letter grade, holds no ordinary grade point average, and places its 3 competency units inside a six month term charged at a flat rate. Foundation courses like this one are usually the cheapest place to buy back term time, because the material rewards concentrated study.
Working from the rubric aspects, or from the blueprint
If your version of D303 is assessed by a performance assessment, the aspects your evaluator scores give you the outline, and WGU requires a score of 2 in each aspect for a task to pass. Aspects are judged independently, so completeness beats brilliance in one section.
Budget before drafting. Start from a rubric of six scored aspects with a target near 1,800 words. Reserve 140 words to describe the organization and its workload, and 100 for the close, which leaves 1,560. Two aspects that ask you to select services and justify the selection take 330 words each, or 660 together, because each needs the requirement, the candidate options and the reason for the choice. The four remaining aspects, typically covering identity, governance or compliance, cost, and the service level agreement position, take 225 each for 900. Those figures sum to 1,560 exactly.
If instead your version is assessed by an objective assessment, run the same arithmetic against study time rather than words. Divide the published domains by weight, give the heaviest domain the most hours, and schedule a retrieval session for each domain rather than a single pass through all of them. Recognition and recall are different abilities, and only recall is tested.
Either way, build a comparison table as you study. Service, category, what it is for, what it costs on, what it is not for. That table is the artifact that makes the material stick, and it doubles as the evidence base if the course asks you to justify a selection in writing.
Shape for a cloud service selection document
When D303 work asks you to recommend Azure services for a described organization, these proportions carry the document.
| Section | What belongs there | Share |
|---|---|---|
| Workload profile | What the organization runs, how variable the demand is, and where its users are. | 10 percent |
| Service selection | Each recommended service, the requirement it meets, and the option you rejected. | 24 percent |
| Identity and access | Who signs in, how, and what they are allowed to do once inside. | 14 percent |
| Governance and compliance | Policy, tagging, resource organization, and the privacy obligations in play. | 16 percent |
| Cost position | What drives spend for the chosen services and the levers available to control it. | 16 percent |
| Service levels | What the provider commits to, what it does not, and what that means operationally. | 13 percent |
| Close | The assumption you are least sure of and what would settle it. | 7 percent |
Citing a platform that changes every quarter
Cloud platforms move faster than textbooks. In this subject the authoritative source is the provider's own current documentation, and the practical rule is to cite the documentation page and give the date you consulted it. A service tier, a regional availability or a pricing model can change between terms, and an undated claim about any of them is a claim with a shelf life you did not declare.
Distinguish the three source types you will use. Provider documentation states what the service does and what it commits to. Independent technical writing explains tradeoffs the provider has no incentive to highlight. Course materials define the scope you are being assessed against. Use all three, and never let a video or a forum answer stand as the sole support for a technical claim.
Be careful with pricing figures. If you quote a number, name the region, the tier and the date, because every one of those changes the figure. Where a general statement will do, prefer describing the cost driver rather than the price: saying that a storage tier trades retrieval cost against storage cost is durable, while saying it costs a specific amount per gigabyte is true for about a quarter.
Use the citation style your task specifies and cite at the point of claim. In a document full of service names it is easy to write a paragraph of platform facts with a single citation at the end, which leaves an evaluator unable to tell which claim came from where.
What earns Competent, and what comes back
Work that passes shows selection rather than listing. Each service named is tied to a requirement from the scenario, an alternative was considered, and the reason for the choice is stated in terms of the workload rather than in adjectives. Identity, governance, cost and service levels each get a real answer instead of a sentence.
Returns follow a few reliable patterns. Services are recommended with no requirement behind them. Two services that do different jobs are treated as interchangeable. The cost section says the solution is cost effective without naming a single cost driver. Governance and identity are merged into one paragraph so one of the two aspects has no home. Or the recommendation ignores something the scenario stated plainly, such as a data residency constraint.
A quick check before submitting: for every service you named, write one sentence beginning with the requirement it satisfies. Any service that resists that sentence is in the document because you knew it, not because the scenario needed it.
There is no grade penalty for revising and resubmitting performance assessment work at WGU, so submit at the point where every aspect has a genuine answer. Objective assessments at WGU are proctored, and our boundary is absolute: preparation only, meaning service comparison drills, terminology work, practice questions and an honest read of your preassessment result. We do not take an exam on anyone's behalf, we are uninvolved while any assessment runs, and we never request or hold portal credentials.
Too many services, none of them sticking?
Send your D303 rubric or preassessment report. We build the comparison table, the drill set and the study order that fits the time you have left.
Six mistakes that cost time in D303
- Memorizing definitions instead of boundaries. Knowing what two similar services each do is easy. Knowing which one a scenario calls for is what gets tested.
- Skipping cost and service levels. They feel administrative and they are heavily represented, because they are how cloud decisions actually get made.
- Confusing identity with governance. One controls who you are and what you may do, the other controls how resources are organized and constrained.
- Quoting undated prices. Name the region, the tier and the date, or describe the cost driver instead of the number.
- Recommending without rejecting. A selection with no alternative considered reads as a preference rather than a decision.
- Ignoring a stated constraint. Data residency, compliance and availability requirements in a scenario are there to steer the answer.
Three questions students ask about D303
Do I need an Azure subscription to get through this course?
How much of this is memorization?
Is D303 the same course as ITCL 2100?
Where D303 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.