The answer is a custom log schema mismatch between the table definition in your Log Analytics workspace and the incoming log format. When data connectors show as healthy but logs are still missing, the ingestion pipeline silently drops records because the Log Analytics agent or Azure Monitor Agent cannot parse data that doesn’t match the expected columns, data types, or delimiters. On the SC-200 exam, this scenario tests your understanding of how custom log ingestion works—specifically that schema validation occurs before any data is written, and failures are not reported as connector errors. A common trap is assuming a healthy connector guarantees log delivery, but the real issue is often a forgotten field or incorrect delimiter in the custom log table. Remember the mnemonic: “Schema first, logs last”—if the schema doesn’t fit, the logs won’t stick.
SC-200 Manage a security operations environment Practice Question
This SC-200 practice question tests your understanding of manage a security operations environment. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Your Microsoft Sentinel workspace ingests logs from multiple sources but you notice that some custom logs are missing in the Log Analytics workspace. You've confirmed that the data connectors are healthy. What is the most likely cause?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The custom log table schema does not match the incoming log format.
When data connectors are healthy but custom logs are missing, the most common cause is a schema mismatch between the custom log table definition in the Log Analytics workspace and the actual log data being sent. Microsoft Sentinel requires the custom log table's schema (columns, data types, and delimiters) to exactly match the incoming log format; otherwise, the ingestion pipeline drops the records without error. This is because the Log Analytics agent or AMA uses the table schema to parse and transform the data, and any deviation results in silent failures.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✓
The custom log table schema does not match the incoming log format.
Why this is correct
Mismatch causes logs to be dropped.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
There is a time gap between log generation and ingestion.
Why it's wrong here
Delays don't cause missing logs; they show up later.
✗
The workspace has exceeded its daily ingestion limit.
Why it's wrong here
This would affect all logs, not just custom ones.
✗
The data connectors are not properly configured for custom log ingestion.
Why it's wrong here
They are healthy, so configuration should be correct.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates assume a healthy data connector guarantees all logs are ingested, but Microsoft tests the nuance that schema mismatches cause silent ingestion failures even when the connector itself is operational.
Trap categories for this question
Command / output trap
Delays don't cause missing logs; they show up later.
Detailed technical explanation
How to think about this question
Under the hood, custom log ingestion uses a transformation pipeline where the Log Analytics agent or Azure Monitor Agent reads the log file, applies a delimiter (e.g., comma, tab, or newline) based on the table schema, and maps fields to columns. If the schema defines three columns but the log file contains four fields, or if a date field expects ISO 8601 format but receives epoch time, the entire record is discarded. In real-world scenarios, this often happens when log sources update their format (e.g., adding a new field) without updating the custom log table schema in the workspace.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this SC-200 question in full detail.
Manage a security operations environment — This question tests Manage a security operations environment — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The custom log table schema does not match the incoming log format. — When data connectors are healthy but custom logs are missing, the most common cause is a schema mismatch between the custom log table definition in the Log Analytics workspace and the actual log data being sent. Microsoft Sentinel requires the custom log table's schema (columns, data types, and delimiters) to exactly match the incoming log format; otherwise, the ingestion pipeline drops the records without error. This is because the Log Analytics agent or AMA uses the table schema to parse and transform the data, and any deviation results in silent failures.
What should I do if I get this SC-200 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This SC-200 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SC-200 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.