Broadcom 250-580 Practice Exams
Last updated on Nov 16,2026- Exam Code: 250-580
- Exam Name: Endpoint Security Complete - R2 Technical Specialist
- Certification Provider: Broadcom
- Latest update: Nov 16,2026
Why is it important for an Incident Responder to search for suspicious registry and system file changes when threat hunting?
- A . Attackers can establish persistence within an infected host
- B . Attackers can trick users into giving up their enterprise credentials
- C . Attackers may shadow valid sessions and inject hidden actions
- D . Attackers may cause unusual DNS requests
A
Explanation:
When threat hunting, it is important for an Incident Responder to search for suspicious registry and system file changes because attackers can use these modifications to establish persistence within an infected host. Persistence allows attackers to maintain control over the compromised system, even after reboots or security updates.
Persistence via Registry and System Files:
Attackers often modify registry keys or add malicious files in system directories to ensure their malware automatically starts with the system.
By establishing persistence, attackers can retain their foothold in the system, making it more difficult for security teams to fully eradicate the threat.
Why Other Options Are Incorrect:
While attackers may attempt to trick users (Option B), shadow sessions (Option C), or cause DNS anomalies (Option D), registry and system file changes are primarily associated with persistence techniques.
Reference: Checking for persistence mechanisms is a critical part of threat hunting, as these often involve registry and system file modifications.
What is the result of disjointed telemetry collection methods used within an organization?
- A . Investigators lack granular visibility
- B . Back of orchestration across controls
- C . False positives are seen
- D . Attacks continue to spread during investigation
A
Explanation:
Disjointed telemetry collection within an organization can result in a lack of granular visibility for investigators. Here’s why this is problematic:
Incomplete Data: Disjointed collection methods lead to fragmented data, making it difficult for security teams to get a complete picture of incidents.
Reduced Investigation Efficiency: Without granular and cohesive telemetry, investigators struggle to trace the attack’s path accurately, slowing down response times.
Increased Risk of Missing Key Indicators: Critical indicators of compromise may be overlooked, allowing threats to persist or re-emerge in the environment.
Unified telemetry is essential for thorough and efficient investigations, as it provides the detailed insights necessary to understand and mitigate threats fully.
A file has been identified as malicious.
Which feature of SEDR allows an administrator to manually block a specific file hash?
- A . Playbooks
- B . Quarantine
- C . Allow List
- D . Block List
D
Explanation:
In Symantec Endpoint Detection and Response (SEDR), the Block List feature allows administrators to manually block a specific file hash identified as malicious. By adding the hash of the malicious file to the Block List, SEDR ensures that the file cannot execute or interact with the network, preventing further harm. This manual blocking capability provides administrators with direct control over specific threats detected in their environment.
How does Memory Exploit Mitigation protect applications?
- A . Injects a DLL (IPSEng32.dll or IPSEng64.dll) into protected processes and when an exploit attempt is detected, terminates the protected process to prevent the malicious code from running.
- B . Injects a DLL (UMEngx86.dll) into applications that run in user mode and if the application behaves maliciously, then SEP detects it.
- C . Injects a DLL (sysfer.dll) into processes being launched on the machine and if the process isn’t trusted, prevents the process from running.
- D . Injects a DLL (IPSEng32.dll) into browser processes and protects the machine from drive-by downloads.
A
Explanation:
Memory Exploit Mitigation in Symantec Endpoint Protection (SEP) works by injecting a DLL (Dynamic Link Library) ― specifically, IPSEng32.dll for 32-bit processes or IPSEng64.dll for 64-bit processes ― into applications that require protection.
Here’s how it works: DLL Injection:
When Memory Exploit Mitigation is enabled, SEP injects IPSEng DLLs into processes that it monitors for potential exploit attempts.
This injection allows SEP to monitor the behavior of the process at a low level, enabling it to detect
exploit attempts on protected applications.
Exploit Detection and Response:
If an exploit attempt is detected within a protected process, SEP will terminate the process immediately. This termination prevents malicious code from running, stopping potential exploit actions from completing.
Why This Approach is Effective:
By terminating the process upon exploit detection, SEP prevents any code injected or manipulated by an exploit from executing. This proactive approach effectively stops many types of memory-based attacks, such as buffer overflows, before they can harm the system. Clarification on Other Options:
Option B (UMEngx86.dll) pertains to user-mode protection, which isn’t used for Memory Exploit Mitigation.
Option C (sysfer.dll) is involved in file system driver activities, not direct exploit prevention. Option D is partially correct about IPSEng32.dll but inaccurately specifies that it’s for browser processes only; the DLL is used for multiple types of processes.
Reference: The use of IPSEng DLL injection for Memory Exploit Mitigation is detailed in Symantec Endpoint Protection’s advanced application protection mechanisms outlined in the SEP documentation.
Which alert rule category includes events that are generated about the cloud console?
- A . Security
- B . System
- C . Diagnostic
- D . Application Activity
B
Explanation:
The System alert rule category includes events generated about the cloud console. These alerts relate to system-level activities within the management console, such as administrative actions, system health checks, and other essential notifications related to console operations.
Types of Alerts in System Category:
System alerts cover activities directly associated with the console and infrastructure, ensuring that administrators are informed of significant changes or issues affecting the management platform itself.
Why Other Options Are Incorrect:
Security (Option A) focuses on potential threats and security events.
Diagnostic (Option C) involves troubleshooting information but does not specifically cover console events.
Application Activity (Option D) pertains to application-specific events rather than console-level notifications.
Reference: System alerts provide visibility into cloud console-related events, crucial for managing and maintaining the console’s operational integrity.
Which technique randomizes the memory address map with Memory Exploit Mitigation?
- A . ForceDEP
- B . SEHOP
- C . ASLR
- D . ROPHEAP
C
Explanation:
ASLR (Address Space Layout Randomization) is a security technique used in Memory Exploit Mitigation that randomizes the memory address map for processes. By placing key data areas at random locations in memory, ASLR makes it more difficult for attackers to predict the locations of specific functions or buffers, thus preventing exploitation techniques that rely on fixed memory addresses.
How ASLR Enhances Security:
ASLR rearranges the location of executable code, heap, stack, and libraries each time a program is run, thwarting attacks that depend on known memory locations.
Why Other Options Are Incorrect:
ForceDEP (Option A) enforces Data Execution Prevention but does not randomize addresses. SEHOP (Option B) mitigates exploits by protecting exception handling but does not involve address randomization.
ROPHEAP (Option D) refers to Return-Oriented Programming attacks rather than a mitigation technique.
Reference: ASLR is a widely used method in Memory Exploit Mitigation, adding randomness to memory locations to reduce vulnerability to exploitation.
What is the difference between running Device Control for a Mac versus Windows?
- A . Mac Device Control runs at the driver level. It enforces control only on Apple supported devices.
- B . Mac Device Control runs at the volume level. It enforces control only on storage devices. O
- C . Mac Device Control runs at the kernel level. It enforces control only on built-in devices.
- D . Mac Device Control runs at the user level. It enforces control only on iCIoud storage.
B
Explanation:
Device Control operates differently on Mac compared to Windows in Symantec Endpoint Protection:
Mac Device Control Functionality:
On macOS, Device Control operates at the volume level, specifically targeting storage devices. This volume-level control means that SEP enforces policies on storage devices like external drives, USB storage, or other mounted storage volumes rather than peripheral devices in general. Platform Differences:
On Windows, Device Control can operate at a more granular level (driver level), allowing enforcement across a broader range of devices, including non-storage peripherals.
Why Other Options Are Incorrect:
Option A (driver level) is incorrect for Mac, as SEP does not control non-storage device drivers on macOS.
Option C (kernel level) and D (user level) incorrectly describe the control layer and do not accurately reflect SEP’s enforcement scope on Mac.
Reference: The device control implementation on macOS, specifically focusing on volume-based storage device control, is part of SEP’s cross-platform device management features.
The SES Intrusion Prevention System has blocked an intruder’s attempt to establish an IRC connection inside the firewall.
Which Advanced Firewall Protection setting should an administrator enable to prevent the intruder’s system from communicating with the network after the IPS detection?
- A . Enable port scan detection
- B . Automatically block an attacker’s IP address
- C . Block all traffic until the firewall starts and after the firewall stops
- D . Enable denial of service detection
B
Explanation:
To enhance security and prevent further attempts from the intruder after the Intrusion Prevention System (IPS) has detected and blocked an attack, the administrator should enable the setting to Automatically block an attacker’s IP address.
Here’s why this setting is critical:
Immediate Action Against Threats: By automatically blocking the IP address of the detected attacker, the firewall can prevent any further communication attempts from that address. This helps to mitigate the risk of subsequent attacks or reconnections.
Proactive Defense Mechanism: Enabling this feature serves as a proactive defense strategy, minimizing the chances of successful future intrusions by making it harder for the attacker to re-establish a connection to the network.
Reduction of Administrative Overhead: Automating this response allows the security team to focus on investigating and remediating the incident rather than manually tracking and blocking malicious IP addresses, thus optimizing incident response workflows.
Layered Security Approach: This setting complements other security measures, such as intrusion detection and port scan detection, creating a layered security approach that enhances overall network security.
Enabling automatic blocking of an attacker’s IP address directly addresses the immediate risk posed by the detected intrusion and reinforces the organization’s defense posture against future threats.
Which action must a Symantec Endpoint Protection administrator take before creating custom Intrusion Prevention signatures?
- A . Change the custom signature order
- B . Create a Custom Intrusion Prevention Signature library
- C . Define signature variables
- D . Enable signature logging
C
Explanation:
Before creating custom Intrusion Prevention signatures, a Symantec Endpoint Protection (SEP)
administrator must define signature variables. Defining these variables allows for the customization
of specific values (such as IP addresses or port numbers) used within the custom signatures, enabling
flexibility and precision in threat detection.
Role of Signature Variables:
Signature variables allow administrators to adapt custom signatures to specific needs by defining parameters that can be reused across multiple signatures.
This initial step is crucial for ensuring that the custom signature functions correctly and targets the
desired threat or network behavior.
Why Other Options Are Incorrect:
Changing custom signature order (Option A) is done after creating signatures.
Creating a Custom Intrusion Prevention Signature library (Option B) is not required as a preliminary action.
Enabling signature logging (Option D) is optional for monitoring purposes but is not a prerequisite for creating custom signatures.
Reference: Defining signature variables is an essential preparatory step for creating effective custom Intrusion Prevention signatures in SEP.
What is the purpose of a Threat Defense for Active Directory Deceptive Account?
- A . It prevents attackers from reading the contents of the Domain Admins Group.
- B . It assigns a fake NTLM password hash value for users with an assigned AdminCount attribute.
- C . It exposes attackers as they seek to gather credential information from workstation memory.
- D . It acts as a honeypot to expose attackers as they attempt to build their AD treasure map
D
Explanation:
The Threat Defense for Active Directory (AD) Deceptive Account feature serves as a honeypot within Active Directory, designed to lure attackers who are attempting to map out AD for valuable accounts or resources. By using deceptive accounts, this feature can expose attackers’ reconnaissance activities, such as attempts to gather credential information or access sensitive accounts. This strategy helps detect attackers early by observing interactions with fake accounts set up to appear as attractive targets.