350-201(NEW-127Q) · Question #77
A large amount of malicious spam was detected with suspicious attachments. The attachments are being automatically submitted to a free online malware analysis resource for review. Before all the…
The correct answer is D. The site has a rate limit that has been exceeded. Rate limiting is the reason the process stops: free online malware analysis services (like VirusTotal) impose submission quotas - often per minute or per day - to prevent abuse and manage server load. Once that quota is hit, the API or upload mechanism rejects further requests…
Question
Options
- AInsufficient local system resources caused a slow-down.
- BThe available local network bandwidth has been exceeded.
- CAn attachment in an unknown format caused a hang of the process.
- DThe site has a rate limit that has been exceeded.
How the community answered
(32 responses)- A3% (1)
- B13% (4)
- C6% (2)
- D78% (25)
Explanation
Rate limiting is the reason the process stops: free online malware analysis services (like VirusTotal) impose submission quotas - often per minute or per day - to prevent abuse and manage server load. Once that quota is hit, the API or upload mechanism rejects further requests, halting the automated process entirely.
Why the distractors are wrong:
- A (local system resources): A slow-down due to CPU/RAM constraints would cause the process to slow, not stop abruptly - and local resources are unrelated to a remote service's behavior.
- B (network bandwidth): Bandwidth exhaustion would degrade throughput gradually, not cause a clean stop, and spam attachments are typically small files.
- C (unknown format): A well-engineered submission tool would either skip or log unrecognized formats rather than hang; even if it did hang, that would affect one attachment, not terminate the entire batch process the same way rate limiting would.
Memory tip: Think "free = limited." Any free online service enforces rate limits to protect itself from being overwhelmed - if an automated process suddenly stops mid-batch, the culprit is almost always the service's quota, not your local machine.
Topics
Community Discussion
No community discussion yet for this question.