A user reports that their computer has become unusually slow. Which conclusion is best supported by this observation?
Malware Symptoms and Indicators Online Quiz Questions
Use this free practice quiz with 20 questions to review Malware Symptoms and Indicators, test your knowledge, and prepare for your next test or exam.
Select all the observations that are indicators: observable or recorded clues that can be examined.
- A
An unfamiliar process running on the device
- B
A user notices that the computer is slow
- C
An unexpected network connection
- D
A changed startup setting
A single malware indicator rarely proves that a system is infected.
- A
True
- B
False
What is the single term for an effect noticed by a user or administrator, such as a slow computer?
A single indicator rarely that malware has infected a system.
How can an analyst assess whether observations support a malware investigation while avoiding the conclusion that one clue proves infection?
Unusual outbound traffic is observed. Which classification is supported?
- A
It can only be a symptom, because it is visible.
- B
It can only be an indicator, because it involves network activity.
- C
It can be both a symptom and an indicator.
- D
It is proof that malware is responsible.
Select all statements that accurately describe how to assess observations that may indicate malware.
- A
A hardware fault can produce an observation that resembles a malware-related problem.
- B
A software bug or legitimate administrative activity can resemble suspicious activity.
- C
An unfamiliar process by itself establishes that malware is responsible.
- D
Comparing observations with a trusted baseline and correlating evidence from multiple sources can reduce false alarms.
A symptom and an indicator are always mutually exclusive categories.
- A
True
- B
False
What two-word reference should analysts compare observations with to help assess whether activity is unusual?
A symptom is an noticed by a user or administrator. An indicator is an observable or recorded that can be examined.
A computer crashes, and an unfamiliar process is also found. Which conclusion is best supported by these observations?
- A
A crash proves malware is present.
- B
An unfamiliar process proves malware is present.
- C
Either observation can justify investigation, but neither alone proves malware is responsible.
- D
Only a known-malicious file hash can justify investigation.
A single malware indicator is enough to prove that a system is infected.
- A
True
- B
False
What should analysts compare system observations with to help distinguish unusual activity from normal activity? Enter the two-word term.
Which observation is an example of a symptom rather than a recorded or observable clue such as a process or network connection?
- A
A changed startup setting
- B
A computer running slowly
- C
An unfamiliar process in a process record
- D
An unexpected network connection
Hardware faults, software bugs, and legitimate administrative activity can produce observations that resemble malware-related symptoms or indicators.
- A
True
- B
False
A known-malicious file hash is an example of what type of malware indicator? Enter the two-word indicator type.
Which approach best helps analysts assess observations while reducing false alarms?
- A
Treat every unexpected connection as proof of malware.
- B
Rely only on whether a domain has a suspicious reputation.
- C
Assume a familiar filename means a file is legitimate.
- D
Compare activity with a trusted baseline and correlate evidence from multiple sources.
What rarely proves infection by itself? Enter the three-word phrase.
Unusual outbound traffic is observed on a device. How may this observation be classified?
- A
It may be both a symptom and an indicator.
- B
It is always proof that malware is responsible.
- C
It is only a symptom and cannot be examined as evidence.
- D
It is only an indicator and cannot be noticed as an effect.
Related study packs and tools
1 Network Troubleshooting Method
A medium-difficulty quiz on applying a disciplined network troubleshooting workflow: defining symptoms, gathering evidence, testing hypotheses, verifying fixes, and documenting outcomes.
1 Network Troubleshooting Method
Learn a disciplined workflow for defining network problems, gathering evidence, testing likely causes, applying controlled fixes, and confirming and documenting the results.
2 Cabling and Physical Connectivity
Learn how to troubleshoot physical network connections, interpret cable-test results, and isolate cabling and port faults.
3 Network Access Control
A medium-difficulty quiz on applying network access-control principles, models, and policy rules.
3 Network Connectivity Diagnosis
A medium-difficulty quiz on diagnosing network connectivity in stages, interpreting test results, and choosing appropriate next checks.
4 Mobile Connectivity
A 14-question quiz on applying mobile connectivity concepts to common settings, usage, and troubleshooting situations.
4 Network Configuration Problems
Diagnose network configuration failures by checking client settings, VLANs, gateways, routes, DHCP, and DNS in a systematic order.
5 Mobile Device Configuration
Learn how to personalize a phone or tablet, configure accessibility and notifications, install operating-system updates, and maintain backups that can support recovery.
5 Network Services and Name Resolution
A medium-difficulty quiz on diagnosing DHCP, DNS, and network-service problems, progressing from core concepts to multi-step troubleshooting.
6 Security Operations and Incident Response
Learn how security teams monitor activity, manage vulnerabilities, respond to incidents, preserve digital evidence, and restore services safely.
7 Integrated Network Troubleshooting Practice
A practical guide to isolating network faults, choosing diagnostic tests, verifying recovery, and communicating results.
8 Comprehensive Security+ Practice and Review
A scenario-focused guide to Security+ SY0-701 concepts, emphasizing evidence-based incident response, access control, cryptography, vulnerability handling, recovery objectives, and risk governance.