Download Latest CY0-001 Questions

Basic Concept: Class imbalance in training data — where some categories have significantly more examples than others — causes ML models to be biased toward the majority class, producing poor detection of minority class threats. Addressing this imbalance before training is critical for threat classification accuracy. CompTIA SecAI+ covers data preparation techniques under basic AI concepts.

Why B is Correct: Data augmentation addresses class imbalance by artificially increasing the number of training samples in under-represented classes. Techniques include oversampling minority classes by creating synthetic examples using methods like SMOTE (Synthetic Minority Over-sampling Technique), or undersampling majority classes. This balances label distribution and enables the model to learn decision boundaries that accurately classify all threat categories, not just the dominant ones.

Why A is Wrong: Data lineage documents the origin, movement, and transformation of data throughout its lifecycle. It provides traceability and auditability but does not address class imbalance in training data distribution.

Why C is Wrong: Data provenance records the history and context of data origins. Like lineage, it is a governance and tracking concept that does not alter data distribution for model training balance.

Why D is Wrong: Data verification confirms that data is correct and consistent with expected formats and values. It checks data quality and integrity but does not address the statistical distribution imbalance between threat classes in training datasets.

Basic Concept: AI systems that rely on knowledge bases, vector databases, or reference documents are vulnerable to attacks that corrupt or manipulate that source data. When an adversary deliberately modifies the data an AI uses, this is a form of data poisoning. CompTIA SecAI+ Study Guide covers data poisoning as a core AI vulnerability.

Why C is Correct: Data poisoning is an attack where an adversary intentionally corrupts or manipulates the data that an AI system uses for training, inference, or reference. In this scenario, the employee modified the company policies document that the chatbot uses as its knowledge base, causing the chatbot to provide incorrect, misleading, or confusing information to users. This is a classic indirect data poisoning attack targeting the AI ' s reference data rather than its model weights.

Why A is Wrong: Data reduction refers to techniques that decrease the volume or dimensionality of data for processing efficiency. It is a data engineering concept, not an attack vector or vulnerability classification.

Why B is Wrong: Data masking replaces sensitive data values with anonymized equivalents to protect privacy. It is a data protection control used legitimately, not an attack that an employee would exploit to cause disruption.

Why D is Wrong: Data leaking involves unauthorized disclosure of sensitive information from an AI system or its associated data stores. The employee ' s action of manipulating data is an integrity attack, not a confidentiality violation involving leakage of data to unauthorized parties.

Basic Concept: AI can augment SOC operations in various ways, but the most appropriate uses maintain human oversight and leverage AI ' s natural language understanding to reduce cognitive load on analysts. CompTIA SecAI+ Study Guide identifies alert summarization as a high-value, low-risk AI application for SOC enhancement.

Why D is Correct: AI-powered alert summarization consolidates complex, high-volume security alerts into concise, actionable insights, helping analysts rapidly understand threats without reading extensive raw log data. This is a safe, bounded AI application that enhances analyst efficiency while preserving human decision-making authority, directly addressing the volume and complexity challenges SOCs face.

Why A is Wrong: Generating and executing code directly in production without human review introduces serious risk. AI-generated code may contain errors, security vulnerabilities, or unintended side effects that could disrupt or compromise production systems.

Why B is Wrong: Enabling an AI assistant to act autonomously with no human intervention violates the human-in-the-loop principle. Autonomous AI in a SOC without oversight could incorrectly contain legitimate systems, miss actual threats, or make consequential decisions without accountability.

Why C is Wrong: Deploying open-source models directly in production without proper vetting, security hardening, and compliance review introduces supply chain risk, model reliability concerns, and potential intellectual property issues into sensitive security operations.

Basic Concept: AI chatbot operational costs are primarily driven by token consumption — the number of tokens processed in requests and generated in responses. Unexpected cost increases in LLM-based chatbots almost always trace back to abnormal token usage patterns. CompTIA SecAI+ Study Guide covers AI cost monitoring and token-based billing under securing AI systems.

Why D is Correct: Model token usage logs directly show how many tokens are being consumed per request, by which users or endpoints, and whether usage has increased abnormally. Examining token usage data is the most direct path to identifying the root cause of unexpected cost increases — whether from a denial-of-wallet attack, user abuse, a new feature generating verbose responses, or legitimate organic growth in usage. This is the first and most relevant examination point for LLM cost analysis.

Why A is Wrong: Firewall logs capture network-level traffic information. While they can reveal unusual access patterns or volumes, they do not contain token consumption data that directly explains LLM billing increases.

Why B is Wrong: WAF rules define filtering policies for web traffic. Reviewing rule configurations does not reveal whether token usage has increased or why costs have risen; it shows security policy settings rather than consumption metrics.

Why C is Wrong: Vector database IOPS performance measures how quickly the database processes read and write operations. While relevant to RAG system performance, IOPS metrics do not directly explain LLM API cost increases driven by token consumption.