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
An administrator needs to identify infected computers that require a restart to finish remediation of a threat.
What steps in the SEPM should an administrator perform to identify and restart the systems?
- A . View the Computer Status log to determine if any computers require a restart. Run a command from the Risk log to restart computers.
- B . View the SONAR log to determine if any computers require a restart. Run a command from the Computer Status log to restart computers.
- C . View the Computer Status log to determine if any computers require a restart. Run a command from the SONAR log to restart computers.
- D . View the Computer Status log to determine if any computers require a restart. Run a command from the Attack log to restart computers.
A
Explanation:
To identify computers that need a restart for completing threat remediation, the administrator should:
Steps for Identification and Action:
View the Computer Status log in the Symantec Endpoint Protection Manager (SEPM) to see if any computers are flagged as needing a restart.
Once identified, the administrator can go to the Risk log and run a command to initiate a restart on those systems, thereby completing the remediation process.
Why This Method is Effective:
The Computer Status log provides comprehensive information on the current state of each endpoint, including whether a restart is pending.
Risk log commands enable administrators to remotely trigger actions such as reboots on endpoints impacted by malware.
Why Other Options Are Incorrect:
Other options suggest using logs like SONAR or Attack logs to trigger restarts, which do not provide the necessary functionality for identifying and restarting systems in need of final remediation.
Reference: Using the Computer Status log along with the Risk log in SEPM ensures administrators can efficiently identify and restart infected systems.
The Behavioral Heat Map indicates that a specific application and a specific behavior are never used together.
What action can be safely set for the application behavior in a Behavioral Isolation policy?
- A . Deny
- B . Allow
- C . Delete
- D . Monitor
A
Explanation:
In Symantec EDR’s Behavioral Isolation policy, if the Behavioral Heat Map indicates that a specific application and a particular behavior are never used together, setting the action to Deny for that application behavior is a safe response. This prevents potential misuse by blocking the unusual behavior, which could indicate a security risk.
Rationale for Denying the Behavior:
If historical data shows that this behavior does not normally occur with the application, it suggests that any attempt to initiate it could be anomalous or malicious. Blocking this behavior helps prevent unexpected activities that could be exploited by threats.
Why Other Actions Are Less Appropriate:
Allow (Option B) would permit potentially risky behavior.
Delete (Option C) does not apply in this context, as it is not an action for behavior control. Monitor (Option D) would only log the behavior but does not provide active protection, which is critical when the behavior is atypical.
Reference: Setting a Deny action based on Behavioral Heat Map insights aligns with best practices for proactive threat prevention in Symantec EDR.
An organization identifies a threat in its environment and needs to limit the spread of the threat.
How should the SEP Administrator block the threat using Application and Device Control?
- A . Gather the MD5 hash of the file and create an Application Content Rule that blocks the file based on the file fingerprint.
- B . Gather the process name of the file and create an Application Content Rule that blocks the file based on the device ID type.
- C . Gather the MD5 hash of the file and create an Application Content Rule that uses regular expression matching.
- D . Gather the MD5 hash of the file and create an Application Content Rule that blocks the file based on specific arguments.
A
Explanation:
When a threat is detected within an organization’s environment, preventing its spread becomes crucial. Symantec Endpoint Protection (SEP) allows administrators to create Application and Device Control policies that target specific threat files to block them across the network. To block a known malicious file, the administrator should:
Identify the File MD5 Hash: The MD5 hash serves as a unique "fingerprint" for the malicious file, ensuring that the specific file version can be accurately identified across systems.
Create an Application Content Rule: Using the Application and Device Control feature, the administrator can create a content rule that targets the identified file by its MD5 hash, effectively blocking it based on its fingerprint.
Apply the Rule Across Endpoints: Once created, this rule is applied to endpoints, preventing the file from executing or spreading.
This method ensures precise blocking of the threat without impacting other files or processes.
How does an administrator view all devices impacted by a suspicious file?
- A . From the Alerts and Events list, select Files; then, from the file list, select Devices.
- B . From the Discovered Items list, select Devices.
- C . From the Discovered Items list, select the file; then, from the Details page, select Devices.
- D . From the Alerts and Event list, select Device.
C
Explanation:
To view all devices impacted by a suspicious file, the administrator should go to the Discovered Items list, select the specific file, and then view the impacted devices from the Details page.
Steps to View Impacted Devices:
Navigate to the Discovered Items list within the management console.
Locate and select the suspicious file in question to open its Details page.
On the Details page, a list of devices associated with the file is displayed, providing insights into which endpoints are potentially impacted by the suspicious activity.
Why Other Options Are Less Suitable:
Options A and B do not provide the specific device list for a selected file.
Option D is incorrect as it implies selecting by device first rather than by suspicious file.
Reference: The Discovered Items list and file-specific Details page allow administrators to trace a file’s footprint across multiple devices.
A Symantec Endpoint Protection (SEP) client uses a management server list with three management servers in the priority 1 list.
Which mechanism does the SEP client use to select an alternate management server if the currently selected management server is unavailable?
- A . The client chooses another server in the list randomly.
- B . The client chooses a server based on the lowest server load.
- C . The client chooses a server with the next highest IP address.
- D . The client chooses the next server alphabetically by server name.
A
Explanation:
When a Symantec Endpoint Protection (SEP) client has multiple management servers listed in its priority 1 list and the currently selected management server becomes unavailable, the SEP client randomly selects another server from the list. This randomized selection helps distribute load among the available servers and ensures continuity of management services.
Mechanism of Random Selection:
By choosing the next server randomly, SEP clients help balance the load across available servers, avoiding potential bottlenecks.
This method also ensures that the client can quickly connect to an alternative server without
requiring additional logic for server selection.
Why Other Options Are Incorrect:
SEP clients do not evaluate server load (Option B), IP addresses (Option C), or alphabetical order (Option D) when selecting an alternate server.
Reference: The SEP client’s randomized approach to selecting management servers ensures efficient load distribution and server availability.
Which device page should an administrator view to track the progress of an issued device command?
- A . Command History
- B . Activity Update
- C . Command Status
- D . Recent Activity
C
Explanation:
The Command Status page is where an administrator should track the progress of issued device commands in Symantec Endpoint Security.
This page provides:
Real-Time Command Updates: It shows the current status of commands, such as "Pending," "Completed," or "Failed," providing immediate insights into the command’s execution. Detailed Progress Tracking: Command Status logs offer details on each command, enabling the administrator to confirm that actions, such as scans, updates, or reboots, have been successfully processed by the endpoint.
The Command Status page is essential for effective device management, as it helps administrators monitor and verify the outcome of their issued commands.
How would an administrator specify which remote consoles and servers have access to the management server?
- A . Edit the Server Properties and under the General tab, change the Server Communication Permission.
- B . Edit the Communication Settings for the Group under the Clients tab.
- C . Edit the External Communication Settings for the Group under the Clients tab.
- D . Edit the Site Properties and under the General tab, change the server priority.
A
Explanation:
To control which remote consoles and servers have access to the Symantec Endpoint Protection Management (SEPM) server, an administrator should edit the Server Properties and adjust the Server Communication Permission under the General tab. This setting specifies which remote systems are authorized to communicate with the management server, enhancing security by limiting access to trusted consoles and servers only. Adjusting the Server Communication Permission helps manage server access centrally and ensures only approved systems interact with the management server.
Which two (2) instances could cause Symantec Endpoint Protection to be unable to remediate a file? (Select two.)
- A . Another scan is in progress.
- B . The detected file is in use.
- C . There are insufficient file permissions.
- D . The file is marked for deletion by Windows on restart.
- E . The file has good reputation.
BC
Explanation:
Symantec Endpoint Protection (SEP) may be unable to remediate a file in certain situations.
Two primary reasons for this failure are:
The detected file is in use (Option B): When a file is actively being used by the system or an application, SEP cannot remediate or delete it until it is no longer in use. Active files are locked by the operating system, preventing modification.
Insufficient file permissions (Option C): SEP needs adequate permissions to access and modify files. If SEP does not have the necessary permissions for the detected file, it cannot perform remediation.
Why Other Options Are Incorrect:
Another scan in progress (Option A) does not directly prevent remediation.
File marked for deletion on restart (Option D) would typically allow SEP to complete the deletion
upon reboot.
File with good reputation (Option E) is less likely to be flagged for remediation but would not prevent it if flagged.
Reference: File in-use status and insufficient permissions are common causes of remediation failure in SEP environments.
What should an administrator know regarding the differences between a Domain and a Tenant in ICDm?
- A . A tenant can contain multiple domains
- B . Each customer can have one domain and many tenants
- C . A domain can contain multiple tenants
- D . Each customer can have one tenant and no domains
A
Explanation:
In Integrated Cyber Defense Manager (ICDm), a tenant can encompass multiple domains, allowing organizations with complex structures to manage security across various groups or departments within a single tenant. Each tenant represents an overarching entity, while domains within a tenant enable separate administration and policy enforcement for different segments, providing flexibility in security management across large enterprises.
Which type of security threat continues to threaten endpoint security after a system reboot?
- A . file-less
- B . memory attack
- C . script
- D . Rootkit
D
Explanation:
A Rootkit is a type of security threat that can persist across system reboots, making it difficult to detect and remove. Rootkits operate by embedding themselves deep within the operating system, often at the kernel level, and they can disguise their presence by intercepting and modifying standard operating system functionality. Here’s how they maintain persistence:
Kernel-Level Integration: Rootkits modify core operating system files, allowing them to load during the boot process and remain active after reboots.
Stealth Techniques: By hiding from regular security checks, rootkits avoid detection by conventional anti-virus and anti-malware tools.
Persistence Mechanism: The modifications rootkits make ensure they start up again after each reboot, enabling continuous threat activity on the compromised system.
Due to their persistence and stealth, rootkits present significant challenges for endpoint security.