AT-510 Exam Guide: Verify the Scope, Build the Right Study Plan, and Prepare for Technical Scenarios
The supplied official-source snapshot does not identify AT-510’s exam owner, certification title, audience, measured skills, prerequisites, delivery format, scoring model, or current availability. That limitation changes the first preparation decision: verify the exam record before buying training or scheduling a sitting. This guide gives you a disciplined way to do that, then turns the available technical evidence into a conditional study plan covering endpoint connectivity, troubleshooting utilities, DHCP database recovery, and Exchange Online delivery diagnostics only where those subjects appear in your confirmed AT-510 outline.
What can be confirmed about AT-510 before you study
No official AT-510 exam specification is present in the supplied research. The available sources are IBM Fix Central, Microsoft Intune endpoint guidance, Microsoft Sysinternals documentation, a Microsoft Q&A discussion about DHCP JET error -510, and Microsoft Exchange Online NDR guidance. None of those pages names AT-510 or establishes that these topics are exam objectives.
Treat the exam code as an identifier requiring confirmation, not as proof of a vendor, certification family, role, or technology scope. Do not rely on an unofficial page that supplies a title, question count, duration, passing score, language list, price, prerequisite, or retirement date unless the certification owner confirms it.
The practical decision is whether to proceed with exam-specific preparation now or pause for authoritative identification. If your registration portal, candidate agreement, or official certification page provides an objective list, preserve that document and compare every study topic against it. If it does not, ask the issuing organization to confirm the exam’s owner and current blueprint before committing money or a test appointment.
Information that still needs official confirmation
The research does not verify AT-510’s purpose, intended candidate, measured skills, domain weights, prerequisites, delivery method, testing location, remote-proctoring rules, appointment process, exam fee, duration, question count, score requirements, languages, retake policy, or status. These are official requirements when published by the owner; they cannot be inferred from the technical subjects in the supplied pages.
Do not convert this absence into a claim that the exam has no prerequisites or that it is available in a particular format. Record each unknown in a preparation checklist and resolve it through the exam owner’s current page or support channel.
How to use this guide responsibly
Use the technical material below as a conditional practice framework. It is appropriate if your verified AT-510 outline includes Microsoft Intune networking, Windows troubleshooting tools, DHCP recovery, or Exchange Online mail-flow diagnostics. If the official outline names different technologies, replace these modules rather than forcing an apparent match.
How to turn the verified outline into a study map
Once you obtain the official objective list, make it the control document for preparation. Copy each objective into a table, add the evidence source or lab that will teach it, and mark whether you can explain, perform, troubleshoot, or document the task. Because no AT-510 blueprint weights were supplied, do not assign percentages or rank domains by unsupported importance.
Separate knowledge statements from operational tasks. A candidate may recognize an SMTP status code yet still be unable to identify whether the sending system, recipient organization, DNS, authentication, or network path is responsible. Your study map should test both recognition and diagnostic judgment.
Use a four-column tracker: objective, evidence, hands-on exercise, and review result. A review result should say what failed and why, not merely ‘read’ or ‘watched.’ This prevents a large collection of notes from being mistaken for exam readiness.
A useful objective-to-practice method
For each confirmed objective, write one answer in plain language, one command or administrative action if applicable, one expected result, and one failure interpretation. Then create a small scenario that changes one variable at a time. This is a practical recommendation, not an official AT-510 requirement.
For example, an endpoint objective might require you to identify the destination, port, proxy behavior, certificate requirement, or inspection constraint. Your exercise should therefore capture the endpoint name, connection attempt, observed failure, and corrective change. A definition-only flashcard will not test that reasoning.
How to handle missing domain weights
If the owner later publishes domain percentages, write the associated exam domain in the same sentence as each percentage in your plan. For example, use the owner’s exact label and percentage together, rather than creating a list of unlabeled numbers. Until those facts are available, allocate study time according to your baseline knowledge, confirmed objective difficulty, and observed practice errors.
Endpoint connectivity: study the configuration decision, not just the URL
Microsoft’s Intune guidance says the consolidated endpoint list should be used because older PowerShell scripts for retrieving Intune endpoint IP addresses and FQDNs no longer return accurate data from the Office 365 Endpoint service. If endpoint administration is confirmed in your AT-510 outline, learn how to identify the correct endpoint set, ports, tenant location, proxy behavior, and inspection constraints from the current Microsoft documentation.
The Intune page describes endpoint categories such as Optimize, Allow, and Default, and explains that the tables associate endpoint sets with addresses and ports. It also states that managed devices behind firewalls and proxy servers need communication enabled for Intune, while SSL traffic inspection is not supported for certain listed service endpoints.
A good exercise is to begin with a failed device action and work outward: confirm tenant location, resolve the FQDN, test outbound connectivity, inspect proxy treatment, verify certificate handling, and compare the result with the current consolidated list. Do not memorize a static endpoint list as if it were permanent.
What to practise in an Intune network scenario
Build a worksheet that records the service being tested, the FQDN or wildcard, TCP or UDP port, firewall result, proxy result, and whether SSL inspection is involved. The official page explains that the connector has the same network requirements as managed devices, so include connector traffic when your scenario involves the Microsoft Intune Certificate Connector.
The page identifies TCP ports 80 and 443 for particular endpoint entries and separately describes other endpoint-specific requirements. Reproduce the port attached to the exact endpoint in your source rather than applying one port universally. Keep the endpoint list current at the time you study.
Tools and test sequencing
The Microsoft page describes a connectivity diagnostic that checks DNS resolution, outbound TCP connectivity on ports 80 and 443 to Azure Front Door IP addresses, and HTTPS validation to the Intune cloud service. It lists PowerShell 5.1 or later as a prerequisite for running the script. If this appears in your confirmed objectives, practise interpreting each check separately instead of treating a failed overall result as one undifferentiated problem.
The documented execution options include running Test-IntuneAFDConnectivity.ps1 as the current user or running it in device context with PsExec from Microsoft Sysinternals. The exact command shown for the current-user option is .\Test-IntuneAFDConnectivity.ps1. Use the official page for the current script and prerequisites before reproducing the exercise.
Regional and platform constraints
The research notes that devices in China managed by Intune cannot use features requiring Google Mobile Services because Google Mobile Services is not available there. It also notes that some tasks can require up to 8 hours to finish. Treat these as scenario-specific operational constraints from the Intune source, not as universal timing or behavior for every device or exam task.
Windows troubleshooting utilities: learn tool selection and evidence handling
The Sysinternals Suite bundles individual troubleshooting tools and their help files. The supplied Microsoft page lists utilities including Process Explorer, Process Monitor, PsExec, PsPing, TCPView, Autoruns, Handle, ProcDump, RAMMap, Sigcheck, Sysmon, and VMMap. If AT-510 includes Windows troubleshooting, prepare by choosing a tool for a stated diagnostic question rather than memorizing the entire catalogue.
Map the question to the evidence: process relationships and loaded components, file or registry activity, network connections, persistence, memory pressure, authentication context, or system events. Then record the observation, timestamp, affected process or endpoint, and next test. This approach is a practical recommendation based on the tools’ published names and troubleshooting purpose; it is not evidence of the AT-510 blueprint.
Download the current suite from the official Microsoft page and read the help for only the utilities relevant to your confirmed objectives. Avoid treating a tool’s presence in the suite as proof that the exam tests it.
A focused Sysinternals lab sequence
Start with a harmless, reproducible Windows problem in a test environment. Observe the process tree, capture the relevant file or registry activity, inspect active connections, and compare the evidence before and after a controlled change. Use PsExec only when you specifically need to understand device-context execution and have authorization to do so.
Your notes should explain why one tool was selected and what alternative evidence would change the diagnosis. A screenshot without interpretation is weak revision material. Preserve command syntax, privilege context, filtering choices, and the conclusion separately.
Common troubleshooting mistakes
Do not launch every utility at once, collect unfiltered output indefinitely, or change several variables before recording a baseline. Those habits make causality difficult to establish. Do not infer that a process is malicious solely because its name is unfamiliar; validate path, signature, parent process, behavior, and surrounding evidence in the lab.
DHCP JET error -510: practise safe recovery reasoning
The Microsoft Q&A research describes JET error -510 as a low-level Extensible Storage Engine corruption event in the discussion’s answer. It attributes the reported DHCP startup failure to a corrupted transaction log, specifically j50.log, and describes a recovery sequence that preserves backups before repair. If DHCP recovery is part of your confirmed AT-510 scope, study the order of operations and the risk controls rather than memorizing a destructive shortcut.
The documented sequence is to stop the DHCP Server service, back up dhcp.mdb, dhcp.tmp, and all j50*.log files under %SystemRoot%\System32\dhcp, remove the corrupted log files, run jetpack dhcp.mdb tmp.mdb from an elevated command prompt, and restart the service. The answer also describes restoring from the built-in backup location if repair fails.
Because this source is a Microsoft Q&A answer rather than an AT-510 exam blueprint, use it as technical reference material only. Validate recovery procedures against the current Microsoft support guidance and your organization’s change-control policy before using them on production data.
What a recovery worksheet should contain
Record the service state, database and log paths, backup location, backup validation, command executed, repair result, restored scope configuration, and post-restart checks. Include a decision point for failure: if jetpack cannot repair the database, the researched answer directs the administrator toward a valid DHCP backup rather than repeated experimentation on the original files.
Practise explaining why a backup comes first. DHCP scope configuration and lease history are operationally important, so a recovery plan must distinguish preservation, repair, restoration, and validation. That reasoning is more transferable than recalling a single filename.
Preventive controls to review
The supplied answer recommends regular DHCP database backups using the built-in DHCP console option or netsh dhcp server export, together with disk-health checks and suitable antivirus exclusions. Treat these as recommendations from the cited discussion, not as verified AT-510 requirements. Add them to your study notes only if the confirmed outline covers maintenance or recovery planning.
Exchange Online NDRs: build a classification and escalation habit
Microsoft describes a nondelivery report as a delivery status notification generated when a message cannot reach its intended recipient. The report normally includes an error code, a reason, possible solutions, further help, and administrator-oriented technical details. If Exchange Online mail flow is in scope, learn to classify the failure before choosing a fix.
Begin with the enhanced status code and the diagnostic text, then identify the generating server, sender, recipient, and whether the failure is temporary or permanent. Microsoft explains that a 5.x.x code indicates a permanent error and a 4.x.x code indicates a temporary error. That classification guides whether to correct configuration, retry, investigate throttling, or contact the receiving organization.
The NDR page cautions that the Microsoft 365 or Office 365 logo does not necessarily mean Microsoft 365 caused the error. Practise locating the server that rejected the message and separating a sender-side configuration problem from a remote-server or recipient-domain problem.
Authentication and identity failures
Create a table that groups authentication failures by mechanism and identity. The research includes 5.7.1 Client was not authenticated, 5.7.57 Client was not authenticated to send anonymous mail during MAIL FROM, and XOAUTH2 authentication failures including 535 5.7.142, 535 5.7.143, and 535 5.7.144. It also states that an expired OAuth access token can be rejected.
Do not treat every authentication code as an instruction to reset a password. Check whether the scenario involves SMTP relay, OAuth, an application or device, a connector, or a recipient that rejects unauthenticated external mail. The correct next action depends on that distinction.
Address, relay, and policy failures
Practise reading the exact error text. The supplied evidence includes 5.1.10 Recipient not found, 5.4.1 Recipient address rejected: Access denied, 5.4.1 Relay Access Denied, 5.7.1 Unable to relay, 5.7.124 Sender not in allowed-senders list, and 5.7.134 Sender was not authenticated for mailbox. These codes can look similar while pointing to different ownership and configuration checks.
The research also states that domains used to send mail from Microsoft 365 or Office 365 should be added and validated. Include domain validation, recipient existence, allowed-sender settings, and relay authorization in separate branches of your diagnostic tree.
DNS, TLS, and certificate failures
Build a transport-security branch for SPF, DKIM, DMARC, MTA-STS, DANE, certificates, and TLS. The supplied evidence includes a sender domain that fails DMARC, 5.7.23 for an SPF violation, 5.7.321 starttls-not-supported, certificate-expired errors, certificate-host-mismatch errors, tlsa-invalid errors, and MTA-STS validation failures.
The useful preparation decision is to identify who controls the failed dependency. A destination certificate, MX host, DNS record, or remote TLS capability may require action by the receiving organization rather than by the Microsoft 365 administrator. The NDR’s server and diagnostic details should determine the escalation path.
Throttling, loops, and recipient limits
The Exchange research describes several limit and loop conditions. External recipient rate limits are tracked over a 24-hour rolling window; the supplied evidence states that messages from onmicrosoft.com domains are limited to 100 external recipients for a rolling 24-hour period, and one error describes an organization exceeding 100 external recipients within a 24-hour rolling window. Keep each limit attached to its exact scenario instead of generalizing it to all sending accounts.
The source also states that Exchange interrupts an email loop after 20 iterations and generates an NDR. Other examples include too many recipients, recipient mailbox receive throttling, concurrent authenticated connections, and message or submission quotas. Practise distinguishing a retryable service or recipient condition from a policy or configuration failure.
Administrator diagnostics
The Microsoft page says that running nondelivery report diagnostics requires a Microsoft 365 administrator account. It also describes a diagnostic launch from the Microsoft 365 admin center. If administrator workflows are included in your confirmed objectives, practise deciding when to use NDR details, message trace, service diagnostics, or external-domain escalation rather than assuming every issue can be fixed from the sender mailbox.
A practical study roadmap without unsupported exam promises
Use a staged plan that begins with scope verification, then builds technical foundations, then tests diagnostic decisions. The schedule should be driven by your confirmed AT-510 objectives and available study time, not by an invented exam duration or question count. Each stage should end with evidence that you can perform or explain the objective independently.
The roadmap below is a practical recommendation. It is not an official AT-510 schedule, and it does not predict a passing result. Shorten or extend each stage according to the gaps revealed by your objective tracker.
Stage one: establish the exam boundary
Obtain the current official exam page, candidate agreement, registration information, and objective list from the issuing organization. Confirm the exam title, vendor, audience, measured skills, prerequisites, delivery method, score policy, languages, and availability. Save the page or document version used for planning because technical products and exam policies can change.
Next action: create two lists. The first contains verified requirements. The second contains claims found elsewhere that still need confirmation. Do not purchase a course or schedule a sitting based only on the code AT-510.
Stage two: assess your baseline
For every confirmed objective, rate yourself as unfamiliar, familiar, able to explain, or able to perform and troubleshoot. Validate the rating with a small task, not confidence alone. For endpoint topics, test connectivity interpretation; for Windows tools, select and use the right evidence source; for DHCP, explain a safe recovery sequence; for Exchange, classify NDR ownership and next action.
Next action: choose the two weakest confirmed areas for the first lab cycle. If none of the supplied technical subjects appears in the official outline, remove them from the plan and substitute the actual objectives.
Stage three: learn in dependency order
Study fundamentals before exception handling. For Intune, understand endpoint categories, FQDNs, ports, proxy access, tenant location, and inspection restrictions before troubleshooting a failed device action. For Windows tools, learn process, file, registry, network, and execution-context evidence before interpreting complex incidents. For Exchange, learn status-code classes and NDR structure before memorizing individual codes.
Next action: write a one-page decision tree for each technical domain. Every branch should end in an observation, a corrective action, or a justified escalation.
Stage four: practise controlled scenarios
Run one-variable exercises in an authorized lab. Capture the baseline, make a deliberate change, observe the failure, reverse or correct it, and document the result. For DHCP recovery, practise backup-first reasoning. For Exchange, classify the code and identify the responsible system. For Intune, test DNS, TCP, HTTPS, proxy, and inspection conditions separately where the environment permits.
Next action: review every scenario you solved by guesswork. Rebuild it until you can state the evidence that supports the conclusion.
Stage five: close gaps and decide whether to schedule
Schedule only after the official requirements are confirmed and your practice record shows repeatable performance across the tested objectives. Use the owner’s current registration and delivery instructions for the final appointment decision. Do not use an unofficial passing claim, memorized dump, or leaked-question collection as readiness evidence.
Next action: perform a final objective-by-objective review, mark unresolved topics, verify the current exam information again, and prepare an escalation list for any requirement the owner has not clearly published.
Mistakes that waste preparation time
The most expensive errors are scope errors: studying a technology because it appears in a search result, treating a page about a product as an exam blueprint, and trusting stale endpoint or policy information. The supplied sources support technical learning, but they do not establish AT-510’s domains or weighting. Keep that distinction visible in your notes.
A second problem is passive study. Reading error-code tables without classifying ownership, or downloading utilities without using them against a controlled problem, produces recognition without judgment. A third is unsafe administration: deleting database files or changing firewall rules without preserving evidence and obtaining authorization.
Avoid unsupported precision
Do not publish or plan around an unverified question count, test duration, passing score, fee, language, prerequisite, delivery method, or retirement date. If an official source later supplies one of these facts, reproduce it with its exact subject and unit. Until then, describe the information as unconfirmed and direct the reader to the exam owner.
Avoid confusing source authority
A Microsoft product page can document product behavior without defining an exam objective. A Q&A answer can offer a recovery path without being a certification requirement. IBM Fix Central explains how to find fixes and updates for IBM products, but the supplied page does not connect Fix Central to AT-510. Use each source for what it actually establishes.
Avoid memorization as a substitute for diagnosis
Memorize stable concepts such as the distinction between temporary and permanent SMTP status-code classes, but practise applying them to evidence. Do not assume that memorizing NDR codes, endpoint names, or tool names guarantees success. Technical examinations generally reward the decision supported by the scenario; this guide cannot claim how AT-510 scores any particular response because its scoring rules were not supplied.
Your next actions and source check
Before studying further, verify AT-510 with the certification owner and obtain its current objective list. Then keep only the conditional modules that match that list, build a baseline assessment, and schedule practice around observed weaknesses. The official pages below are useful technical references, but none of the supplied evidence confirms the exam’s identity or blueprint.
Use the Intune endpoint page for current network requirements rather than obsolete endpoint scripts, the Sysinternals page for the suite and tool documentation, the Exchange NDR page for status-code interpretation, the DHCP Q&A page as a cautiously qualified recovery reference, and IBM Fix Central only when your confirmed objective concerns IBM fix discovery. Recheck the owner’s exam page immediately before registration because this research snapshot does not verify time-sensitive exam details.
Official technical references supplied for this guide
Microsoft Intune network endpoints: https://learn.microsoft.com/en-us/intune/fundamentals/endpoints
Microsoft Sysinternals Suite: https://learn.microsoft.com/en-us/sysinternals/downloads/sysinternals-suite
Exchange Online NDRs and SMTP errors: https://learn.microsoft.com/en-us/troubleshoot/exchange/email-delivery/ndr/non-delivery-reports-in-exchange-online
Microsoft Q&A discussion on DHCP JET error -510: https://learn.microsoft.com/en-us/answers/questions/5966848/clean-recovery-from-dhcp-jet-error-510
IBM Fix Central: https://www.ibm.com/support/fixcentral/?lnk=fpl-fcen
Conclusion
The responsible AT-510 decision is verification first, specialization second. The supplied official research supports useful preparation around Intune endpoints, Sysinternals troubleshooting, DHCP database recovery, Exchange Online NDR analysis, and IBM fix discovery, but it does not prove that AT-510 examines any of them. Confirm the owner, objectives, requirements, and delivery details; map each verified objective to a lab or diagnostic exercise; measure performance with evidence; and use only current official registration information when deciding whether and when to schedule.
