You save $69.98
SC-200 Premium Bundle
- Premium File 499 Questions & Answers
- Last Update: Nov 17, 2026
- Training Course 47 Lectures
- Study Guide 441 Pages
You save $69.98
A cloud incident names an abused service principal and several associated Azure resources in different subscriptions. The selected response is to trace credential usage, role grants, and workload operations into one cross-resource investigative graph. Which technical mechanism BEST explains its effectiveness?
Cross-domain threat investigation relates cloud identities and resources through authenticated actions. The change is Trace credential usage, role grants, and workload operations into one cross-resource investigative graph. Verify that a controlled test principal's operations resolve to the correct subscription and resource scopes.
High-confidence cross-domain attack correlation can trigger identity or device containment during active campaigns. The active incident mechanism is cross-domain threat investigation relates cloud identities and resources through authenticated actions.
Container-aware workload protection can correlate runtime signals to deployed workload objects. The active incident mechanism is cross-domain threat investigation relates cloud identities and resources through authenticated actions.
Cloud app governance links OAuth permissions and observed API activity to potential data exposure. The active incident mechanism is cross-domain threat investigation relates cloud identities and resources through authenticated actions.
The security team performs this response: Trace credential usage, role grants, and workload operations into one cross-resource investigative graph The original issue: a cloud incident names an abused service principal and several associated Azure resources in different subscriptions. Which observation BEST validates the intended outcome?
A controlled test principal's operations resolve to the correct subscription and resource scopes. Cross-domain threat investigation relates cloud identities and resources through authenticated actions.
The affected VM and timeline are confirmed and a safe isolation or patch action is documented. The expected evidence here is A controlled test principal's operations resolve to the correct subscription and resource scopes.
Incident evidence shows an eligible test entity was contained while the phishing message was remediated. The expected evidence here is A controlled test principal's operations resolve to the correct subscription and resource scopes.
The test investigation identifies the consenting account and download activity preceding revocation. The expected evidence here is A controlled test principal's operations resolve to the correct subscription and resource scopes.
A cloud incident names an abused service principal and several associated Azure resources in different subscriptions. The team has decided to trace credential usage, role grants, and workload operations into one cross-resource investigative graph. Which case-specific residual limitation MOST needs attention?
Disabling an identity without mapping legitimate application dependencies can cause widespread outages. Cross-domain threat investigation relates cloud identities and resources through authenticated actions.
Revoking a shared production secret can break business systems if dependencies are not identified. The outstanding risk here is disabling an identity without mapping legitimate application dependencies can cause widespread outages.
Unexpected geography alone is insufficient to prove malicious access or data theft. The outstanding risk here is disabling an identity without mapping legitimate application dependencies can cause widespread outages.
Automatic disruption does not replace investigating mailbox rules and already issued sessions. The outstanding risk here is disabling an identity without mapping legitimate application dependencies can cause widespread outages.
An analyst believes a single endpoint alert proves ransomware spread across the tenant. The required acceptance result is: A simulated source device and two targets appear only when corresponding evidence exists. Which response MOST DIRECTLY addresses the stated security-operations requirement?
Corroborate propagation with separate identity, process, and network observations before expanding impact. Blast radius must be derived from observed affected entities rather than assumed from severity labels. Confirm that a simulated source device and two targets appear only when corresponding evidence exists. Overstating blast radius can trigger unnecessary isolation of unrelated business assets.
Alert grouping depends on mapped entities, rule behavior, and cross-source correlation logic.
An alert's recommended remediation and the actual cloud resource state are separate facts.
Identity alert coverage depends on functioning sensors and appropriate directory telemetry collection.
An analyst believes a single endpoint alert proves ransomware spread across the tenant. The selected response is to corroborate propagation with separate identity, process, and network observations before expanding impact. Which technical mechanism BEST explains its effectiveness?
Blast radius must be derived from observed affected entities rather than assumed from severity labels. The change is Corroborate propagation with separate identity, process, and network observations before expanding impact. Verify that a simulated source device and two targets appear only when corresponding evidence exists.
Defender for Cloud workload detections connect cloud resource identities with observed suspicious behaviors. The active incident mechanism is blast radius must be derived from observed affected entities rather than assumed from severity labels.
Multi-source correlation distinguishes recorded file movement from assumptions based on labels alone. The active incident mechanism is blast radius must be derived from observed affected entities rather than assumed from severity labels.
Defender for Identity correlates directory authentication signals that may indicate credential replay or theft. The active incident mechanism is blast radius must be derived from observed affected entities rather than assumed from severity labels.
The security team performs this response: Corroborate propagation with separate identity, process, and network observations before expanding impact The original issue: an analyst believes a single endpoint alert proves ransomware spread across the tenant. Which observation BEST validates the intended outcome?
A simulated source device and two targets appear only when corresponding evidence exists. Blast radius must be derived from observed affected entities rather than assumed from severity labels.
A controlled directory security event generates expected visibility after sensor repair. The expected evidence here is A simulated source device and two targets appear only when corresponding evidence exists.
The case corrects the Copilot claim when source event details contradict the generated summary. The expected evidence here is A simulated source device and two targets appear only when corresponding evidence exists.
The affected VM and timeline are confirmed and a safe isolation or patch action is documented. The expected evidence here is A simulated source device and two targets appear only when corresponding evidence exists.
An analyst believes a single endpoint alert proves ransomware spread across the tenant. The team has decided to corroborate propagation with separate identity, process, and network observations before expanding impact. Which case-specific residual limitation MOST needs attention?
Overstating blast radius can trigger unnecessary isolation of unrelated business assets. Blast radius must be derived from observed affected entities rather than assumed from severity labels.
A green recommendation status might lag actual events or omit lateral activity elsewhere. The outstanding risk here is overstating blast radius can trigger unnecessary isolation of unrelated business assets.
Absence of new alerts during a sensor outage cannot be considered evidence of safety. The outstanding risk here is overstating blast radius can trigger unnecessary isolation of unrelated business assets.
A fluent AI summary is not a substitute for verified observations and accountable human decisions. The outstanding risk here is overstating blast radius can trigger unnecessary isolation of unrelated business assets.
Investigators suspect a compromised cloud mailbox created forwarding rules to conceal subsequent exfiltration. The required acceptance result is: A test forwarding-rule creation is attributable to the same validated actor and time window. Which response MOST DIRECTLY addresses the stated security-operations requirement?
Correlate mailbox audit actions, OAuth app permissions, and authentication sessions into the incident. Mail-flow manipulation and identity activity can reveal related but distinct stages of compromise. Confirm that a test forwarding-rule creation is attributable to the same validated actor and time window. Forwarding rules can be legitimate; authorized automation should be excluded with evidence.
Cloud app governance links OAuth permissions and observed API activity to potential data exposure.
Workload and identity evidence can reveal a single credential used across multiple protected resources.
Workload identities can be compromised through app credentials independently of human password events.
Investigators suspect a compromised cloud mailbox created forwarding rules to conceal subsequent exfiltration. The selected response is to correlate mailbox audit actions, OAuth app permissions, and authentication sessions into the incident. Which technical mechanism BEST explains its effectiveness?
Mail-flow manipulation and identity activity can reveal related but distinct stages of compromise. The change is Correlate mailbox audit actions, OAuth app permissions, and authentication sessions into the incident. Verify that a test forwarding-rule creation is attributable to the same validated actor and time window.
Defender for Cloud Apps file policies can detect risky sharing and apply connector-specific governance actions. The active incident mechanism is mail-flow manipulation and identity activity can reveal related but distinct stages of compromise.
Workload identities can be compromised through app credentials independently of human password events. The active incident mechanism is mail-flow manipulation and identity activity can reveal related but distinct stages of compromise.
Defender for Identity correlates directory authentication signals that may indicate credential replay or theft. The active incident mechanism is mail-flow manipulation and identity activity can reveal related but distinct stages of compromise.
The security team performs this response: Correlate mailbox audit actions, OAuth app permissions, and authentication sessions into the incident The original issue: investigators suspect a compromised cloud mailbox created forwarding rules to conceal subsequent exfiltration. Which observation BEST validates the intended outcome?
A test forwarding-rule creation is attributable to the same validated actor and time window. Mail-flow manipulation and identity activity can reveal related but distinct stages of compromise.
A test principal's suspicious operation is attributed to the correct subscription and role grants. The expected evidence here is A test forwarding-rule creation is attributable to the same validated actor and time window.
A test document's public share is removed with a recorded action outcome. The expected evidence here is A test forwarding-rule creation is attributable to the same validated actor and time window.
A test unauthorized credential is removed and corresponding application sign-in attempts stop. The expected evidence here is A test forwarding-rule creation is attributable to the same validated actor and time window.
Investigators suspect a compromised cloud mailbox created forwarding rules to conceal subsequent exfiltration. The team has decided to correlate mailbox audit actions, OAuth app permissions, and authentication sessions into the incident. Which case-specific residual limitation MOST needs attention?
Forwarding rules can be legitimate; authorized automation should be excluded with evidence. Mail-flow manipulation and identity activity can reveal related but distinct stages of compromise.
Resetting an app secret alone cannot prove no other long-lived token remains usable. The outstanding risk here is forwarding rules can be legitimate; authorized automation should be excluded with evidence.
Disabling a production principal without a dependency plan can interrupt legitimate applications. The outstanding risk here is forwarding rules can be legitimate; authorized automation should be excluded with evidence.
Revoking a shared production secret can break business systems if dependencies are not identified. The outstanding risk here is forwarding rules can be legitimate; authorized automation should be excluded with evidence.
Please check your mailbox for a message from support@examlabs.com and follow the directions.