The answer is to use a single Log Analytics workspace for all subscriptions and configure Microsoft Sentinel in that workspace. This approach centralizes incident management in Sentinel across multiple subscriptions by funneling all security data into one location, which allows the security operations center to view and manage every incident from a unified console without needing to switch between workspaces. Crucially, Microsoft Sentinel does not charge for cross-workspace queries performed within the same region, so you minimize data egress costs while maintaining full visibility. On the Microsoft Cybersecurity Architect exam, this scenario tests your understanding of workspace architecture trade-offs—specifically, the balance between data residency requirements and operational efficiency. A common trap is choosing separate workspaces per region to reduce egress, but that fragments incident management; another is suggesting Azure Monitor cross-workspace queries, which are for analysis, not centralization. Memory tip: think “one workspace to rule them all” for centralized incident handling, and remember that Sentinel’s regional cross-workspace queries are free, so egress is not a concern within the same geography.
SC-100 Practice Question: Design security operations, identity, and compliance capabilities
This SC-100 practice question tests your understanding of design security operations, identity, and compliance capabilities. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. 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.
You are designing a security operations solution for a multinational organization using Microsoft Sentinel. The organization has multiple Azure subscriptions, each with its own Log Analytics workspace. You need to centralize incident management while minimizing data egress costs. What should you recommend?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use a single Log Analytics workspace for all subscriptions and configure Sentinel in that workspace.
Option C is correct because using a single workspace for all subscriptions centralizes data and incidents, and Microsoft Sentinel does not charge for cross-workspace querying within the same region. Option A is wrong because separate workspaces per region would not centralize incidents. Option B is wrong because a third-party SIEM adds complexity and cost. Option D is wrong because Azure Monitor cross-workspace queries are for analysis, not incident centralization.
Key principle: NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Deploy a Sentinel workspace in each region and use cross-workspace views.
Why it's wrong here
This does not centralize incident management.
✗
Export all logs to a third-party SIEM using Azure Event Hubs.
Why it's wrong here
This adds cost and complexity.
✗
Configure Azure Monitor cross-workspace queries to correlate incidents.
Why it's wrong here
Cross-workspace queries are for analysis, not incident management centralization.
✓
Use a single Log Analytics workspace for all subscriptions and configure Sentinel in that workspace.
Why this is correct
Centralizes incidents and avoids egress costs within the same region.
Related concept
Static NAT maps one inside address to one outside address.
Common exam traps
Common exam trap: NAT rules depend on direction and matching traffic
NAT is not only about the public address. The inside/outside interface roles and the ACL or rule that matches traffic are just as important.
Detailed technical explanation
How to think about this question
NAT questions usually test address translation, overload/PAT behaviour, static mappings and whether the right traffic is being translated. Read the interface direction and address terms carefully.
KKey Concepts to Remember
Static NAT maps one inside address to one outside address.
PAT allows many inside hosts to share one public address using ports.
Inside local and inside global describe the private and translated addresses.
NAT ACLs identify traffic for translation, not always security filtering.
TExam Day Tips
→Identify inside and outside interfaces first.
→Check whether the scenario needs static NAT, dynamic NAT or PAT.
→Do not confuse NAT matching ACLs with normal packet-filtering intent.
Key takeaway
NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.
Real-world example
How this comes up in practice
A startup's cloud architect reviews their monthly bill and notices costs are higher than expected for a long-running batch job. Switching from on-demand instances to Reserved Instances — or using Spot/Preemptible VMs — can reduce compute costs by up to 72 %. Questions like this test whether you understand the tradeoffs between commitment, flexibility, and cost across cloud pricing models.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this SC-100 question in full detail.
Review the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related SC-100 NAT questions on configuration and troubleshooting.
Design security operations, identity, and compliance capabilities — This question tests Design security operations, identity, and compliance capabilities — Static NAT maps one inside address to one outside address..
What is the correct answer to this question?
The correct answer is: Use a single Log Analytics workspace for all subscriptions and configure Sentinel in that workspace. — Option C is correct because using a single workspace for all subscriptions centralizes data and incidents, and Microsoft Sentinel does not charge for cross-workspace querying within the same region. Option A is wrong because separate workspaces per region would not centralize incidents. Option B is wrong because a third-party SIEM adds complexity and cost. Option D is wrong because Azure Monitor cross-workspace queries are for analysis, not incident centralization.
What should I do if I get this SC-100 question wrong?
Review the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related SC-100 NAT questions on configuration and troubleshooting.
What is the key concept behind this question?
Static NAT maps one inside address to one outside address.
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-100 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-100 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.