98-362 Windows Development Fundamentals: preparation and scheduling guide
Microsoft Exam 98-362, Windows Development Fundamentals, is an entry-level MTA exam for candidates who want to demonstrate Windows programming and application-development knowledge. It suits learners with some exposure to C# or Visual Basic .NET who need to decide whether their current Windows desktop development skills are ready for assessment. Use this guide to map the official topic scope to hands-on practice, identify gaps before booking, and verify whether a delivery option is currently available.
Decide whether 98-362 matches your goal
98-362 is aimed at candidates seeking to prove Windows programming and application-development knowledge and skills, rather than a broad software-development credential. It is a sensible target when your learning has centered on Windows desktop application concepts, .NET language fundamentals, and the kinds of application components named in the official objectives.
Microsoft’s MTA pathway material places 98-362 within an entry-level training and certification program covering IT infrastructure, database, and software-development fundamentals. That positioning matters when setting expectations. Treat the exam as evidence of foundational Windows development knowledge, not as a substitute for a portfolio, production experience, or a current role-based developer certification.
The best fit is a learner who can already read and modify small examples in a Microsoft .NET language, then explain why a Windows application uses a particular project type, control, event, service, or deployment approach. The official preparation guide specifically expects some experience with C# or Microsoft Visual Basic .NET. If basic variables, methods, classes, event handlers, and debugging are still unfamiliar, build that base first rather than trying to memorize Windows terminology.
A practical decision test is to choose a small desktop-app idea, such as a contact lookup form or a settings utility. If you can describe the interface, identify user actions that must raise events, separate reusable interface pieces from application-specific behavior, and explain how the app would obtain and deploy its data, the exam scope is likely aligned with your current direction. If not, use the project as a learning vehicle before setting an appointment.
Who should pause before booking
Candidates whose experience is limited to browser-based development, cloud services, or command-line programs may find several 98-362 topics unfamiliar. Windows Forms, WPF, Windows Services, Win32, graphical controls, and desktop deployment all appear in the official scope. Plan time for those concepts rather than assuming general coding knowledge transfers automatically.
Do not infer current availability from older pathway documents. The current Certiport MTA Objective Domains page displays objective downloads for several MTA exams but does not display 98-362. That does not, by itself, establish the exam’s status. It does mean you should verify availability with the relevant official scheduling route before committing to a course, voucher, or study calendar.
What skills does the exam measure?
The published 98-362 preparation guide concentrates on the building blocks of Windows-based applications: application types, graphical interface design, Visual Studio projects, Windows Forms behavior and reuse, services, data access, and deployment. Convert each topic into an explanation task and a small build task; recognition alone is a weak form of preparation.
The official guide names Windows Forms, Windows Presentation Foundation (WPF), Windows Services, and Win32 applications. Start by distinguishing their purpose at a conceptual level. A candidate should be able to identify what makes an application graphical, what background service behavior means in a Windows context, and why project and application choices affect the way software is designed and deployed.
User-interface design principles are explicitly included for graphical Windows applications. Study this as a design topic, not a vocabulary list. For every interface you create, ask whether labels make the required action clear, controls match the input they collect, feedback is visible, and the flow prevents avoidable user mistakes. You do not need to claim a preferred design pattern to practice this well; make and justify straightforward design choices.
The objectives also include creating Windows-based applications with Visual Studio, including project types and application-project components. Practice opening a project and identifying the parts that define its interface, code, references, configuration, and output. The exact tools available to you may differ, but the learning goal is to connect project structure with application behavior rather than treating files as unrelated artifacts.
Windows Forms deserves deliberate attention. The official scope includes creating and handling events, Windows Forms inheritance and visual inheritance, and creating new graphical controls or extending existing controls. These are connected ideas: an event gives a form or control behavior, inheritance enables reuse, and a custom or extended control packages a repeated interface need.
The remaining official areas complete the application lifecycle. The guide covers programming and hosting Windows Services on a Windows computer, accessing data from various sources for use in a Windows-based application, and successfully deploying a Windows application to target computers. Build study notes around the route from a user action, to processing, to data, to a usable installed application.
Avoid invented blueprint weights
Use the named objective areas to plan study time; the supplied official objective guide identifies topics but does not provide supported domain percentages for 98-362. Do not assign priority from third-party weight tables, unlabeled percentages, or claims that one area is worth more than another.
Instead, rate each official area as ready, developing, or unfamiliar. An unfamiliar area that appears explicitly in the guide deserves focused practice even if you find an unsourced study plan that minimizes it. This approach is more durable than optimizing around an unverified scoring breakdown.
Build skill, not a stack of notes
A small Windows application is the most efficient way to connect the 98-362 topics. Build one modest project in your chosen .NET language, then revisit it repeatedly: improve the interface, add event-driven behavior, reuse a form element, obtain data, consider service behavior, and document how the application would reach a target computer.
Keep the project intentionally narrow. A simple desktop utility with a main form, input controls, an output area, and a data-backed feature is enough. The purpose is not to create a commercial product. It is to make each official topic tangible and expose where you can follow instructions without understanding the design decision behind them.
Begin with the application type. Write a short comparison in your own words covering Windows Forms, WPF, Windows Services, and Win32 applications. Then state which type fits your practice app and why. This forces a useful distinction between an interface technology, a background-oriented service, and a Windows application category.
Next, create the graphical surface. Add controls deliberately, name them clearly in your notes, and trace the expected user journey from opening the app to completing one task. Review the layout against basic user-interface design principles: readable prompts, sensible control choice, clear feedback, and a predictable action path. Change one confusing element and record why the revision improves the interaction.
Move from appearance to behavior by attaching an event to a user action. For example, a button can validate entered information and update a result area. The important exercise is to explain the chain: a user action occurs, an event is raised, the handler runs, and the interface reflects the result. Repeat the exercise with a different control or event so that event handling does not become a single memorized pattern.
Then introduce reuse. Create a repeated interface requirement, such as a common header, a validation-aware input component, or shared presentation behavior. Explore how a derived form or extended control could avoid duplication. Contrast visual reuse with copying code into several forms. If you cannot explain what is inherited and what remains specific to a form, return to a smaller example.
Data work should be equally concrete. Identify a source your practice application can access, define what information the interface needs, and follow the flow from retrieval to display. The official objective is broad—accessing data from various sources for use in a Windows-based application—so focus on the reasoning: what data is required, where it comes from, how the application uses it, and how errors or missing data affect the interface.
Finally, write a deployment checklist for your app. Include the target computer, the application output, dependencies you know the application needs, and how you would confirm that the installed application starts successfully. The official guide includes successful deployment to target computers; treating deployment as an afterthought leaves a real gap in the skill map.
Use active recall after every build session
Close the project and answer short prompts without looking at code: Which application type is this? What event changes this control? What behavior would belong in a reusable control? What data does the form need? What must be considered before deployment? Your answers reveal conceptual gaps that compiling code can hide.
Maintain an error log rather than rewriting every lesson. Record the mistaken assumption, the corrected explanation, and one action that would have exposed the issue earlier. Examples include confusing a service with a graphical app, treating an event handler as an arbitrary method, or copying a control instead of considering extension or inheritance. Review that log before revisiting notes.
Follow a practical study roadmap
Study in dependency order: application concepts first, graphical projects and interface behavior next, reuse and services after that, then data and deployment. This sequence reduces context switching because later practice depends on a working understanding of the earlier desktop application structure.
Phase one is orientation. Read the official 98-362 guide and make a checklist using its exact topic areas. For each one, write a plain-language definition and a question you should be able to answer. Do not schedule this phase around an assumed question count, score, duration, or blueprint percentage; none of those details are established in the supplied official material.
Phase two is application-type and project fluency. Compare Windows Forms, WPF, Windows Services, and Win32 applications in your notes. Create a Windows-based project in Visual Studio and identify its project type and key application-project components. Your exit condition is the ability to explain the role of each component in the project you built, not merely to recognize its name.
Phase three is graphical interface and events. Create a form, add controls, make one user action trigger a useful result, and revise the layout based on interface design principles. Test both ordinary and invalid inputs in your own practice app. The goal is to connect design, interaction, and code behavior in one mental model.
Phase four is reuse and extension. Rework one repeated visual element so it is represented through a reusable form or control approach. Study Windows Forms inheritance and visual inheritance alongside custom or extended controls because they address related reuse decisions. Explain the benefit and limitation of your approach in a few sentences before moving on.
Phase five covers the non-interface parts of the scope. Make a written model of a Windows Service: what it is intended to do, how it differs from an interactive graphical application, and what hosting on a Windows computer involves at a conceptual level. Then add a data-access exercise and finish with deployment planning for the application you already built.
Phase six is consolidation. Shuffle your topic checklist and answer mixed prompts. A good review question crosses boundaries: for example, how would an event-driven interface obtain information from a source, present a result clearly, and be prepared for deployment? Mixed review is more useful than repeating a chapter in isolation because the official scope itself spans the full application path.
Choose resources carefully
Start with the official objective guide because it names the scope for 98-362. Microsoft Learn describes self-paced modules and tutorials as interactive skill builders that can be completed at an individual pace, and its preparation guidance says study guides and preparation resources can help candidates focus their work. Use those resources to strengthen concepts where they match your gap list.
The Microsoft Learn Software Development Fundamentals video series is explicitly described as preparation for 98-361, not 98-362. It may help only as general introductory context when a topic overlaps your foundational needs; it is not evidence of the 98-362 objective set. Keep the 98-362 guide as the boundary for exam-specific study.
Do not substitute recalled questions, unauthorized materials, or answer-only files for learning. They cannot prove that you can interpret a new scenario involving an application type, event, inherited form, data source, service, or deployment requirement. A better checkpoint is rebuilding a small feature from a written requirement and explaining each design choice afterward.
Find and close the gaps that matter
The most common preparation failure is treating the exam as a list of unrelated definitions. Counter that by requiring evidence for every objective: a working example, a diagram, or a concise explanation tied to your own project. If you cannot produce one of those, mark the objective for another pass.
Watch for four specific blind spots. First, learners sometimes focus on form layout and neglect the event model. Second, they may write repeated controls without studying inheritance, visual inheritance, or extension. Third, data retrieval can be practiced as a code snippet without explaining how the graphical application uses the result. Fourth, a project that runs on the development machine can create false confidence when deployment has not been considered.
Use a three-column readiness sheet. In the first column, copy the official objective area. In the second, write what you can do without help. In the third, list the next observable task. For example, under graphical controls, the next task might be to create or extend a control and explain how it is reused. Under services, it might be to diagram how a Windows Service differs from the graphical practice app.
Set your booking decision around the completed sheet, not around a fixed number of study days. You are ready to investigate scheduling when every official topic has a credible explanation and you have practiced the connected skills in a Windows-based application. If several areas remain definition-only, delay the booking decision and return to building.
Use practice tools as diagnostics
Microsoft Learn says that some exams have free Practice Assessments, and availability can vary. It also notes that a Practice Assessment can be available in a language that is not the same as the exam language. Check the official exam and preparation pages rather than assuming an assessment exists for 98-362 or that its language options match a delivery option.
If an applicable official assessment or prep video is available, use the result to prioritize study rather than to predict an outcome. Review every missed or uncertain item by returning to the relevant official topic, then complete a related hands-on task. A score without a correction plan is only a snapshot.
Verify delivery options before you schedule
Confirm that 98-362 can currently be scheduled through an official route before making financial or calendar commitments. The supplied current Certiport objective-domain page does not list 98-362 among its displayed downloads, while older official pathway and objective documents identify the exam. That combination calls for verification, not an assumption about availability or retirement.
Microsoft’s scheduling guidance says to begin from the certification overview or certifications list, open the certification, and use the Schedule exam section to select an available provider. When more than one provider appears, the page explains that candidates taking a certification independently or through training generally select Pearson VUE, while students, academic-institution members, and MOS candidates select Certiport. Provider choices shown for a particular exam are the controlling information.
Do not state that an online delivery option exists merely because online testing is available for some Microsoft certification exams. Microsoft notes that if an online option is not shown, it is not available from that exam provider. It further states that Certiport does not offer online proctored exams at this time. If your available route is different, use the options displayed by that route and follow its requirements.
If the official page presents a schedule action, you may be prompted to sign in to or create a Learn Profile. Microsoft advises using a personal Microsoft account and indicates that the legal name in the profile must match legal identification for the exam. Check this early, especially if you have used a work or school account for training.
Microsoft states that certification exams can be scheduled no more than 90 days in advance. Its current guidance also says that, through Pearson VUE, a candidate can have a maximum of two Microsoft Certification exams scheduled at a time. These are general scheduling rules from the cited page; they do not establish that 98-362 itself is available through Pearson VUE or any other provider.
Choose a testing setting based on the displayed option
A test center can be a practical choice when you want a pre-configured environment and do not want to validate your own computer or install required exam software. Microsoft describes online proctored testing as requiring the candidate to ensure that the computer and exam area meet security standards. Select only from the options actually offered for the exam and provider you verify.
If an official online appointment is offered by the provider, complete the required system pre-check before registering, as Microsoft instructs for online exams. If you need an accommodation, request it before scheduling so the provider has time to review the request and determine whether the testing environment supports your needs.
Make the final go or no-go decision
Book only after you have verified live availability and can demonstrate every published objective in context. A defensible final review is not a marathon of notes: it is a short walkthrough of your practice application, your readiness sheet, and the official scheduling path.
On the technical side, explain the application types in scope, show a graphical interface designed for a user task, trace an event into visible behavior, and explain one reuse decision involving forms or controls. Then describe how the application obtains data, how a Windows Service differs from that interactive application, and what deployment to a target computer requires.
On the administrative side, verify the provider option, location or online availability if shown, profile details, identification requirements presented during registration, and any accommodation process that applies to you. Microsoft also provides an exam sandbox so candidates can experience the look and feel of an exam before taking it; use it when relevant to familiarize yourself with the interface rather than as a substitute for technical preparation.
After booking, retain the topic checklist. Any weak point should become a focused final exercise: revise a form design, add and explain an event handler, document a custom-control decision, diagram data flow, or write the deployment steps for your project. That work is directly tied to the published 98-362 scope and remains useful whether your appointment proceeds or availability requires you to reconsider the certification path.
Conclusion
98-362 is best approached as a foundational Windows desktop development assessment with a clear, practical scope. Build and explain a small Windows-based application, using it to connect interfaces, events, reusable forms or controls, services, data access, and deployment. Because the supplied current objective-domain listing does not display 98-362, verify current scheduling availability through the official route before you book. That sequence protects both your study time and your scheduling decision.
