CompTIA Updated CY0-001 Exam Questions and Answers by niall

Basic Concept: A denial-of-wallet (DoW) attack deliberately generates excessive API calls or token consumption to exhaust an organization ' s AI budget. Since LLM providers charge based on tokens processed, attackers can cause significant financial damage by driving massive usage. CompTIA SecAI+ Study Guide addresses financial abuse vectors in AI systems.

Why E is Correct: API rate controls limit the number of requests a user or application can make within a defined time period. By capping request frequency, rate controls directly prevent attackers from generating the massive API call volume needed to execute a denial-of-wallet attack.

Why F is Correct: Output token controls cap the maximum number of tokens the model can generate per response. Since billing is based on tokens consumed including outputs, limiting output tokens directly caps the cost per request, preventing attackers from triggering extremely long, expensive responses.

Why A is Wrong: Endpoint access controls manage device or network access. They do not directly limit token consumption or API call volume that drives denial-of-wallet costs.

Why B is Wrong: A CDN distributes content geographically to improve performance and absorb traffic. It does not control LLM API billing or token consumption.

Why C is Wrong: Model fine-tuning adjusts model parameters for improved performance on specific tasks. It is a training process that does not address active cost-exhaustion attacks.

Why D is Wrong: Modality controls restrict which input types such as text, images, or audio a model accepts. While useful for reducing attack surface, they do not directly address the rate or volume of API calls in a DoW attack.

Basic Concept: Context window DoS attacks flood an LLM ' s context with obfuscated content to exhaust processing resources or manipulate model behavior. Attackers may hide large amounts of text behind Unicode characters like emojis. CompTIA SecAI+ Study Guide identifies prompt filtering as the primary defense against input-based attacks on LLMs.

Why D is Correct: A prompt filter inspects incoming inputs before they reach the LLM, detecting and blocking malicious content including obfuscated text hidden behind Unicode characters or emojis. By analyzing input structure, character counts, hidden content, and encoding anomalies, prompt filters can identify and reject attacks that attempt to abuse the context window, preventing resource exhaustion.

Why A is Wrong: Fraud detection systems are designed to identify fraudulent transactions or activities in structured data contexts. They are not designed to inspect LLM prompt structures for obfuscated content attacks on context windows.

Why B is Wrong: LLM-as-a-judge uses a secondary LLM to evaluate the quality or safety of another model ' s outputs. It operates post-generation and cannot prevent a DoS attack that occurs during input processing before output is generated.

Why C is Wrong: Pattern recognition can identify known attack patterns but requires the attack to match pre-learned patterns. Novel obfuscation techniques using Unicode or emoji hiding may evade pattern-based detection without dedicated prompt filtering logic.

Option D is correct because behavioral anomaly detection requires a persistent baseline of normal user activity and a repeatable method for measuring departures from that baseline. Automated playbooks can continuously collect authentication, endpoint, network, and application events, calculate deviations such as unusual login times, abnormal resource access, or atypical transaction volume, and escalate activity that exceeds defined thresholds. Standard-deviation-based comparison is broader and more defensible than searching for a username or checking a single data source. Option A provides only a permissions comparison at one point in time; it does not establish how the user normally behaves. Option B searches log occurrences but lacks behavioral context, trend analysis, and reliable anomaly scoring. Option C observes only browser activity and therefore misses anomalies in identity, host, cloud, and business systems. A mature implementation should tune baselines, account for role and seasonality, and retain analyst review so legitimate changes are not treated as malicious. This aligns with AI-assisted security concepts involving user and entity behavior analytics, automated enrichment, and risk-based triage.

================

Basic Concept: Responsible AI principles each address different aspects of trustworthy AI behavior. When stakeholders are concerned about both bias and inconsistency — specifically that the same or equivalent work might receive different treatment from the AI system — the principle of consistency is most directly relevant. CompTIA SecAI+ covers responsible AI principles under governance.

Why C is Correct: Consistency in AI systems means the model applies the same rules, standards, and decision criteria uniformly across all inputs and user groups without variation based on characteristics unrelated to the task. An AI plagiarism detection system that produces inconsistent results across different student submissions or demographic groups fails the consistency principle, which directly addresses both the bias concern (differential treatment) and inconsistency concern the faculty have raised.

Why A is Wrong: Transparency relates to openness about how the AI system works and what data it uses. While valuable for understanding the system, transparency alone does not ensure that the system applies its rules uniformly or consistently.

Why B is Wrong: Explainability means the system can articulate why it made a particular decision. While useful for understanding individual cases, it does not guarantee that decisions are made with equal consistency across different submissions or groups.

Why D is Wrong: Accountability identifies who is responsible for AI system decisions and outcomes. It is a governance principle about ownership and responsibility rather than about ensuring uniform application of evaluation criteria.