Defender for Endpoint File Hash Indicators: PE Files Only
Short answer
A Only File1.sys is a portable executable (PE) file, so Defender for Endpoint file-hash indicators can block it, while File2.pdf, File3.docx, and File4.xlsx cannot be blocked with indicator hashes.
Question
As part of an incident investigation, you identify the following suspected malware files:
• sys
• docx
• xlsx
You need to create indicator hashes to block users from downloading the files to the devices.
Which files can you block by using the indicator hashes?
Key Takeaways
The exam tests whether you know file-hash indicators in Defender for Endpoint are limited to PE files; the trap is assuming any hashed document can be blocked.
This SC-200 question tests the scope of Microsoft Defender for Endpoint file indicator hashes. Only File1.sys is a supported portable executable, so the answer is A.
Common mistake: Choosing E because hashes are extension-agnostic; a hash exists for every file, but MDE file indicators only enforce on PE files, so PDF, DOCX, and XLSX cannot be blocked this way.
Expert Analysis
The boundary is PE versus non-PE
The scenario asks you to create indicator hashes in Microsoft Defender for Endpoint, not to use every possible incident-response action. Microsoft's file-indicator documentation limits custom file indicators to portable executable (PE) files. Among the listed files, File1.sys is the only PE-format file; File2.pdf, File3.docx, and File4.xlsx are non-PE documents. That makes A correct, not E.
Why the hash-agnostic argument fails
A recurring argument is that a SHA-1 or SHA-256 hash is filename- and extension-agnostic, so any file could match. The hash value itself is indeed independent of the name, but Defender for Endpoint's file-indicator feature is scoped to supported PE file types. The extension is not the matching key; it determines whether this indicator type can be enforced at all. Community notes point back to Microsoft's "indicator-file" documentation and note that file indicators support PE files such as.exe and.dll, while another note cites broader "block and remediate" behavior. The question's wording, "create indicator hashes," keeps us in the custom-indicator workflow, so the PE limitation controls.
Do not blend in response actions
Defender's incident response actions can act on files observed during investigation, which can feel broader than a preconfigured hash indicator. Here, the requirement is specifically to block downloads by creating indicator hashes. Only File1.sys qualifies from the supplied list; PDF, DOCX, and XLSX require a different control. Therefore, the answer is A.
Official Reference
https://learn.microsoft.com/en-us/defender-endpoint/indicator-file
This link opens the official vendor documentation in a new tab.
Exam Strategy
When a question asks what Defender for Endpoint file indicators can block, classify each extension first: treat .exe, .dll, .sys, and other PE formats as supported, and treat .pdf, .docx, and .xlsx as unsupported. Ignore hash-agnostic reasoning unless the question asks about a response action rather than a custom indicator. Then select the option that includes only PE files.
Frequently Asked Questions
Can Microsoft Defender for Endpoint block a PDF or Office file by using a file-hash indicator?
Why is File1.sys blockable when the documentation examples mention .exe and .dll?
Does 'Block and remediate' allow blocking any file hash?
Community Votes
47% of anonymous learners picked answer E. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 26 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 26
-
liveup2it 👍 21 Answered EBased on File hashes, you should be able to block each and every file with this hash, regardless the name of the file.
-
Hawklx 👍 10 Answered AThis feature is designed to prevent suspected malware (or potentially malicious files) from being downloaded from the web. It currently supports portable executable (PE) files, including .exe and .dll files. Ref: https://learn.microsoft.com/en-us/defender-endpoint/indicator-file
-
g_man_rap 👍 6 Answered AKey Points: Executable Files: Microsoft Defender for Endpoint can block executable files such as .exe, .dll, .sys, and other similar types. Non-Executable Files: Generally, Microsoft Defender for Endpoint does not allow blocking of non-executable files (e.g., .pdf, .docx, .xlsx) by file hash using the same indicator mechanism designed for executables.
-
Feredi 👍 5 Answered AAccording to Microsoft Defender for Endpoint documentation, you can block files based on hash only if they are executable. This typically includes: .exe, .dll, .sys, .msi, .scr, .drv, .com
-
phoenix5 👍 3Answer - C (.sys , .docx, .xlsx as per this explanation by Copilot - You can create indicator hashes to block executable files with the following extensions: .exe, .dll, and .sys. Additionally, Office files like .docx and .xlsx can also be blocked using indicator hashes. However, PDF files cannot be blocked using indicator hashes in Microsoft Defender for Endpoint1.
Show 21 more comments
-
1375514 👍 3 Answered Ahttps://learn.microsoft.com/en-us/defender-endpoint/indicator-file From Microsoft: "File indicators support portable executable (PE) files, including .exe and .dll files only." Only the .sys is a PE file, therefore it is the only file that can be blocked via file indicator.
-
Syncure 👍 3Portable Executable(PE) include: .exe .dll .sys .ocx .cpl .scr The answer es A at the moment, I don't see Office 365 files supports in the MD for Endpoint V2 in this feature
-
Tuitor01 👍 2I second this...adding though that M$ doesn't recommend using hash based IOC since they can change in a blink of an eye but use App control instead (side note), so Answer E, undoubtedly since a hash is file name and extension agnostic.
-
Krayzr 👍 2However, given this straight forward link. It should be A: https://learn.microsoft.com/en-us/defender-endpoint/indicator-file#windows-prerequisites
-
b9cf0e5 👍 2Answer is D: Blocking .sys files could affect system functionality, and thus Defender for Endpoint does not allow blocking system-critical files.
-
4420964 👍 2 Answered CHash blocking works only for executables and macro-based documents. So the answer is C
-
talosDevbot 👍 2 Answered AFile indicators only support Portable Execution (PE) files like exe, dll, sys
-
RonWonkers 👍 2 Answered EYou make get a hash for every file and block it.
-
KAMOMILED 👍 2 Answered E13 Sep 2025 TEST
-
Krayzr 👍 1Are There Limitations? Could there be restrictions based on file type or extension? In some security contexts, blocking might focus on execution (e.g., for .exe or .sys) rather than file access. However, Microsoft Defender for Endpoint’s "Block and remediate" action is designed to prevent file operations broadly—reading, writing, or executing—based on hash matches. Documentation and practical use cases confirm that this applies to all file types, including documents like .pdf, .docx, and .xlsx, not just executables. There’s no indication in Plan 2 that certain file extensions are excluded from hash-based blocking.
-
neogeek87 👍 1 Answered EA file indicator is based on the file’s SHA-1 or SHA-256 hash, not the filename extension. Therefore, Defender can block each specific file represented by a valid hash, including .sys, .pdf, .docx, and .xlsx. Correct answer E. File1.sys, File2.pdf, File3.docx, and File4.xlsx The “portable executable” wording in Microsoft’s documentation describes a common scenario, but it should not have been used to exclude document files from hash-based blocking. Create indicators for files documents creating file indicators using file hashes.
-
The1BelowAll 👍 1 Answered BMicrosoft Defender for Endpoint Plan 2 supports blocking executable files like: .exe .dll .sys (driver files) It also supports blocking Office files like: .docx .xlsx
-
Avaris 👍 1 Answered EI am gonna go with a whim and select E for one reason, I remember blocking all types of files including pdfs we block with hashes I think
-
QzLP2P 👍 1 Answered CYou cannot block pdf https://learn.microsoft.com/en-us/defender-endpoint/indicator-ip-domain?view=o365-worldwide#limitations
-
Rodwhite 👍 1 Answered EI took the hash from (.pdf, sys, doc,) and each file and was able to upload successfully. Therefore, the answer is E.
-
rvln7 👍 1 Answered AMicrosoft Defender for Endpoint indicator hashes can only block executable files. .exe .dll .sys .scr
-
shdwktn 👍 1by this logic and the link you provided. .sys files are not even stated. Maybe I misunderstood
-
Krayzr 👍 1https://learn.microsoft.com/en-us/defender-endpoint/indicator-file#windows-prerequisites
-
arturro007 👍 1 Answered EQuestion is about hashes. You can add any hash to Defender and it will be blocked.
-
smanzana 👍 1E https://learn.microsoft.com/en-us/defender-endpoint/indicator-file
-
ada26b1 👍 1 Answered ESurely you can block all of them
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All SC-200 Questions
Access 80 questions with complete answers and detailed explanations.
View Full SC-200 Practice Test →