CompTIA Updated CY0-001 Exam Questions and Answers by damien

Basic Concept: Responsible AI encompasses a set of principles designed to ensure AI systems operate ethically, fairly, and accountably. These principles guide AI development and deployment to minimize harm and maximize trustworthiness. CompTIA SecAI+ Exam Objectives list transparency and explainability as foundational responsible AI principles under Domain 4.

Why B is Correct: Transparency and explainability are cornerstone principles of responsible AI. Transparency means AI systems are open about their nature, capabilities, limitations, and how they make decisions. Explainability means the system can articulate the reasons behind its decisions in human-understandable terms. Together, they enable accountability, support regulatory compliance, allow bias detection, and build user trust. The CompTIA SecAI+ Study Guide and responsible AI frameworks including OECD and NIST AI RMF consistently identify this as a key principle.

Why A is Wrong: Using protected data for training would violate privacy and intellectual property rights. This is not a responsible AI principle — responsible AI actually requires ensuring that training data respects privacy, consent, and legal protections.

Why C is Wrong: Human-in-the-loop is an important operational practice for high-stakes AI decisions, but it is one design pattern rather than the key overarching principle of responsible AI. Not all responsible AI systems require human-in-the-loop operation for every decision.

Why D is Wrong: Maximizing model security is a cybersecurity objective for AI systems. While important, it is an operational security concern rather than a responsible AI governance principle focused on fairness, accountability, and trustworthiness in AI decision-making.

OWASP is the best answer because it publishes the Top 10 for Large Language Model Applications, a resource specifically structured around significant security vulnerabilities and attack patterns affecting LLM-based applications. CompTIA SecAI+ Objective 2.1 directly lists the OWASP Top 10 and specifically the LLM Top 10 as an AI threat-modeling resource. MITRE ATLAS is also highly relevant to AI security, but its purpose is broader: it catalogs adversarial tactics, techniques, and procedures associated with attacks against AI and machine learning systems. The MIT AI Risk Repository aggregates a broad range of AI risks rather than functioning as the recognized LLM application vulnerability Top 10. NIST AI RMF provides a risk-management framework for governing and managing AI risks but is not primarily a vulnerability catalog for LLM applications. Since the question asks for the resource that most directly captures widely recognized threat vectors and common vulnerabilities associated specifically with LLM applications, OWASP ' s LLM-focused Top 10 is the most precise match.

Basic Concept: Operating AI systems within a budget requires direct control over the primary cost driver of LLM usage. For research environments where users may run extensive queries, token consumption management is the most effective budget control mechanism. CompTIA SecAI+ Study Guide covers token limits as the key cost management control for AI environments.

Why D is Correct: Token limits set hard caps on the maximum tokens consumed per request and per session, directly controlling the per-interaction cost of LLM API usage. In a research environment where users may submit complex, multi-part queries generating long responses, token limits prevent any single interaction from consuming disproportionate budget and enable the administrator to enforce aggregate budget constraints across all users and research activities.

Why A is Wrong: Prompt firewalls inspect and filter prompt content for security and policy compliance. They are security controls designed to prevent malicious or policy-violating prompts, not financial controls for managing token consumption or enforcing budget limits.

Why B is Wrong: API access controls manage authentication and authorization for API interactions, governing who can connect to the AI API. While restricting API access could limit who uses the system, it does not control how much budget individual authorized users consume through their research queries.

Why C is Wrong: Model guardrails enforce content policy and behavioral constraints on model inputs and outputs. They ensure safe and appropriate responses but do not limit the computational resources or tokens consumed by interactions, making them unsuitable as budget enforcement controls.

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.