Question 230
An authorized responder at Meridian Analytics has selected the secret leakage in repository approach to prevent deployment credentials being committed into application source control. Which concrete implementation step belongs to that approach instead of an adjacent but different SOC workflow?
- Run software dependency and vulnerability checks in the CI pipeline.
- Use managed secret storage and automated precommit secret detection.
- Encrypt storage with centrally managed key-recovery and access controls.
- Compare IdP sessions device posture VPN egress and MFA events before classifying.
Explanation
Correct Answer
B:To prevent deployment credentials being committed into application source control, this step operationalizes secret leakage in repository. In particular, use managed secret storage and automated precommit secret detection; acceptance requires that a test secret triggers the repository guard while valid runtime retrieval works.
Incorrect Answers
A:This step implements ci dependency scanning, aimed at catch a newly disclosed vulnerable library before code is promoted to production. It does not carry out the needed step for secret leakage in repository, where responders must use managed secret storage and automated precommit secret detection.
C:This step implements data at rest safeguards, aimed at protect confidential files left on a stolen employee laptop. It does not carry out the needed step for secret leakage in repository, where responders must use managed secret storage and automated precommit secret detection.
D:This step implements ueba travel anomaly validation, aimed at triage an impossible-travel login alert for a user accessing a VPN gateway. It does not carry out the needed step for secret leakage in repository, where responders must use managed secret storage and automated precommit secret detection.
Question 231
Highland Operations has performed this action as part of secret leakage in repository: Use managed secret storage and automated precommit secret detection. The requirement is to prevent deployment credentials being committed into application source control. Which observation actually confirms the intended result?
- Build status rejects artifacts that violate documented severity policy.
- A powered-off stolen drive cannot expose plaintext without decryption credentials.
- A test secret triggers the repository guard while valid runtime retrieval works.
- Corroborated sessions distinguish proxy routing from account misuse.
Explanation
Correct Answer
C:The relevant acceptance signal is that a test secret triggers the repository guard while valid runtime retrieval works. It verifies the requested result to prevent deployment credentials being committed into application source control rather than merely measuring unrelated activity.
Incorrect Answers
A:This is an acceptance observation for ci dependency scanning, which deals with catch a newly disclosed vulnerable library before code is promoted to production. It does not verify that a test secret triggers the repository guard while valid runtime retrieval works in the specified case.
B:This is an acceptance observation for data at rest safeguards, which deals with protect confidential files left on a stolen employee laptop. It does not verify that a test secret triggers the repository guard while valid runtime retrieval works in the specified case.
D:This is an acceptance observation for ueba travel anomaly validation, which deals with triage an impossible-travel login alert for a user accessing a VPN gateway. It does not verify that a test secret triggers the repository guard while valid runtime retrieval works in the specified case.
Question 232
During Lakeside Finance's post-change review, secret leakage in repository was selected to prevent deployment credentials being committed into application source control. The primary implementation looks successful. Which remaining limitation or failure mode is directly relevant to this specific approach?
- Passing a dependency scan does not establish runtime configuration safety.
- Full-disk encryption offers limited protection after an attacker obtains an unlocked session.
- Geolocation inferred from IP addresses can be wrong for VPN users.
- Deleting one Git commit may not erase the secret from all history or caches.
Explanation
Correct Answer
D:The residual risk for this case is that deleting one Git commit may not erase the secret from all history or caches. This matters even after the measure to prevent deployment credentials being committed into application source control appears to work and should be reflected in the operational plan.
Incorrect Answers
A:That caution belongs to ci dependency scanning under the different requirement to catch a newly disclosed vulnerable library before code is promoted to production. The current case instead requires managing the risk that deleting one Git commit may not erase the secret from all history or caches.
B:That caution belongs to data at rest safeguards under the different requirement to protect confidential files left on a stolen employee laptop. The current case instead requires managing the risk that deleting one Git commit may not erase the secret from all history or caches.
C:That caution belongs to ueba travel anomaly validation under the different requirement to triage an impossible-travel login alert for a user accessing a VPN gateway. The current case instead requires managing the risk that deleting one Git commit may not erase the secret from all history or caches.
Question 233
Cedar Health's security operations team must give analysts context about a suspicious domain across diverse internal alerts. Several nearby defensive approaches are under consideration. Which approach is the most direct match for this specific requirement?
- Threat intelligence enrichment
- Indicator feed lifecycle
- Overbroad IDS threshold
- AI clustering of malicious infrastructure
Explanation
Correct Answer
A:Threat intelligence enrichment addresses this case because the team should normalize the domain indicator and enrich it using a threat intelligence platform. The direct verification is that related alerts show provenance confidence timestamps and campaign context.
Incorrect Answers
B:Indicator feed lifecycle would address a different operational issue: prevent stale threat indicators from blocking legitimate traffic indefinitely. The separate task is to apply indicator expiration rules and source provenance when syncing feeds, rather than the requested outcome to give analysts context about a suspicious domain across diverse internal alerts.
C:Overbroad IDS threshold would address a different operational issue: troubleshoot a detection rule that fires on every application health check. The separate task is to replay benign and malicious traffic and tighten the relevant match conditions, rather than the requested outcome to give analysts context about a suspicious domain across diverse internal alerts.
D:AI clustering of malicious infrastructure would address a different operational issue: group related suspicious infrastructure before launching an investigation. The separate task is to cluster indicators on shared infrastructure traits then validate overlaps manually, rather than the requested outcome to give analysts context about a suspicious domain across diverse internal alerts.
Question 234
An authorized responder at Mariner Logistics has selected the threat intelligence enrichment approach to give analysts context about a suspicious domain across diverse internal alerts. Which concrete implementation step belongs to that approach instead of an adjacent but different SOC workflow?
- Apply indicator expiration rules and source provenance when syncing feeds.
- Normalize the domain indicator and enrich it using a threat intelligence platform.
- Replay benign and malicious traffic and tighten the relevant match conditions.
- Cluster indicators on shared infrastructure traits then validate overlaps manually.
Explanation
Correct Answer
B:To give analysts context about a suspicious domain across diverse internal alerts, this step operationalizes threat intelligence enrichment. In particular, normalize the domain indicator and enrich it using a threat intelligence platform; acceptance requires that related alerts show provenance confidence timestamps and campaign context.
Incorrect Answers
A:This step implements indicator feed lifecycle, aimed at prevent stale threat indicators from blocking legitimate traffic indefinitely. It does not carry out the needed step for threat intelligence enrichment, where responders must normalize the domain indicator and enrich it using a threat intelligence platform.
C:This step implements overbroad ids threshold, aimed at troubleshoot a detection rule that fires on every application health check. It does not carry out the needed step for threat intelligence enrichment, where responders must normalize the domain indicator and enrich it using a threat intelligence platform.
D:This step implements ai clustering of malicious infrastructure, aimed at group related suspicious infrastructure before launching an investigation. It does not carry out the needed step for threat intelligence enrichment, where responders must normalize the domain indicator and enrich it using a threat intelligence platform.
Question 235
Pioneer Research has performed this action as part of threat intelligence enrichment: Normalize the domain indicator and enrich it using a threat intelligence platform. The requirement is to give analysts context about a suspicious domain across diverse internal alerts. Which observation actually confirms the intended result?
- Expired indicators are retired and relevant current ones remain searchable.
- Tests preserve malicious detections while excluding documented health probes.
- Related alerts show provenance confidence timestamps and campaign context.
- Candidate clusters have concrete linking artifacts such as certificates or DNS patterns.
Explanation
Correct Answer
C:The relevant acceptance signal is that related alerts show provenance confidence timestamps and campaign context. It verifies the requested result to give analysts context about a suspicious domain across diverse internal alerts rather than merely measuring unrelated activity.
Incorrect Answers
A:This is an acceptance observation for indicator feed lifecycle, which deals with prevent stale threat indicators from blocking legitimate traffic indefinitely. It does not verify that related alerts show provenance confidence timestamps and campaign context in the specified case.
B:This is an acceptance observation for overbroad ids threshold, which deals with troubleshoot a detection rule that fires on every application health check. It does not verify that related alerts show provenance confidence timestamps and campaign context in the specified case.
D:This is an acceptance observation for ai clustering of malicious infrastructure, which deals with group related suspicious infrastructure before launching an investigation. It does not verify that related alerts show provenance confidence timestamps and campaign context in the specified case.
Question 236
During Willow Retail's post-change review, threat intelligence enrichment was selected to give analysts context about a suspicious domain across diverse internal alerts. The primary implementation looks successful. Which remaining limitation or failure mode is directly relevant to this specific approach?
- Automating blocking without expiration can cause avoidable false positives.
- Permanent global rule disablement creates blind spots.
- Shared hosting and CDNs can create false linkages between unrelated tenants.
- Indicator feeds can contain expired or misattributed entries.
Explanation
Correct Answer
D:The residual risk for this case is that indicator feeds can contain expired or misattributed entries. This matters even after the measure to give analysts context about a suspicious domain across diverse internal alerts appears to work and should be reflected in the operational plan.
Incorrect Answers
A:That caution belongs to indicator feed lifecycle under the different requirement to prevent stale threat indicators from blocking legitimate traffic indefinitely. The current case instead requires managing the risk that indicator feeds can contain expired or misattributed entries.
B:That caution belongs to overbroad ids threshold under the different requirement to troubleshoot a detection rule that fires on every application health check. The current case instead requires managing the risk that indicator feeds can contain expired or misattributed entries.
C:That caution belongs to ai clustering of malicious infrastructure under the different requirement to group related suspicious infrastructure before launching an investigation. The current case instead requires managing the risk that indicator feeds can contain expired or misattributed entries.
Question 237
Northstar Manufacturing's security operations team must prevent stale threat indicators from blocking legitimate traffic indefinitely. Several nearby defensive approaches are under consideration. Which approach is the most direct match for this specific requirement?
- Indicator feed lifecycle
- Threat intelligence enrichment
- Host inventory coverage
- High-volume false-positive tuning
Explanation
Correct Answer
A:Indicator feed lifecycle addresses this case because the team should apply indicator expiration rules and source provenance when syncing feeds. The direct verification is that expired indicators are retired and relevant current ones remain searchable.
Incorrect Answers
B:Threat intelligence enrichment would address a different operational issue: give analysts context about a suspicious domain across diverse internal alerts. The separate task is to normalize the domain indicator and enrich it using a threat intelligence platform, rather than the requested outcome to prevent stale threat indicators from blocking legitimate traffic indefinitely.
C:Host inventory coverage would address a different operational issue: evaluate whether an asset is included in the enterprise security baseline. The separate task is to correlate discovery inventory and EDR enrollment before scoring posture, rather than the requested outcome to prevent stale threat indicators from blocking legitimate traffic indefinitely.
D:High-volume false-positive tuning would address a different operational issue: reduce IDS alerts triggered by a legitimate approved vulnerability scanner. The separate task is to restrict a suppression or threshold rule to the validated scanner identity and traffic, rather than the requested outcome to prevent stale threat indicators from blocking legitimate traffic indefinitely.
Question 238
An authorized responder at Meridian Analytics has selected the indicator feed lifecycle approach to prevent stale threat indicators from blocking legitimate traffic indefinitely. Which concrete implementation step belongs to that approach instead of an adjacent but different SOC workflow?
- Normalize the domain indicator and enrich it using a threat intelligence platform.
- Apply indicator expiration rules and source provenance when syncing feeds.
- Correlate discovery inventory and EDR enrollment before scoring posture.
- Restrict a suppression or threshold rule to the validated scanner identity and traffic.
Explanation
Correct Answer
B:To prevent stale threat indicators from blocking legitimate traffic indefinitely, this step operationalizes indicator feed lifecycle. In particular, apply indicator expiration rules and source provenance when syncing feeds; acceptance requires that expired indicators are retired and relevant current ones remain searchable.
Incorrect Answers
A:This step implements threat intelligence enrichment, aimed at give analysts context about a suspicious domain across diverse internal alerts. It does not carry out the needed step for indicator feed lifecycle, where responders must apply indicator expiration rules and source provenance when syncing feeds.
C:This step implements host inventory coverage, aimed at evaluate whether an asset is included in the enterprise security baseline. It does not carry out the needed step for indicator feed lifecycle, where responders must apply indicator expiration rules and source provenance when syncing feeds.
D:This step implements high-volume false-positive tuning, aimed at reduce IDS alerts triggered by a legitimate approved vulnerability scanner. It does not carry out the needed step for indicator feed lifecycle, where responders must apply indicator expiration rules and source provenance when syncing feeds.
Question 239
Highland Operations has performed this action as part of indicator feed lifecycle: Apply indicator expiration rules and source provenance when syncing feeds. The requirement is to prevent stale threat indicators from blocking legitimate traffic indefinitely. Which observation actually confirms the intended result?
- Related alerts show provenance confidence timestamps and campaign context.
- The asset's owner software version and telemetry status are recorded.
- Expired indicators are retired and relevant current ones remain searchable.
- Scanner-related alerts decrease while malicious traffic rules still fire.
Explanation
Correct Answer
C:The relevant acceptance signal is that expired indicators are retired and relevant current ones remain searchable. It verifies the requested result to prevent stale threat indicators from blocking legitimate traffic indefinitely rather than merely measuring unrelated activity.
Incorrect Answers
A:This is an acceptance observation for threat intelligence enrichment, which deals with give analysts context about a suspicious domain across diverse internal alerts. It does not verify that expired indicators are retired and relevant current ones remain searchable in the specified case.
B:This is an acceptance observation for host inventory coverage, which deals with evaluate whether an asset is included in the enterprise security baseline. It does not verify that expired indicators are retired and relevant current ones remain searchable in the specified case.
D:This is an acceptance observation for high-volume false-positive tuning, which deals with reduce IDS alerts triggered by a legitimate approved vulnerability scanner. It does not verify that expired indicators are retired and relevant current ones remain searchable in the specified case.
Question 240
During Lakeside Finance's post-change review, indicator feed lifecycle was selected to prevent stale threat indicators from blocking legitimate traffic indefinitely. The primary implementation looks successful. Which remaining limitation or failure mode is directly relevant to this specific approach?
- Indicator feeds can contain expired or misattributed entries.
- An unmanaged host cannot be assessed solely from centrally enrolled endpoints.
- Disabling the entire signature would hide real threats from other sources.
- Automating blocking without expiration can cause avoidable false positives.
Explanation
Correct Answer
D:The residual risk for this case is that automating blocking without expiration can cause avoidable false positives. This matters even after the measure to prevent stale threat indicators from blocking legitimate traffic indefinitely appears to work and should be reflected in the operational plan.
Incorrect Answers
A:That caution belongs to threat intelligence enrichment under the different requirement to give analysts context about a suspicious domain across diverse internal alerts. The current case instead requires managing the risk that automating blocking without expiration can cause avoidable false positives.
B:That caution belongs to host inventory coverage under the different requirement to evaluate whether an asset is included in the enterprise security baseline. The current case instead requires managing the risk that automating blocking without expiration can cause avoidable false positives.
C:That caution belongs to high-volume false-positive tuning under the different requirement to reduce IDS alerts triggered by a legitimate approved vulnerability scanner. The current case instead requires managing the risk that automating blocking without expiration can cause avoidable false positives.
Performing Cybersecurity Using Cisco Security Technologies (CBRCOR) (350-201) Practice Tests