Question 110Network taps cover the headquarters VLAN but contractors work over split-tunnel connections elsewhere. After the change — Inventory coverage across remote clients, cloud boundaries and existing monitored links. — which result would best demonstrate that it worked? A terminated test container remains linked to its service identity and deployment event in the case timeline. The case report separates confirmed infrastructure activity from unproven actor identity. A documented matrix shows each test path's network and endpoint event sources. Known samples trigger signatures and an unknown safe behavioral simulation triggers the analytic. ExplanationCorrect Answer C:A documented matrix shows each test path's network and endpoint event sources. The result demonstrates the repair under real operating conditions. Inventory coverage across remote clients, cloud boundaries and existing monitored links. It limits the chance that unmonitored remote paths could host unnoticed compromise. Incorrect Answers A:Cloud and container environments require entity tracking beyond stable hostnames. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A documented matrix shows each test path's network and endpoint event sources. B:Threat-actor attribution requires multiple independent evidence sources beyond a single network address. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A documented matrix shows each test path's network and endpoint event sources. D:Rule-based signatures and behavior-based detection detect different classes of activity. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A documented matrix shows each test path's network and endpoint event sources.
Question 111A workstation records malware-like behavior but its host IDS uses only legacy static signatures. What is the most direct risk if this problem remains unresolved? Signature-only host monitoring may miss previously unseen variants. Untrusted clients might reach sensitive management services. An incorrect attribution could compromise disciplinary or legal decisions. Platform confusion may cause missed authentication abuse. ExplanationCorrect Answer A:Signature-only host monitoring may miss previously unseen variants. The risk is connected to the particular hardware or process gap. Add an approved behavior-based detection rule and tune it against safe endpoint simulations. Confirm through: The controlled behavioral test produces a case even without a known file signature. Incorrect Answers B:Antimalware health does not establish host-network access control effectiveness. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Signature-only host monitoring may miss previously unseen variants. C:Shared credentials weaken person-level attribution even when commands are recorded. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Signature-only host monitoring may miss previously unseen variants. D:Operating-system logging locations and event structures depend on the platform. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Signature-only host monitoring may miss previously unseen variants.
Question 112A production IPS deployed inline loses connectivity, and the team does not know its configured fail-open behavior. What is the most appropriate security operations response? Document limits of header filtering and add approved application telemetry where visibility permits. Select the precise timed connection tuple and reassemble only that TCP stream. Review fail-open or fail-closed policy and test approved appliance maintenance scenarios. Track file versions, algorithms, sources and hashes before correlating indicator matches. ExplanationCorrect Answer C:Review fail-open or fail-closed policy and test approved appliance maintenance scenarios. Inline devices can change traffic availability when their own health or power changes. The acceptance test is specific: Controlled failover demonstrates the documented forwarding result when the IPS is unavailable. Incorrect Answers A:Packet filtering uses header attributes whereas deep inspection may require accessible higher-layer content. That is relevant to a different intervention. For the stated situation, the required action is: Review fail-open or fail-closed policy and test approved appliance maintenance scenarios. The governing reason is: Inline devices can change traffic availability when their own health or power changes. B:File extraction depends on correct stream identification, sequencing and available bytes. That is relevant to a different intervention. For the stated situation, the required action is: Review fail-open or fail-closed policy and test approved appliance maintenance scenarios. The governing reason is: Inline devices can change traffic availability when their own health or power changes. D:Hash comparisons require consistent algorithms and immutable artifact boundaries. That is relevant to a different intervention. For the stated situation, the required action is: Review fail-open or fail-closed policy and test approved appliance maintenance scenarios. The governing reason is: Inline devices can change traffic availability when their own health or power changes.
Question 113A campaign report links one domain and one malware sample but has no proven adversary infrastructure relationship. The team proposes: Use Diamond Model entities and confidence to distinguish observed capabilities, infrastructure and victims. Which security principle best explains the decision? Forensic collection order should consider evidence that disappears when a system powers off. Intrusion models relate adversary, capability, infrastructure and victim without guaranteeing attribution. Incident planning must account for reporting obligations and protected information handling. Incident handling balances timely containment with lawful and reliable evidence preservation. ExplanationCorrect Answer B:Intrusion models relate adversary, capability, infrastructure and victim without guaranteeing attribution. The principle identifies the control actually at risk. Use Diamond Model entities and confidence to distinguish observed capabilities, infrastructure and victims. It should produce: The analysis marks observed links and uncertain actor connections explicitly. Incorrect Answers A:Forensic collection order should consider evidence that disappears when a system powers off. This does not establish the proposed intervention. The governing principle here is: Intrusion models relate adversary, capability, infrastructure and victim without guaranteeing attribution. Apply it by: Use Diamond Model entities and confidence to distinguish observed capabilities, infrastructure and victims. C:Incident planning must account for reporting obligations and protected information handling. This does not establish the proposed intervention. The governing principle here is: Intrusion models relate adversary, capability, infrastructure and victim without guaranteeing attribution. Apply it by: Use Diamond Model entities and confidence to distinguish observed capabilities, infrastructure and victims. D:Incident handling balances timely containment with lawful and reliable evidence preservation. This does not establish the proposed intervention. The governing principle here is: Intrusion models relate adversary, capability, infrastructure and victim without guaranteeing attribution. Apply it by: Use Diamond Model entities and confidence to distinguish observed capabilities, infrastructure and victims.
Question 114A branch uploads far more data after hours but dashboards show only inbound volume totals. What is the most direct risk if this problem remains unresolved? Excess false positives could bury a real data theft event. Large unauthorized exports may blend into normal aggregate traffic. Lateral movement could remain unseen despite healthy endpoint software. Altered balances could evade detection and misstate customer accounts. ExplanationCorrect Answer B:Large unauthorized exports may blend into normal aggregate traffic. The stated weakness directly creates that exposure. Traffic profiling can expose potential exfiltration through directional and temporal deviations. Reduce it by: Baseline bidirectional transfer volume by destination, identity and business schedule. Incorrect Answers A:A traffic anomaly requires business context before it establishes a data-loss incident. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Large unauthorized exports may blend into normal aggregate traffic. C:Endpoint and network sensors expose different visibility and detection opportunities. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Large unauthorized exports may blend into normal aggregate traffic. D:Integrity means detecting and preventing unauthorized modifications to trusted information. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Large unauthorized exports may blend into normal aggregate traffic.
Question 115A monitoring dashboard shows a detection but the exported log omits timezone and original event identifier. After the change — Preserve event IDs, source timestamps and normalization offsets with the collected evidence. — which result would best demonstrate that it worked? The timeline links the download to a matching file artifact or records the corroboration gap. The device label and handoff records match the analyst's evidence register. Raw and normalized times map to the same event with stable identifiers. The failed Windows logon is found with its account, host and result code. ExplanationCorrect Answer C:Raw and normalized times map to the same event with stable identifiers. The observation confirms the corrected dependency: Event provenance and time normalization are essential to credible correlation. The avoided exposure is: Ambiguous chronology could reverse cause and effect. Incorrect Answers A:Independent evidence sources can strengthen an inference without converting it automatically into certainty. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Raw and normalized times map to the same event with stable identifiers. B:Investigation accountability depends on knowing which custodian handled each artifact. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Raw and normalized times map to the same event with stable identifiers. D:Operating-system logging locations and event structures depend on the platform. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Raw and normalized times map to the same event with stable identifiers.
Question 116A service team mistakes a PKCS#12 keystore for a public certificate bundle and uploads sensitive keys to a shared ticket. What is the most direct risk if this problem remains unresolved? Leaked private keys could permit unauthorized service impersonation. Incompatible settings could block valid secure connections. Missing translation context could lead responders to isolate the wrong device. Removing encryption broadly could create greater exposure than the original alert. ExplanationCorrect Answer A:Leaked private keys could permit unauthorized service impersonation. PKCS packaging can hold private keys and must be classified by actual contents. An effective remedy is: Recover the exposed key material and enforce separate handling of public certificates and private-key containers. The success indicator is: The unsafe attachment is revoked and key rotation is logged under approved custody. Incorrect Answers B:Certificate validity and cipher-suite negotiation are separate TLS handshake requirements. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Leaked private keys could permit unauthorized service impersonation. C:Address translation changes visible network identities and requires mapping to original endpoints. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Leaked private keys could permit unauthorized service impersonation. D:Detection needs cannot justify blanket removal of confidentiality controls. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Leaked private keys could permit unauthorized service impersonation.
Question 117A dashboard reports all denied connections as true positives even though many were harmless configuration mistakes. After the change — Validate labels against confirmed event truth and separate benign denials from malicious attempts. — which result would best demonstrate that it worked? Labeled benign sessions stay quiet and safe positive simulations produce the intended alerts. The labeled sample set documents true positives, false positives, negatives and benign events. The report identifies the confirmed destination service or explicitly states the field is missing. The parsed upper-layer protocol and ports match a known benign IPv6 test flow. ExplanationCorrect Answer B:The labeled sample set documents true positives, false positives, negatives and benign events. A true positive requires a detection matched to actual target behavior, not any enforcement action. The test establishes that the fix addresses the specific failure. Incorrect Answers A:True negatives and false negatives cannot be distinguished without ground-truth test cases. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The labeled sample set documents true positives, false positives, negatives and benign events. C:Service mapping depends on transport ports and the actual listener context. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The labeled sample set documents true positives, false positives, negatives and benign events. D:IPv4 and IPv6 header structures differ, affecting offsets and extension processing. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The labeled sample set documents true positives, false positives, negatives and benign events.
Question 118A SOC correlates two alerts by time alone despite different destination ports and processes. The team proposes: Combine session metadata, endpoint identity and relevant transaction fields in event correlation. Which security principle best explains the decision? Correlating distinct event data types requires shared identifiers and meaningful temporal context. Public/private key matching is essential independently of certificate metadata. Symmetric keys require shared-secret handling while asymmetric techniques support distinct public and private roles. Anonymizing overlays can separate the observable exit from the controlling user. ExplanationCorrect Answer A:Correlating distinct event data types requires shared identifiers and meaningful temporal context. Combine session metadata, endpoint identity and relevant transaction fields in event correlation. That is the direct response to this rule. Verify using: The case timeline links the intended transactions and excludes an unrelated same-minute event. Incorrect Answers B:Public/private key matching is essential independently of certificate metadata. This does not establish the proposed intervention. The governing principle here is: Correlating distinct event data types requires shared identifiers and meaningful temporal context. Apply it by: Combine session metadata, endpoint identity and relevant transaction fields in event correlation. C:Symmetric keys require shared-secret handling while asymmetric techniques support distinct public and private roles. This does not establish the proposed intervention. The governing principle here is: Correlating distinct event data types requires shared identifiers and meaningful temporal context. Apply it by: Combine session metadata, endpoint identity and relevant transaction fields in event correlation. D:Anonymizing overlays can separate the observable exit from the controlling user. This does not establish the proposed intervention. The governing principle here is: Correlating distinct event data types requires shared identifiers and meaningful temporal context. Apply it by: Combine session metadata, endpoint identity and relevant transaction fields in event correlation.
Question 119A monitoring team claims success because a large number of allowed benign sessions produced no alert but never checks known attacks. The team proposes: Test both benign and positive cases before accepting the detection classifier. Which security principle best explains the decision? Host action fields and connection fields represent different event types despite shared timestamps. Cross-sensor corroboration depends on time and entity alignment, not a matching display name. True negatives and false negatives cannot be distinguished without ground-truth test cases. Regex metacharacters have distinct syntax semantics from plain text literals. ExplanationCorrect Answer C:True negatives and false negatives cannot be distinguished without ground-truth test cases. The principle identifies the control actually at risk. Test both benign and positive cases before accepting the detection classifier. It should produce: Labeled benign sessions stay quiet and safe positive simulations produce the intended alerts. Incorrect Answers A:Host action fields and connection fields represent different event types despite shared timestamps. This does not establish the proposed intervention. The governing principle here is: True negatives and false negatives cannot be distinguished without ground-truth test cases. Apply it by: Test both benign and positive cases before accepting the detection classifier. B:Cross-sensor corroboration depends on time and entity alignment, not a matching display name. This does not establish the proposed intervention. The governing principle here is: True negatives and false negatives cannot be distinguished without ground-truth test cases. Apply it by: Test both benign and positive cases before accepting the detection classifier. D:Regex metacharacters have distinct syntax semantics from plain text literals. This does not establish the proposed intervention. The governing principle here is: True negatives and false negatives cannot be distinguished without ground-truth test cases. Apply it by: Test both benign and positive cases before accepting the detection classifier.
Question 120A small company relies entirely on software running on managed laptops, leaving unmanaged visitor devices unobserved. After the change — Add network-based controls for unmanaged access while retaining enrolled endpoint agents. — which result would best demonstrate that it worked? Managed endpoints report host actions and an unmanaged test device triggers the perimeter rule. A test incident retains source events, creates one correlated case and requires approved playbook approval. The register distinguishes vulnerable hosts, adversary capabilities and verified exploit telemetry. Known samples trigger signatures and an unknown safe behavioral simulation triggers the analytic. ExplanationCorrect Answer A:Managed endpoints report host actions and an unmanaged test device triggers the perimeter rule. This tests the affected component rather than an unrelated service. Agentless and agent-based approaches differ in coverage, enforcement depth and deployment prerequisites. Without the change, an unmanaged device could bypass host-only monitoring. Incorrect Answers B:Log management, SIEM analysis and SOAR actions are different operational functions. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Managed endpoints report host actions and an unmanaged test device triggers the perimeter rule. C:A vulnerability is an exposure, while a threat and exploit represent different risk elements. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Managed endpoints report host actions and an unmanaged test device triggers the perimeter rule. D:Rule-based signatures and behavior-based detection detect different classes of activity. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Managed endpoints report host actions and an unmanaged test device triggers the perimeter rule.