CrowdStrike IDP Cert Guide PDF 100% Cover Real Exam Questions
Pass IDP Exam - Real Questions and Answers
NEW QUESTION # 30
Describe the difference between a Human account and a Programmatic account.
- A. A programmatic account is never authorized for multi-factor authentication
- B. A programmatic account is only used interactively
- C. A human account is an Administrator
- D. A human account is often used interactively
Answer: D
NEW QUESTION # 31
For false positives, the Detection details can be set to new"Actions"using:
- A. exits
- B. remediations
- C. exceptions
- D. recommendations
Answer: C
Explanation:
When an identity-based detection is determined to be afalse positive, Falcon Identity Protection allows administrators to take corrective action usingexceptions. According to the CCIS curriculum, exceptions are the mechanism by which detections can be suppressed for specific entities or conditions without disabling the detection entirely.
Exceptions are configured from theDetection detailsview and are intended to handle known, acceptable behavior that would otherwise continue to trigger detections. This allows security teams to reduce noise while maintaining visibility into true threats. Exceptions are especially valuable in environments with complex authentication patterns or legacy configurations.
The other options are incorrect:
* Exitsare not a detection control mechanism.
* Remediationsrefer to corrective actions, not suppression logic.
* Recommendationsprovide guidance but do not change detection behavior.
By usingexceptions, Falcon ensures that false positives are handled in a controlled and auditable way, aligning with best practices outlined in the CCIS material. Therefore,Option Cis the correct answer.
NEW QUESTION # 32
Which of the following would cause an identity-based incident type to change?
- A. A user changed the incident type in the console
- B. Detections related to the incident
- C. A user linked detections to the incident in the console
- D. An exclusion added to the incident
Answer: B
Explanation:
In Falcon Identity Protection,identity-based incidents are dynamicand can evolve over time as additional detections are associated with them. According to the CCIS curriculum, an incident'stype is automatically recalculatedbased on thedetections related to the incident, not by manual user actions.
As new identity-based detections are generated-such as credential misuse, lateral movement attempts, or abnormal authentication behavior-the platform continuously reassesses the incident. If the newly added detections indicate a different or more severe attack pattern, Falcon may automaticallychange the incident typeto better reflect the observed threat activity.
Manual actions such as adding exclusions or linking detections do not directly change the incident type.
Similarly, users cannot manually override an incident's classification. The classification logic is driven entirely by Falcon's analytics engine to ensure consistent, objective threat categorization.
This automated behavior is emphasized in CCIS training to highlight Falcon's ability toadapt incident context as attacks progress, makingOption Dthe correct answer.
NEW QUESTION # 33
Which of the following are minimum requirements for showing the Falcon Identity Verification Dialog on the end user's machine?
- A. .NET 3.5 and PowerShell 5.1
- B. Windows Vista and .NET 3.5
- C. Internet Explorer 9 and Windows Server 2008
- D. Windows Server 2008 and PowerShell 5.1
Answer: C
Explanation:
The Falcon Identity Verification Dialog is used to prompt users for identity verification during conditional access enforcement. According to the CCIS curriculum,Internet Explorer 9 and Windows Server 2008 represent theminimum supported requirementsfor rendering the Identity Verification Dialog on an end user' s system.
This requirement exists because the dialog relies on supported browser and OS components to present authentication challenges reliably during enforcement workflows. Systems that do not meet these minimum requirements may fail to display the dialog correctly, impacting the enforcement of MFA or identity verification actions.
The other options reference runtime frameworks or PowerShell versions that are not directly responsible for rendering the verification dialog. Therefore,Option Ais the correct and verified answer.
NEW QUESTION # 34
Which CrowdStrike documentation category would you search to find GraphQL examples?
- A. Identity Protection APIs
- B. XDR
- C. CrowdStrike APIs
- D. Threat Intelligence
Answer: C
Explanation:
GraphQL is the underlying query technology used by multiple CrowdStrike platforms, including Falcon Identity Protection. According to the CCIS curriculum,GraphQL examples are documented under the broader "CrowdStrike APIs" documentation category, not limited to a single product.
The CrowdStrike APIs section includes:
* Authentication and API key usage
* GraphQL schema references
* Example GraphQL queries and mutations
* Pagination, filtering, and response handling
While Identity Protection uses GraphQL for identity-specific queries, the examples themselves are centralized underCrowdStrike APIsto provide consistency across Falcon modules. Product-specific use cases are then layered on top of these core examples.
The other options are incorrect:
* Threat Intelligence focuses on adversary data.
* XDR covers detection and correlation concepts.
* Identity Protection APIs describe endpoints and permissions, not general GraphQL usage examples.
Therefore,Option Ais the correct and verified answer.
NEW QUESTION # 35
Which of the following areNOTincluded within the three-dot menu on Identity-based Detections?
Which of the following are not included within the three-dot menu on Identity-based Detections?
- A. Add to Watchlist
- B. Add comment
- C. Add exclusion
- D. Edit status
Answer: A
Explanation:
In Falcon Identity Protection, thethree-dot (#) action menuon anidentity-based detectionprovides analysts with a limited set of actions that applydirectly to the detection itself. According to the CCIS curriculum, these actions are designed to support investigation workflow, tuning, and documentation.
The supported actions in the detection-level three-dot menu include:
* Edit status, which allows analysts to update the detection state (for example, New, In Progress, or Closed).
* Add comment, which enables collaboration and documentation directly on the detection.
* Add exclusion, where supported, to suppress future detections that match known benign behavior.
Add to Watchlistisnot includedin this menu because watchlists are applied toentities(such as users, service accounts, or endpoints), not to detections. Watchlists are managed from entity views or investigation workflows and are used to increase visibility and monitoring priority for specific identities-not to act on individual detections.
This distinction is emphasized in CCIS training to reinforce the separation betweenentity-centric actionsand detection-centric actions. Because watchlists operate at the entity level,Option Bis the correct and verified answer.
NEW QUESTION # 36
The Enforce section of Identity Protection is used to:
- A. Define policy rules that determine what actions to take in response to certain triggers observed in the environment
- B. View all identity-based detections and identity-based incidents in the environment
- C. Gain an overview of the domain and indicate whether the domain follows best security practice
- D. Configure domains, appliances, subnets, connectors, risk configuration, and settings
Answer: A
Explanation:
The Enforce section of Falcon Identity Protection is dedicated to policy-based identity enforcement.
According to the CCIS curriculum, this section allows administrators to define and manage Policy Rules and Policy Groups that specify how the platform should respond when identity-related conditions are detected.
These rules evaluate triggers such as risky authentication behavior, privilege misuse, compromised credentials, or elevated risk scores, and then execute actions like blocking access, enforcing MFA, or initiating Falcon Fusion workflows. Enforce is therefore the execution layer of Falcon's identity security model.
The other options correspond to different sections of the platform:
Configuration tasks are handled in Configure.
Detections and incidents are reviewed in Monitor or Explore.
Domain posture overviews are displayed in Domain Security Overview.
Because Enforce directly controls what actions are taken in response to identity risk, Option B is the correct and verified answer.
NEW QUESTION # 37
Which option can be selected from the Threat Hunter menu to open the current Threat Hunter query in a new window as Graph API format?
- A. Save as Custom Query
- B. Open Query in API Builder
- C. Export to API Builder
- D. Save as Custom Report
Answer: B
Explanation:
Falcon Threat Hunter provides a direct integration with theAPI Builderto support advanced investigation workflows and automation. According to the CCIS curriculum, analysts can take an existing Threat Hunter query and convert it into aGraphQL-compatible formatby selectingOpen Query in API Builderfrom the Threat Hunter menu.
This option opens the current query in a new window within API Builder, automatically translating the query structure into GraphQL syntax where applicable. This enables security teams to reuse validated hunting logic for automation, reporting, or external integrations without rewriting queries from scratch.
The other menu options serve different purposes:
* Export to API Builderis not a valid menu action.
* Save as Custom Querystores the query for reuse inside Threat Hunter.
* Save as Custom Reportgenerates a reporting artifact, not an API query.
BecauseOpen Query in API Builderis the only option that opens the query in GraphQL format in a new window,Option Dis the correct and verified answer.
NEW QUESTION # 38 
Which of the followingBESTindicates that this user has an established baseline?
- A. The user has recent logon activity on ETIS-WS03
- B. The user has endpoints that they are considered owners of
- C. The user has a risk score of 6.4
- D. The user was found logging into five endpoints
Answer: B
Explanation:
In Falcon Identity Protection, auser baselineis established by observing consistent and repeatable behavior over time, including authentication patterns, endpoint associations, and usage context. According to the CCIS curriculum, one of the strongest indicators that a user has an established baseline is the presence ofendpoints for which the user is identified as an owner.
Endpoint ownership is determined through historical authentication behavior and usage frequency. When Falcon identifies that a user consistently logs into specific endpoints over time, those endpoints are marked as owned, which signifies that sufficient historical data exists to confidently model the user's normal behavior.
This ownership relationship is only created after Falcon has observed the user long enough to establish a reliable baseline.
The other options do not definitively indicate a baseline:
* Logging into multiple endpoints may occur during initial discovery or anomalous activity.
* A risk score reflects current risk posture, not baseline maturity.
* Recent logon activity alone does not imply historical consistency.
Becauseendpoint ownership requires sustained, predictable behavior over time, it is the clearest indicator that Falcon has successfully established a user baseline. Therefore,Option Bis the correct and verified answer.
NEW QUESTION # 39
Which of the following IDaaS connectors will allow Identity to ingest cloud activity along with applying SSO Policy?
- A. SAML
- B. Azure NPS
- C. ADFS
- D. Okta SSO
Answer: D
Explanation:
Falcon Identity Protection integrates withIdentity-as-a-Service (IDaaS)providers to ingest cloud authentication activity and enforce identity-based policies. According to the CCIS curriculum,Okta SSOis a supported IDaaS connector that enables Falcon to ingestcloud authentication eventswhile also applying Single Sign-On (SSO) policies.
Okta SSO provides rich identity telemetry, including login attempts, device context, and authentication outcomes. This data allows Falcon Identity Protection to correlate on-premises and cloud-based identity activity, extending identity risk analysis beyond Active Directory.
The other options are incorrect:
* ADFSis an on-premises federation service, not a cloud IDaaS.
* Azure NPSis used for RADIUS-based MFA, not SSO ingestion.
* SAMLis a protocol, not an IDaaS connector.
Because Okta SSO provides both cloud activity ingestion and SSO enforcement,Option Bis the correct and verified answer.
NEW QUESTION # 40
When creating an API key, which scope should be selected to retrieve Identity Protection detection and incident information?
- A. Identity Protection Detections
- B. Identity Protection Data
- C. Identity Protection Assessment
- D. Identity Protection Incidents
Answer: A
Explanation:
To retrieve identity-based detections and incident-related data using the CrowdStrike APIs, the API key must include the correctpermission scope. According to the CCIS curriculum, theIdentity Protection Detections scope is required to access identity-based detection and incident information through GraphQL.
This scope allows API queries to retrieve:
* Identity-based detections
* Associated incident metadata
* Detection attributes such as severity, status, and related entities
Incident data in Falcon Identity Protection isderived from detections, making the Detections scope the authoritative permission set for this information. Without this scope, GraphQL queries related to identity detections and incidents will fail authorization.
The other scopes are either too narrow or unrelated to detection retrieval. Therefore,Option Ais the correct and verified answer.
NEW QUESTION # 41
Can a specific detection be excluded altogether or just per entity?
- A. Only detections can be disabled using the Identity-Based Detection # Detection Exclusion page
- B. Only specific entities can be excluded by using the Identity-Based Detection # Detection Exclusion page
- C. All detections can be disabled, some detections support excluding entities
- D. Adding an exclusion for a detection creates a security hole, therefore a detection cannot be excluded
Answer: C
Explanation:
Falcon Identity Protection provides flexible control over how identity-based detections are handled through the Detection Exclusionsframework. According to the CCIS curriculum, administrators can eitherdisable an entire detection typeor, where supported,exclude specific entitiessuch as users, service accounts, or endpoints from triggering that detection.
Not all detections support entity-level exclusions. For detections that do, exclusions allow organizations to suppress known benign behavior without disabling the detection globally. This is particularly useful for service accounts or legacy systems that generate expected but non-malicious activity. When entity-level exclusion is not supported, administrators may choose todisable the detection entirely, which stops it from generating alerts across the environment.
The CCIS documentation clearly explains this dual model:
* All detections can be disabled, regardless of type
* Only some detections support entity-based exclusions
This approach balances operational flexibility with security integrity and avoids the misconception that exclusions automatically create security gaps. Therefore,Option Cis the correct and verified answer.
NEW QUESTION # 42
How should a user be classified if one requires observation for potential risk to the business?
- A. Watched User
- B. Honeytoken Account
- C. High Risk
- D. Marked User
Answer: A
Explanation:
Within Falcon Identity Protection, aWatched Useris a user explicitly designated forheightened monitoring due to potential business risk. According to the CCIS curriculum, watchlists are designed to provide additional visibility into users whose behavior, access level, or role may warrant closer observation, even if they have not yet exhibited confirmed malicious activity.
Watched Users may include executives, administrators, users with access to sensitive systems, or accounts suspected of being targeted. Placing a user on a watchlist does not imply compromise; instead, it ensures their activity is prioritized in investigations, detections, and dashboards.
The other options are incorrect:
* Honeytoken Accountsare decoy accounts designed to detect malicious usage.
* High Riskis a calculated risk state, not a monitoring classification.
* Marked Useris not a valid Falcon Identity Protection classification.
Because the CCIS material explicitly identifiesWatched Usersas accounts requiring observation for potential risk,Option Cis the correct and verified answer.
NEW QUESTION # 43
When an endpoint that has not been used in the last90 daysbecomes active, a detection forUse of Stale Endpointis reported.
- A. 60 days
- B. 90 days
- C. 180 days
- D. 30 days
Answer: B
Explanation:
Falcon Identity Protection identifiesstale endpointsas systems that have not authenticated or shown activity for an extended period and then suddenly become active. According to the CCIS curriculum, an endpoint that has been inactive for90 daysand then resumes activity will trigger aUse of Stale Endpointdetection.
This detection is important because attackers frequently exploit dormant or forgotten systems to re-enter environments, evade monitoring, or move laterally. A long period of inactivity followed by sudden authentication activity is considered a strong identity risk signal.
The 90-day threshold is used to establish a reliable inactivity baseline while minimizing false positives.
Shorter timeframes could incorrectly flag normal usage patterns, while longer timeframes could delay detection of genuine threats.
Because Falcon explicitly defines stale endpoint activity using a90-day inactivity window,Option Bis the correct answer.
NEW QUESTION # 44
The configuration of the Azure AD (Entra ID) Identity-as-a-Service connector requires which three pieces of information?
- A. Tenant Domain, Application ID, Scope
- B. Tenant Domain, Application ID, Application Secret
- C. Tenant Domain, Client Secret, User Identifier
- D. Tenant Domain, Token, Configuration File
Answer: B
Explanation:
To integrate Falcon Identity Protection withAzure AD (Entra ID)as an Identity-as-a-Service (IDaaS) provider, specific application-level credentials are required. According to the CCIS curriculum, the connector configuration requiresTenant Domain,Application (Client) ID, andApplication Secret.
These values are generated when registering an application in Azure AD and are used to authenticate Falcon Identity Protection securely via OAuth-based API access. This method ensures least-privilege access and allows the connector to ingest cloud authentication activity and apply SSO-related policy enforcement.
Other options list incomplete or incorrect credential combinations. Therefore,Option Dis the correct and verified answer.
NEW QUESTION # 45
Within which Identity Protection menu would an administrator enableAuthentication Traffic Inspection (ATI)for a domain?
- A. Configure > Identity Configuration Policies
- B. Enforce > Policy Rules
- C. Configure > Settings
- D. Enforce > Policy Settings
Answer: A
Explanation:
Authentication Traffic Inspection (ATI) is enabled throughIdentity Configuration Policies, which define how the Falcon sensor captures and inspects identity-related network traffic. According to the CCIS documentation, ATI configuration is performed underConfigure > Identity Configuration Policies.
These policies allow administrators to specify which authentication protocols are inspected, which domain controllers are covered, and how identity telemetry is collected. This configuration step is mandatory to enable identity visibility and detection capabilities.
The Enforce menu is used for policy rules and automated actions, not traffic inspection. General settings do not control sensor inspection behavior. Because ATI directly affects sensor data capture, it is managed exclusively through Identity Configuration Policies.
Therefore,Option Dis the correct and verified answer.
NEW QUESTION # 46
Which of the following isNOTan available Goal within the Domain Security Overview?
- A. Privileged Users Management
- B. Business Privileged Users Management
- C. AD Hygiene
- D. Pen Testing
Answer: B
Explanation:
The Domain Security Overview in Falcon Identity Protection usesGoalsto frame identity risks into focused security assessment perspectives. These goals allow organizations to evaluate identity posture based on specific security priorities such as directory hygiene, privilege exposure, or overall attack surface reduction.
According to the CCIS curriculum, theavailable GoalsincludePrivileged Users Management,AD Hygiene, Pen Testing, andReduce Attack Surface. These goals are predefined by CrowdStrike and determine how risks are grouped, weighted, and presented in reports.
Business Privileged Users Managementisnot an available Goalwithin the Domain Security Overview.
While Falcon Identity Protection does support the concept ofbusiness privilegesand evaluates their impact on users and entities, this concept is handled through risk analysis and configuration-not as a selectable Domain Security Goal.
The CCIS documentation clearly distinguishes betweenGoals(which control reporting and assessment views) andbusiness privilege modeling(which influences risk scoring). Therefore,Option Bis the correct and verified answer.
NEW QUESTION # 47
Within the Falcon Identity Protection portal, which page allows you to enable/disable Policy Rules?
- A. Configure
- B. Policy Enforcement
- C. Identity-Based Detections
- D. Enforce
Answer: D
Explanation:
In Falcon Identity Protection, Policy Rules are managed within the Enforce section of the portal. The CCIS documentation explains that Enforce is the operational area where administrators create, enable, disable, and manage Policy Rules and Policy Groups.
This section is specifically designed for identity enforcement logic, allowing security teams to activate or suspend rules without modifying underlying configurations or analytics. Enabling or disabling a Policy Rule immediately affects how identity conditions are enforced across the environment.
Other sections serve different purposes:
Configure manages connectors, domains, subnets, and risk settings.
Identity-Based Detections is used for investigation and monitoring.
Policy Enforcement is not a standalone navigation section in Falcon Identity Protection.
Because rule activation and enforcement control reside exclusively in Enforce, Option B is the correct and verified answer.
NEW QUESTION # 48
By using compromised credentials, threat actors are able to bypass theExecutionphase of the MITRE ATT&CK framework and move directly into:
- A. Discovery
- B. Lateral Movement
- C. Weaponization
- D. Initial Access
Answer: A
Explanation:
The CCIS curriculum highlights a critical identity-security concept: when attackers usecompromised credentials, they often bypass traditional malware-based attack phases, including theExecutionphase of the MITRE ATT&CK framework. Because no malicious code needs to be executed, attackers can immediately begin interacting with the environment as a legitimate user.
As a result, threat actors move directly into theDiscoveryphase. During Discovery, attackers enumerate users, groups, privileges, systems, domain relationships, and trust paths to understand the environment and plan further actions. This behavior is commonly observed in identity-based attacks and living-off-the-land techniques.
Falcon Identity Protection is specifically designed to detect this behavior by monitoring authentication traffic, privilege usage, and anomalous identity activity-areas where traditional EDR tools may have limited visibility.
The other options are incorrect:
* Initial Access has already occurred via credential compromise.
* Weaponization and Execution are not required.
* Lateral Movement typically follows Discovery.
Because compromised credentials allow attackers to jump straight intoDiscovery,Option Cis the correct and verified answer.
NEW QUESTION # 49
The NIST SP 800-207 framework for Zero Trust Architecture defines validation and authentication standards for users in which network locations?
- A. Only those users inside the network
- B. Only those users accessing the network remotely over VPN
- C. Only those users outside the network
- D. All users both inside and outside of the network
Answer: D
Explanation:
TheNIST SP 800-207 Zero Trust Architectureframework fundamentally rejects the concept of implicit trust based on network location. As outlined in both NIST guidance and reinforced in the CCIS curriculum,all users must be continuously validated and authenticated regardless of whether they are inside or outside the network perimeter.
Zero Trust assumes that threats can originate from anywhere, including internal networks. Therefore, authentication and authorization decisions must be made dynamically using identity, device posture, behavior, and risk signals-not network placement.
Falcon Identity Protection aligns directly with this principle by continuously evaluating identity behavior for all users, whether they authenticate from internal corporate networks, remote locations, or cloud environments.
Because Zero Trust applies universally,Option Cis the correct and verified answer.
NEW QUESTION # 50
Any countries or regions included in the _ will trigger a geolocation detection.
- A. Exclusion
- B. Blocklist
- C. Allowlist
- D. Dictionary
Answer: B
Explanation:
Falcon Identity Protection supportsgeolocation-based detectionsto identify potentially risky authentication activity originating from unexpected or prohibited locations. According to the CCIS curriculum, any countries or regions added to theBlocklistwill automatically trigger a geolocation-based detection when authentication traffic is observed from those locations.
The Blocklist is designed to explicitly definedisallowed geographic regions. When an authentication attempt originates from a blocklisted country or region, Falcon treats the activity as suspicious and generates a detection or contributes to increased identity risk.
By contrast:
* An Allowlist defines approved locations and suppresses detections.
* A Dictionary is used for password-related analysis.
* An Exclusion suppresses detections rather than generating them.
Because geolocation detections are triggered byblocklisted locations,Option Ais the correct answer.
NEW QUESTION # 51
The CISO of your organization recently read a report about the increased usage of identity brokers and is interested in finding a solution for the company. Which of the following makes Falcon Identity a valid solution for the organization?
- A. Provides the ability to audit and record sessions across multiple methods, such as SSH, RDP, and SMB
- B. Allows administrators to store and delegate passwords to application servers
- C. Falcon Identity is able to be a middleware between Active Directory and a Human Resource Information System (HRIS)
- D. Gives the organization the ability to proactively mitigate risks, as well as protect critical Active Directory infrastructure through Policy Rules
Answer: D
Explanation:
Falcon Identity Protection is designed to address the growing threat ofidentity brokers, which act as intermediaries that abuse identity infrastructure to facilitate lateral movement, privilege escalation, and persistent access. The CCIS curriculum emphasizes that Falcon Identity Protection providesproactive identity risk mitigationrather than reactive session monitoring or password vaulting.
The platform continuously inspects authentication traffic and identity behavior across Active Directory and Azure AD environments, building behavioral baselines and identifying abnormal activity associated with brokered identity attacks. ThroughPolicy Rules, organizations can automatically enforce controls such as blocking risky authentications, enforcing MFA, or triggering remediation workflows when identity abuse is detected.
The incorrect options describe capabilities associated withPrivileged Access Management (PAM)orIAM middleware, which are not the focus of Falcon Identity Protection. Falcon does not record interactive sessions, act as an HRIS bridge, or store delegated credentials. Instead, it protects identity infrastructure by detecting and preventing identity misuse in real time.
This proactive enforcement model aligns directly with Zero Trust principles and makes Falcon Identity Protection a strong solution against identity broker activity. Therefore,Option Cis the correct and verified answer.
NEW QUESTION # 52
How long does it typically take Falcon Identity to develop a baseline of a user?
- A. One week
- B. Three months
- C. Two weeks
- D. One month
Answer: A
Explanation:
Falcon Identity Protection establishes auser baselineby observing authentication behavior over time, including login frequency, endpoints used, access patterns, and protocol usage. According to the CCIS curriculum, Falcon typically requiresapproximately one weekof consistent activity to develop an initial, reliable baseline for a user.
This baseline allows Falcon to distinguish normal behavior from anomalies and to calculate accurate risk scores. While the baseline continues to mature over time and becomes more precise with additional data, the first usable behavioral model is generally formed within a week.
Longer timeframes such as one or three months are not required to begin detecting abnormal behavior.
Conversely, periods shorter than a week may not provide sufficient behavioral data to accurately model normal usage patterns.
Because Falcon can rapidly establish a functional baseline while continuously refining it,Option C (One week)is the correct and verified answer.
NEW QUESTION # 53
Which of the following users would most likely have aHIGHrisk score?
- A. Privileged user with a Compromised Password
- B. User that recently logged in from a shared endpoint
- C. User that has not logged in recently and is marked as Stale
- D. User that is a member of the Domain Admins group
Answer: A
Explanation:
Falcon Identity Protection calculates user risk scores based on a combination ofprivilege level,credential exposure, andbehavioral indicators. According to the CCIS curriculum, aprivileged user with a compromised passwordrepresents one of the highest-risk identity scenarios.
Privileged accounts-such as administrators or service accounts with elevated access-already pose increased risk due to their access scope. When Falcon detects that such an account's credentials have been compromised, the risk escalates significantly because attackers can immediately gain high-impact access without further escalation.
The other options do not inherently represent the same level of risk:
* Logging in from a shared endpoint may increase risk but is context-dependent.
* Stale users are risky but typically lower risk than active compromised credentials.
* Domain Admin group membership alone does not imply compromise.
Becausecredential compromise combined with privilegedramatically increases attack potential,Option Bis the correct and verified answer.
NEW QUESTION # 54
......
100% Free IDP Daily Practice Exam With 60 Questions: https://actual4test.practicetorrent.com/IDP-practice-exam-torrent.html