CY0-001 Sample Questions Answers

Basic Concept: This is a Performance-Based Question (PBQ) — a HOTSPOT/simulation item requiring interactive selection in the actual exam. It tests the candidate ' s ability to map appropriate security controls to AI system components such as API gateway, model endpoint, data layer, and authentication layer.

Key Concept — Appropriate Controls by Component: For an API gateway connecting an AI system, typical controls include API key authentication, rate limiting, TLS encryption, and input validation. For the model endpoint, controls include IAM role-based access, audit logging, and guardrails. For data access components, encryption at rest and data masking are appropriate. For the authentication layer, MFA and expiring session tokens are relevant.

Why This Matters: The CompTIA SecAI+ Study Guide emphasizes defense-in-depth for AI system integration, ensuring each architectural layer has dedicated, appropriate security controls. The principle of least privilege should guide access control assignments at each component, while availability controls such as rate limiting protect against abuse.

The OWASP Top 10 for Large Language Model Applications is the most directly applicable resource because the system under review is an AI chatbot based on LLM technology. CompTIA SecAI+ Objective 2.1 explicitly identifies the OWASP Top 10, including the LLM Top 10, as an AI threat-modeling resource. It addresses security risks specifically associated with LLM applications, including prompt injection, sensitive information disclosure, insecure output handling, excessive agency, and other AI-specific application threats. ISO 27001 provides a broader information security management framework and is valuable for organizational security governance, but it is not specifically designed to enumerate LLM attack vectors. The EU AI Act primarily addresses regulatory obligations, risk classifications, and governance requirements rather than serving as a technical LLM threat-assessment checklist. Option A is also not the appropriate LLM-specific resource. For a security architect who needs systematic technical coverage of threats affecting an AI chatbot, the OWASP LLM Top 10 provides the most targeted framework among the listed options.

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

Basic Concept: ISO develops management system standards for various organizational domains. For organizations building and managing AI systems in a structured, compliant manner, the appropriate ISO standard must specifically address the unique requirements of AI management systems including risk governance, lifecycle management, and accountability. CompTIA SecAI+ Exam Objectives cover ISO standards applicable to AI governance.

Why D is Correct: ISO 42001 (Artificial Intelligence Management System — AIMS) is the international standard specifically designed for building and managing AI management systems. It provides compliance requirements and guidance for establishing, implementing, maintaining, and continually improving an organization ' s AI management system, addressing AI-specific concerns including risk management, AI system governance, accountability, transparency, and continuous improvement for AI applications.

Why A is Wrong: ISO 20000 is the Information Technology Service Management (ITSM) standard covering IT service delivery processes, SLAs, incident management, and change management. It is not an AI management standard and does not address AI-specific governance requirements.

Why B is Wrong: ISO 27001 is the Information Security Management System (ISMS) standard addressing organizational information security risk management through controls and policies. While relevant to data security in AI systems, it does not contain requirements specifically for building an AI management system.

Why C is Wrong: ISO 27018 is a code of practice for protection of personally identifiable information (PII) in public cloud computing environments, extending ISO 27001 for cloud privacy. It addresses cloud PII protection rather than AI system management compliance requirements.

Basic Concept: When authentication is enabled on an LLM system, users must prove their identity before the system processes any requests. The authentication process must occur at the point where users first attempt to access the system before any data can be transmitted. CompTIA SecAI+ Study Guide covers the order of authentication controls in AI system access architectures.

Why B is Correct: Endpoint access control is the first requirement when authentication is enabled, as it governs the initial connection from the user ' s device to the system. Before any prompt can be sent or response received, the endpoint must be authenticated and authorized to access the LLM service. Endpoint access control verifies user identity and device compliance at the earliest possible point in the request flow, gating all subsequent processing.

Why A is Wrong: A front-end web proxy gateway routes and manages web traffic between users and backend services. While it may participate in the authentication flow, it is a routing and mediation component that operates after the endpoint has been validated, not the first authentication requirement.

Why C is Wrong: An API gateway manages API traffic, authentication tokens, and rate limiting for API interactions. It processes requests after initial endpoint authentication has been established and the request is being routed to the LLM backend.

Why D is Wrong: A back-end access gateway controls access to backend services and resources. It operates downstream from both endpoint authentication and API gateway processing, representing a deeper layer of the access control architecture rather than the first authentication requirement.

Basic Concept: ML models excel at classification tasks, learning to assign incoming data points to predefined categories based on patterns in training data. In a SOC context, alert classification is the highest-value triage function ML can perform. CompTIA SecAI+ Exam Objectives address AI-assisted security operations under Domain 3.

Why C is Correct: ML-based alert classification automatically analyzes characteristics of each alert and assigns it to a severity category such as critical, high, medium, or low, or to a threat type such as malware or intrusion attempt. This dramatically reduces analyst workload and speeds triage by prioritizing which alerts demand immediate human attention, directly solving the high-volume problem.

Why A is Wrong: Applying filters on specific alerts is a rule-based operation achievable without ML using simple log management tools. It requires no learning capability and does not adapt to new or evolving threats.

Why B is Wrong: Automatically patching systems is a remediation action requiring validated, controlled processes. Having an ML system autonomously patch production systems without human oversight poses unacceptable operational and security risk.

Why D is Wrong: Summarizing alert content is a useful generative AI function but does not provide prioritization value for triage. Classification tells analysts what to act on first; summarization only rephrases existing information.

An audit trail is the governance mechanism that preserves evidence of actions, decisions, approvals, validation activities, and responsible parties throughout the lifecycle of an AI system. If the organization cannot establish who authorized deployment or how the system was validated, the fundamental problem is missing traceability and historical evidence. This is precisely what an audit trail should provide. CompTIA SecAI+ emphasizes governance roles, model validation, monitoring, auditing for quality and compliance, and accountability throughout the AI lifecycle. A completed threat model documents threats and attack scenarios, but it would not necessarily record deployment approval or validation evidence. Blueprint controls are not the primary mechanism for preserving historical authorization records. Organizational policies may define that approval and validation must occur, but merely having policies does not demonstrate that the required actions actually occurred. Proper audit records would identify the approver, validation method, relevant results, dates, model version, and other governance evidence. Therefore, the inability to reconstruct those decisions indicates the absence of an adequate audit trail.

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

Basic Concept: OWASP has published the Top 10 vulnerabilities for Large Language Model Applications, each addressing a distinct category of LLM security risk. Understanding which OWASP category maps to specific LLM vulnerability scenarios is a key competency in the CompTIA SecAI+ Study Guide under securing AI systems.

Why D is Correct: Improper output handling (OWASP LLM02) occurs when an application passes LLM-generated outputs to downstream systems such as plug-ins, web browsers, or databases without proper validation, sanitization, or encoding. This can enable XSS, SQL injection, remote code execution, or other injection attacks against plug-ins and downstream systems. The scenario exactly matches this: unsanitized AI responses are automatically passed to multiple plug-ins, which could execute malicious content in the model ' s output.

Why A is Wrong: Misinformation refers to the AI generating false or misleading content that users might believe. It is a content accuracy concern related to hallucinations and false information propagation, not a vulnerability describing how model outputs are handled by downstream systems.

Why B is Wrong: Prompt injection involves crafting inputs to manipulate model behavior and override instructions. While it can be a contributing cause of unsafe outputs, the vulnerability described — passing unsanitized outputs to plug-ins — is specifically the output handling failure, not the injection mechanism itself.

Why C is Wrong: Unbounded consumption (OWASP LLM10) refers to resource exhaustion attacks including denial-of-wallet and denial-of-service through excessive token consumption. It addresses resource management vulnerabilities, not the security implications of passing model outputs to downstream systems.

Basic Concept: In AI governance, each role holds distinct responsibilities. Understanding these roles is core to CompTIA SecAI+ Domain 4 (AI Governance, Risk, and Compliance).

Why D is Correct: The Data Scientist is responsible for translating business use cases into working AI/ML models. They analyze business requirements, identify the appropriate machine learning approach, and develop models that fulfill specific business objectives. According to the CompTIA SecAI+ Study Guide, data scientists bridge raw data and actionable AI solutions by building and validating models derived from business-driven needs.

Why A is Wrong: A Platform Architect designs and manages the infrastructure and technical platforms hosting AI systems. Their focus is architectural design of the environment, not model development from business use cases.

Why B is Wrong: An AI Risk Analyst identifies, evaluates, and mitigates risks associated with AI adoption. Their role is governance and risk-oriented, not model creation.

Why C is Wrong: An MLOps Engineer operationalizes, deploys, monitors, and maintains AI models in production. They take models already built by data scientists and ensure reliable operation at scale, not develop them from business use cases.

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.

Basic Concept: Prompt engineers are responsible for designing and refining the prompts and instructions that guide an LLM ' s behavior. When user experience is declining after an LLM launch, this signals that the model ' s outputs are not meeting quality standards. CompTIA SecAI+ addresses prompt engineering quality management under securing and optimizing AI systems.

Why C is Correct: Quality control should be the highest priority when user experience is declining. Prompt engineers must systematically evaluate model responses against quality benchmarks, identify failure patterns causing poor user experience, and iteratively refine prompts to produce accurate, relevant, and appropriately formatted responses. Quality control encompasses testing, evaluation, and continuous improvement of prompt performance.

Why A is Wrong: Customer success management is a business function focused on customer relationship management and retention. While related to user experience outcomes, it is not a technical priority that prompt engineers can directly address through their core competency of prompt design and refinement.

Why B is Wrong: Sales life cycle management is a business process for managing customer acquisition and revenue. It is entirely outside the scope of prompt engineering activities and does not address declining LLM user experience.

Why D is Wrong: Business objectives define what the organization aims to achieve with the LLM deployment. These are set at the strategic level and inform the direction for prompt engineering. They are inputs to the quality control process rather than the priority action prompt engineers should take when experience is declining.

Model validation is intended to determine systematically whether an AI or machine learning model performs according to its defined objectives and produces acceptable results. This requires a formal methodology, appropriate validation data, measurable criteria, and comparison of actual model behavior against expected outcomes. CompTIA SecAI+ explicitly includes model validation among model-training techniques and also places validation, model evaluation, monitoring, and feedback within the AI lifecycle. Option C therefore represents the actual purpose of validation: objectively establishing whether the model satisfies predetermined performance and quality requirements. Providing feedback between interactions is closer to feedback and iteration or model adaptation rather than validation itself. Checking an exported file is merely an output or serialization check and does not evaluate model quality comprehensively. CI/CD integration checks establish whether software components build, integrate, or deploy correctly; a model could successfully pass those technical checks while still producing inaccurate, biased, unsafe, or otherwise unacceptable predictions. Formal measurement against expected outcomes is therefore the distinguishing characteristic of proper model validation.

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

Agentic AI that can automatically patch organizational systems represents the highest-impact and highest-risk scenario, making human-in-the-loop control the most appropriate. CompTIA SecAI+ identifies human-in-the-loop, human oversight, and human validation as human-centric AI design principles. Agentic systems differ from passive AI because they can take actions through tools, APIs, scripts, or other integrated systems. Automated patching can modify production hosts, restart services, introduce incompatibilities, cause outages, or affect business-critical applications. Requiring human authorization before consequential actions provides an important control point for validating the recommendation, affected assets, timing, dependencies, and rollback plan. A summarization model normally produces content for review without directly modifying systems. A graphics-generation model likewise creates content rather than performing privileged infrastructure changes. An FAQ chatbot is generally constrained to answering questions and typically has limited operational impact. Human oversight can still be valuable in all three situations, but the potential operational consequences are considerably greater when autonomous AI can change production systems. Therefore, agentic AI performing patching is the scenario where human-in-the-loop governance is most strongly warranted.

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

Basic Concept: ISO develops international standards for management systems across various domains. For organizations seeking third-party certification demonstrating commitment to responsible AI governance practices, the appropriate ISO standard must specifically address AI management systems. CompTIA SecAI+ Exam Objectives cover ISO standards relevant to AI governance under Domain 4.

Why D is Correct: ISO 42001 is the International Standard for Artificial Intelligence Management Systems (AIMS). It provides a framework for establishing, implementing, maintaining, and continually improving an AI management system within organizations. ISO 42001 certification provides third-party assurance specifically for responsible AI practices including risk management, transparency, human oversight, and ethical AI governance — directly answering the question.

Why A is Wrong: ISO 20000 is the standard for IT Service Management (ITSM). It provides requirements for establishing and maintaining a service management system for IT services. It does not address AI governance or responsible AI practices.

Why B is Wrong: ISO 27001 is the standard for Information Security Management Systems (ISMS). It addresses general information security risk management, not AI-specific governance or responsible AI practices such as fairness, transparency, and AI lifecycle management.

Why C is Wrong: ISO 27701 extends ISO 27001 to address Privacy Information Management (PIMS), covering personal data protection requirements aligned with GDPR. While relevant to data privacy in AI systems, it does not specifically certify responsible AI governance practices.

Basic Concept: Protecting a released AI model from unauthorized modification requires controlling who can interact with it and at what privilege level. IAM-integrated API access provides granular, auditable control over model interactions. CompTIA SecAI+ Study Guide covers model protection through identity and access management integration.

Why D is Correct: Integrating an API with IAM roles ensures that all interactions with the model are authenticated and authorized according to precisely defined permissions. IAM roles enforce the principle of least privilege, ensuring users can query the model only within authorized scope and cannot modify model parameters, weights, or configuration. API-level access provides an abstraction layer that protects the underlying model from direct access while enabling controlled, auditable interactions.

Why A is Wrong: Changing to an LLM with guardrails addresses model behavior safety but does not protect the model artifacts themselves from tampering or unauthorized modification. It changes the model type rather than implementing access controls.

Why B is Wrong: Providing secure copies for local runtime distributes model copies to multiple endpoints, significantly increasing the attack surface for tampering. Each local copy represents a potential point of unauthorized modification.

Why C is Wrong: Restricting access to IT professionals is overly broad and vague. IT professionals may still need varying levels of access for different purposes, and generic role-based access without IAM integration and API mediation provides insufficient granularity to prevent unintentional modification.

Output bias is the best answer because an autonomous AI agent can convert biased model judgments into consequential decisions without requiring a human to review each result. CompTIA SecAI+ identifies introduction of bias as a significant AI risk and separately identifies autonomous systems as an important governance concern. Responsible AI principles such as fairness, reliability, accountability, explainability, and human oversight exist partly to control this problem.

If an agent ' s model produces systematically biased recommendations, those biased outputs can directly influence hiring, access decisions, financial transactions, security actions, or other automated processes. Autonomy therefore increases the impact of output bias because an erroneous or unfair recommendation may become an action before a person can intervene.

Accidental data leakage is also an important AI risk, but the question emphasizes autonomous decision-making , making biased decisions the more directly associated concern. Overfitting is primarily a model-development problem in which a model memorizes training characteristics and fails to generalize effectively. Increased workload is contrary to one of the primary motivations for using agents, which is automation. Therefore, output bias represents the most relevant risk among the available choices.

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

Basic Concept: When an AI fraud detection model produces false positives (blocking legitimate transactions), this indicates the model ' s decision boundary is insufficiently calibrated. The model needs improved training data to better distinguish fraudulent from legitimate transactions. CompTIA SecAI+ covers model performance improvement under AI-assisted security.

Why A is Correct: Retraining the model with more data and recent transaction patterns directly addresses the root cause of false positives. Additional representative legitimate transaction data helps the model learn more accurate decision boundaries, reducing false positives while maintaining detection sensitivity for actual fraud. This improves model accuracy without abandoning AI-based detection.

Why B is Wrong: Token usage and rate limits are cost and resource management controls for LLM APIs. They have no relevance to improving the accuracy of a fraud detection ML model that incorrectly classifies legitimate transactions.

Why C is Wrong: Encrypting data and applying access controls are data security measures that protect confidentiality and integrity. They do not address model classification accuracy or the false positive problem in fraud detection.

Why D is Wrong: Rolling back to a traditional system abandons the capabilities of AI-based fraud detection. The appropriate response to model performance issues is to improve the model through retraining, not to regress to less capable detection approaches.

Basic Concept: When API sessions or connections remain active and consuming resources after their intended operations have completed, they create resource leaks that progressively degrade system availability. Session lifecycle management is critical for maintaining AI system health. CompTIA SecAI+ Study Guide covers session management as an availability control for AI systems.

Why B is Correct: Enforcing session expiration ensures that external API sessions and connections are automatically terminated after a defined idle period or maximum duration. This prevents resource-consuming zombie sessions from accumulating and exhausting system memory, thread pools, or connection limits. The observed pattern — persistent unavailability that resolves temporarily with restart — is classic resource leak behavior from sessions that never close, making session expiration the direct fix.

Why A is Wrong: Token limits cap the number of tokens processed per request. While useful for controlling per-request resource consumption, they do not address the root cause of sessions persisting and consuming resources long after their operations complete.

Why C is Wrong: Increasing system memory defers the problem rather than solving it. The leak will eventually consume the additional memory too, requiring another restart. Addressing the root cause through session management is superior to scaling resources to accommodate the leak.

Why D is Wrong: MFA adds an additional authentication factor for users accessing the system. It is a security control for identity verification, not a mechanism for managing session lifecycle or preventing resource exhaustion from lingering sessions.

Basic Concept: Data at rest refers to inactive data stored in databases or storage media. Protecting it from unauthorized disclosure is a fundamental data security principle covered in the CompTIA SecAI+ Study Guide under securing AI data pipelines.

Why C is Correct: Encryption protects data at rest by rendering it unreadable to unauthorized parties without the appropriate decryption key. In a financial institution with sensitive data, encryption at rest (e.g., AES-256) is the primary control against data disclosure. Even if storage media is physically compromised, encrypted data remains unintelligible. CompTIA SecAI+ Exam Objectives highlight encryption as the primary confidentiality control for stored AI data.

Why A is Wrong: Data lineage tracks the origin and movement of data throughout its lifecycle. It improves traceability and auditability but does not prevent unauthorized disclosure of data at rest.

Why B is Wrong: Rate limits control the number of API requests within a time period. They protect against abuse and denial-of-service scenarios, not data-at-rest confidentiality.

Why D is Wrong: Data masking replaces sensitive values with fictitious substitutes, useful during development or testing. For actual production data at rest in AI systems handling real financial records, encryption provides stronger and more comprehensive confidentiality.

Basic Concept: Domain-specific AI chatbots can produce contextually inappropriate responses when they lack sufficient domain grounding to disambiguate terms that have different meanings in different contexts. Guardrails can enforce domain-appropriate interpretation and response constraints. CompTIA SecAI+ Study Guide covers guardrails as a mechanism for maintaining model behavioral boundaries.

Why A is Correct: Configuring guardrails allows the organization to enforce domain-specific behavioral constraints on the chatbot, ensuring it interprets ambiguous terms within the correct technical context. Guardrails can include context-aware rules that recognize when a query is in a cybersecurity context and constrain the model to provide domain-appropriate responses. This directly addresses the issue of the model providing biologically-framed responses to a technical cybersecurity question.

Why B is Wrong: Encrypting model weights at rest protects the model parameters from unauthorized access or modification. It is a data protection control for model intellectual property and does not influence how the model interprets or responds to domain-specific queries at inference time.

Why C is Wrong: Model access controls restrict who can query and modify the model. They manage authorization at the user and system level but do not enforce domain-appropriate response constraints or prevent contextually incorrect answers from being generated.

Why D is Wrong: Prompt templates provide structured, reusable formats for common queries. While they can help standardize how cybersecurity questions are asked, they require users to use the template and do not provide real-time enforcement of domain-appropriate response generation for all input variations.

Basic Concept: Various regulatory frameworks govern AI use in different contexts. For auditing legal compliance in high-risk AI applications such as employment and HR, binding regulatory legislation takes precedence over voluntary standards. CompTIA SecAI+ Exam Objectives cover AI governance and compliance frameworks under Domain 4.

Why C is Correct: The EU AI Act is the world ' s first comprehensive, legally binding AI regulation. It explicitly classifies AI systems used in employment, worker management, and recruitment as high-risk AI systems, subjecting them to strict compliance requirements including conformity assessments, transparency obligations, and human oversight mandates. An auditor reviewing HR AI for legal non-compliance must reference this binding legislation.

Why A is Wrong: The OECD AI Principles are non-binding international guidelines promoting responsible AI. They offer policy guidance but carry no legal enforcement power for compliance auditing.

Why B is Wrong: The NIST AI RMF is a voluntary, risk management-focused framework. It is not a legal compliance standard and cannot be used to assess legal non-compliance.

Why D is Wrong: ISO standards such as ISO 42001 are voluntary international best practice standards. They are not legal compliance instruments with enforceable penalties for HR AI systems.

Basic Concept: AI GRC implementation requires roles that combine understanding of AI technical capabilities and limitations with security risk assessment, control design, and compliance framework expertise. Identifying which roles naturally contribute to AI GRC is essential for team design. CompTIA SecAI+ Study Guide covers AI governance role responsibilities under Domain 4.

Why B is Correct: Data Scientists possess deep understanding of AI model capabilities, limitations, data requirements, and failure modes. For GRC implementation, their technical expertise is essential for identifying AI-specific risks such as bias, model drift, and data quality issues, assessing compliance implications of model design choices, and evaluating whether AI systems meet governance requirements.

Why D is Correct: Security Architects design comprehensive security frameworks and risk management strategies. For AI GRC, they translate governance requirements into technical controls, design AI security architectures that satisfy compliance obligations, assess the risk posture of AI deployments, and ensure security principles including least privilege, defense-in-depth, and audit logging are built into AI system designs.

Why A is Wrong: Desktop specialists manage user workstation hardware and software. Their role focuses on endpoint management and user support, not on the strategic risk assessment, compliance evaluation, or technical AI governance activities required for AI GRC implementation.

Why C is Wrong: Software developers write application code. While they implement security controls when directed, they typically lack the broad risk management, compliance framework expertise, and security architecture perspective needed to lead AI GRC implementation.

Why E is Wrong: SOC analysts focus on monitoring, detecting, and responding to security incidents in operational environments. Their expertise is in reactive security operations rather than the proactive governance framework design and compliance management that AI GRC requires.

Why F is Wrong: Network engineers design and maintain network infrastructure. Their expertise is in network connectivity and protocols, not in AI system governance, risk assessment frameworks, or compliance requirements.

Basic Concept: DoS attacks overwhelm AI systems by sending excessive requests that exhaust computational resources, memory, or bandwidth, preventing legitimate users from being served. The primary defense against volume-based attacks is throttling the rate at which requests can be processed. CompTIA SecAI+ Exam Objectives identify rate limiting as the key DoS mitigation control for AI systems.

Why B is Correct: Rate limiting directly addresses the root mechanism of DoS attacks by restricting the number of requests any single client or IP address can submit within a defined time window. By enforcing request quotas, rate limiting prevents attackers from generating the request volume necessary to overwhelm the system while preserving capacity for legitimate users. It is the most direct and effective preventive control against DoS attacks on AI APIs and services.

Why A is Wrong: Model guardrails inspect and filter the content of prompts and responses for policy compliance and safety. They operate at the semantic content level, not at the request volume level, and cannot prevent resource exhaustion from high-volume request flooding.

Why C is Wrong: End-to-end encryption protects the confidentiality and integrity of data in transit. Encrypted DoS traffic is just as damaging as unencrypted traffic; encryption does not limit request rates or prevent resource exhaustion.

Why D is Wrong: Access controls restrict who can interact with the system, which can reduce the potential attacker pool. However, authenticated users and compromised accounts can still launch DoS attacks, and access controls alone cannot prevent high-volume attacks from authorized sources.

Basic Concept: Successful AI adoption at an organizational level requires a centralized governance body that standardizes AI practices, promotes best practices, and ensures consistent, safe, and effective AI deployment across the organization. CompTIA SecAI+ Study Guide covers AI organizational governance structures under Domain 4.

Why A is Correct: An AI Center of Excellence (CoE) is an organizational unit specifically designed to govern, standardize, and advance AI adoption. It develops and publishes policies, creates approved patterns for AI usage, evaluates new AI use cases, provides expert guidance, and maintains governance oversight. The CoE exactly matches the described need for a structure to evaluate, publish, and approve AI usage patterns across the organization.

Why B is Wrong: An AI legal affairs office focuses on legal compliance, intellectual property, and regulatory matters related to AI. While important for legal risk management, it does not fulfill the broader governance mandate of establishing and approving AI usage patterns and best practices across the organization.

Why C is Wrong: An AI audit department conducts post-implementation reviews and compliance assessments of existing AI systems. It is a retrospective and oversight function rather than a proactive body for developing and approving AI usage patterns and policies.

Why D is Wrong: An AI data science division is a technical team focused on building AI models and solutions. It is a development function rather than a governance structure designed to create policies, evaluate AI patterns, and provide cross-organizational oversight of AI adoption.

Regulatory requirements are the most critical consideration because they can establish mandatory restrictions on how organizational, personal, regulated, or otherwise sensitive information may be processed by AI systems. CompTIA SecAI+ places private versus public models directly within the corporate-policy portion of AI governance, risk, and compliance and connects those decisions with sensitive data governance, third-party evaluations, and regulatory obligations. A public model may send data to infrastructure controlled by an external provider, potentially creating concerns involving data residency, retention, confidentiality, processing purposes, and cross-border transfers. A private model can provide greater organizational control over these factors. Model security remains essential, but a technically secure architecture can still be noncompliant if it violates applicable legal or regulatory obligations. Applicability determines whether a model is suitable for the intended use case but is not a governing compliance control. Responsible AI principles provide important guidance around fairness, safety, transparency, privacy, and accountability, but binding regulatory obligations generally take precedence when determining permissible deployment conditions. Therefore, regulations are the controlling consideration when deciding whether public or private AI models are acceptable for sensitive training workloads.

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

Basic Concept: Reducing post-deployment vulnerabilities requires catching security issues as early as possible in the development workflow. AI-assisted tools that analyze code during development provide the earliest possible intervention point. CompTIA SecAI+ Study Guide covers AI integration in secure development under AI-assisted security.

Why A is Correct: AI-assisted code linting analyzes source code in real time during development to identify security vulnerabilities, insecure coding patterns, policy violations, and quality issues before code is compiled or committed. By catching vulnerabilities at the coding stage — the earliest possible point in the development workflow — AI code linting prevents vulnerable code from progressing to testing, staging, or production, directly reducing post-deployment vulnerabilities at their source.

Why B is Wrong: Incident management handles security events and incidents after they have occurred in production. It is a reactive capability focused on response and recovery rather than early-stage vulnerability identification in the development workflow.

Why C is Wrong: Automated deployment/rollback automates the process of pushing code to production and reverting to previous versions when issues are detected post-deployment. It is a deployment safety mechanism rather than an early detection tool during the development phase.

Why D is Wrong: System auditing reviews and records system activities and configurations for compliance verification. It is primarily a detective and compliance control for systems that are already deployed, not an early development-phase vulnerability identification tool.

Basic Concept: Training an AI model involves repeatedly exposing it to training data so it can learn optimal parameters. The terminology for training cycles is fundamental to understanding AI model training processes. CompTIA SecAI+ Study Guide covers core AI training concepts under basic AI concepts.

Why D is Correct: An epoch refers to one complete pass through the entire training dataset. When a model trains for multiple epochs, it sees each training example multiple times, allowing it to refine its parameters progressively. The number of training epochs is a key hyperparameter that directly affects model performance — too few and the model underfits; too many and it may overfit. For a threat detection model, specifying epochs controls how thoroughly the model has learned from the training data.

Why A is Wrong: k-means clustering is an unsupervised machine learning algorithm that groups data points into k clusters based on feature similarity. It is a data clustering algorithm, not a term describing training cycles or iterations.

Why B is Wrong: Tokens are the discrete units that LLMs use to process text inputs and outputs. Token count measures text processing volume and LLM utilization, not the number of times a model has processed its training dataset.

Why C is Wrong: Temperature is an inference parameter that controls the randomness or creativity of an LLM ' s output generation. Higher temperature produces more varied outputs; lower temperature produces more deterministic responses. It is not related to training cycles or iterations.

Basic Concept: When unauthorized changes to an ML training pipeline cause model degradation, the root cause is insufficient access control and change management around the pipeline. Preventing future occurrences requires implementing governance controls that ensure all pipeline changes are reviewed and approved before execution. CompTIA SecAI+ Study Guide covers MDLC change management controls.

Why B is Correct: Enabling human review and approval workflows in the repository creates a mandatory gate requiring authorized reviewers to examine and approve any changes to training pipeline code before they can be merged and executed. This prevents unauthorized modifications from reaching the pipeline by enforcing a review process where any suspicious or unauthorized changes will be caught and rejected before they affect model training and performance.

Why A is Wrong: Static code scanning analyzes code for vulnerabilities and coding standard violations. While it improves code quality and security, it does not prevent unauthorized individuals from submitting and merging malicious changes to the pipeline without proper review.

Why C is Wrong: Retraining with more data and epochs addresses model performance restoration after the fact but does not prevent future unauthorized pipeline modifications. If the pipeline remains unprotected, the same attack could occur again on the new model.

Why D is Wrong: Keeping multiple model copies enables rapid restoration of a previous version when a deployed model is found to be compromised. While useful for recovery, it is a reactive measure that does not prevent unauthorized pipeline changes from occurring and affecting future model training.

Basic Concept: Suspicious queries in AI system logs indicate that potentially malicious or policy-violating prompts are reaching the AI model. Proactively intercepting and filtering suspicious prompts before they are processed requires a prompt-level security control. CompTIA SecAI+ Study Guide identifies prompt firewalls as the appropriate control for blocking suspicious AI queries.

Why A is Correct: A prompt firewall analyzes incoming queries using a combination of pattern matching, semantic analysis, and policy rules to identify and block suspicious prompts before they reach the AI model. It can detect prompt injection attempts, jailbreaking patterns, sensitive data extraction queries, and other suspicious prompt characteristics. By intercepting malicious prompts at the perimeter, it prevents them from influencing model behavior or extracting sensitive information.

Why B is Wrong: Data size controls limit the volume or size of data in requests. While controlling input size can prevent some attacks, it does not analyze the content or semantics of queries to detect suspicious patterns. A small suspicious prompt can be just as harmful as a large one.

Why C is Wrong: Rate limiting controls the frequency of requests from a source. While it can slow down automated attack campaigns, it does not inspect query content for suspicious patterns and allows suspicious queries through as long as they are submitted below the rate threshold.

Why D is Wrong: Agentic AI is an AI architecture for autonomous multi-step task execution. It is a type of AI system, not a security control for filtering suspicious queries from an existing AI system ' s logs.

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.

Basic Concept: AI chatbots are designed with safety guidelines and content policies that prevent them from generating harmful, offensive, or inappropriate content. When users find ways to bypass these restrictions through crafted prompts, they have " jailbroken " the model. CompTIA SecAI+ Study Guide covers jailbreaking as a key AI vulnerability category.

Why C is Correct: Jailbreaking is the process of using cleverly crafted prompts to bypass an AI model ' s built-in safety restrictions, content policies, and behavioral guardrails, causing it to produce outputs it was designed to refuse. The scenario describes a chatbot that was designed for automobile configuration assistance but is producing offensive responses following customer prompts, indicating that customers have successfully prompted the model to bypass its safety constraints and generate prohibited content.

Why A is Wrong: Model skewing refers to attacks or biases that cause a model to favor certain outputs or perspectives systematically over time, often through data manipulation. It describes a gradual distortion of model behavior, not a direct user-prompted bypass of safety restrictions in a single interaction.

Why B is Wrong: Model theft involves extracting or replicating a proprietary model ' s functionality or architecture through repeated queries. It is an intellectual property attack aimed at stealing the model ' s knowledge, not an attack that causes the model to produce offensive content.

Why D is Wrong: Insecure output handling occurs when an application fails to properly validate or sanitize AI-generated outputs before using them in ways that could cause harm such as passing AI output directly to a system command or database query. It describes a developer implementation vulnerability, not the act of a user prompting a model to bypass its safety constraints.

Basic Concept: Reconnaissance is the information gathering phase of an attack. LLMs can be enhanced to perform more effective reconnaissance by giving them access to current, specific information beyond their training data cutoff. CompTIA SecAI+ covers AI augmentation techniques including RAG under AI-assisted security.

Why A is Correct: RAG enhances an LLM by connecting it to an external knowledge base or real-time data sources that it can query during inference. For reconnaissance purposes, a RAG-enabled LLM can access up-to-date organizational information, technical documentation, and intelligence feeds that go beyond its static training data. This makes the LLM significantly more capable for gathering current, targeted intelligence about specific organizations or infrastructure.

Why B is Wrong: Creating a web scraper is a basic data collection technique. While AI can help write scraper code, the scraper itself is a simple script that does not enhance the LLM ' s intelligence or reasoning capabilities for sophisticated reconnaissance.

Why C is Wrong: Instructing an AI assistant to query as an administrator is a prompt manipulation attempt. An LLM cannot actually gain elevated permissions through a prompt instruction; this describes social engineering or privilege escalation via prompting, not a performance enhancement technique.

Why D is Wrong: Prompting a chatbot to describe naming patterns is a basic use of an existing LLM ' s knowledge. It does not strengthen or enhance the model ' s capabilities; it merely queries what the model already knows from training data, which may be outdated or generic.

Basic Concept: Preventing prompt injection and ensuring output sanitization requires a control that can inspect both the semantic content of incoming prompts and the safety of outgoing responses. This requires an intelligent, context-aware filtering layer specifically designed for LLM traffic. CompTIA SecAI+ Study Guide identifies LLM firewalls as a primary control for prompt security and output safety.

Why C is Correct: An LLM firewall is specifically designed to inspect, filter, and sanitize both incoming prompts and outgoing AI responses. It can detect and block prompt injection attempts using pattern matching, semantic analysis, and behavioral heuristics, while also sanitizing output to remove sensitive data, harmful content, or policy violations before responses reach users. This dual capability makes it the primary control addressing both requirements simultaneously.

Why A is Wrong: Least privilege restricts what resources and actions users and systems can access. It reduces the potential impact of successful attacks but does not inspect prompt content for injection attempts or sanitize model outputs.

Why B is Wrong: Encryption protects data confidentiality in transit and at rest. It does not analyze prompt content for malicious patterns or filter AI-generated responses for unsafe content. Encrypted traffic can still carry prompt injection attacks.

Why D is Wrong: Rate limiting controls request frequency. While it can slow down automated injection attack campaigns, it does not inspect the content of individual prompts to detect injections, nor does it sanitize output responses. Malicious prompts can still succeed within rate limits.

Domain-specific specialization is a major advantage of using a small language model when cost efficiency matters. CompTIA SecAI+ requires candidates to distinguish both LLMs and SLMs within natural language processing concepts. An SLM can be trained or fine-tuned for a narrowly defined task such as interpreting SIEM events, endpoint terminology, security alerts, and incident patterns. Because it does not require the enormous parameter count and broad general-purpose knowledge of a large model, an SLM can provide efficient task-specific inference while requiring less memory and computational capacity. This can reduce infrastructure and operational costs substantially. Broad dataset training is characteristic of general-purpose foundation models and tends to increase rather than reduce training and compute requirements. Data aggregation is a preprocessing or analytics function and is not an inherent SLM advantage. Data privacy can improve when smaller models are deployed locally, but local deployment is an architectural choice rather than the defining cost-related benefit represented by the available choices. A model concentrated on domain-specific cybersecurity information can therefore deliver the required SIEM-analysis capability more economically than a general-purpose LLM.

Basic Concept: In a layered AI system security architecture, access control must be established at each layer, beginning from the outermost point of entry. Authentication must be established at the endpoint level first, as this is the first point of interaction between users and the AI system. CompTIA SecAI+ Study Guide establishes endpoint authentication as the initial access control layer for AI systems.

Why D is Correct: Endpoint access control is the first authentication control to implement because it governs the initial connection from user devices or client applications to the AI system. All subsequent access layers including server access, model access, and data access depend on the endpoint being authenticated first. Establishing endpoint authentication ensures that only authorized endpoints can initiate sessions and proceed through subsequent authentication layers.

Why A is Wrong: Model access controls govern who can query, update, or access the AI model ' s parameters and functions. This control layer is implemented after endpoint authentication has been established, as it applies to requests that have already been authenticated at the endpoint level.

Why B is Wrong: Server access controls manage access to the computing infrastructure hosting the AI system. While critical for infrastructure security, server-level controls are configured by administrators and are not the first authentication control for end-user access flows.

Why C is Wrong: Data access controls define what data the AI system and its users can read, write, or query. These are implemented at a deeper layer after endpoint and potentially model authentication have verified that the requester is authorized to interact with the system at all.

Basic Concept: Pattern recognition is an AI technique that enables a system to identify recurring sequences or structures within data. In cybersecurity, detecting behavioral patterns such as consistent pre-login failure sequences followed by successful access is critical for threat detection. CompTIA SecAI+ Exam Objectives cover this under AI-assisted security.

Why B is Correct: The scenario describes a highly regular, repeating behavioral pattern — two failures followed by success at a specific time interval, consistently during office hours. Pattern recognition enables the AI model to learn this sequence and flag it as indicative of credential stuffing or an automated brute-force attack with timing controls. ML-driven pattern recognition is specifically designed for such behavioral anomaly detection.

Why A is Wrong: Access management controls who can log in and under what conditions. It enforces authorization policies but does not analyze or detect suspicious behavioral sequences in authentication logs.

Why C is Wrong: Signature matching compares known attack signatures against observed data. The described pattern is behavioral and time-based rather than a known malware or exploit signature, making this technique unsuitable.

Why D is Wrong: Vulnerability analysis identifies weaknesses in systems and code. It does not analyze authentication log sequences or detect behavioral patterns in user activity data.

Basic Concept: Data validation is a critical step in the AI development pipeline that involves verifying that the data used for training and inference meets quality standards, is representative, and is free from systematic errors that could introduce bias. The quality of training data directly determines the quality and fairness of model outputs. CompTIA SecAI+ Study Guide covers data validation under AI development and responsible AI principles.

Why D is Correct: The primary purpose of data validation for an AI system is to ensure that the data is accurate, representative, and free from systematic errors that would cause the model to produce biased or discriminatory outcomes. Validating data checks for class imbalance, demographic underrepresentation, labeling errors, and corrupted values that could embed biases into the model. This ensures the AI system produces fair, accurate, and trustworthy outputs across all user groups.

Why A is Wrong: Automating the process is a benefit of using automated data validation tools but is not the primary purpose of validation itself. The automation serves the validation goal rather than being the reason validation is performed.

Why B is Wrong: Reducing resource consumption is an engineering optimization concern. Data validation may reduce resource waste by preventing training on poor-quality data, but this is a secondary benefit, not the primary purpose.

Why C is Wrong: Optimizing storage databases is a database engineering concern about performance and efficiency. Data validation examines data quality and representativeness for AI purposes, not database architecture optimization.

Deploying data loss prevention (DLP) is the best answer because the chatbot has exposed internal application logic rather than returning only the information intended for the customer. This represents a form of sensitive information disclosure , which CompTIA SecAI+ specifically identifies as an AI-system attack or failure condition. The objectives also emphasize data security controls such as classification, redaction, masking, and minimization to prevent inappropriate disclosure.

A DLP control can inspect generated responses for source code, confidential identifiers, credentials, internal business logic, or other restricted information and prevent that content from being returned externally. Retraining the model to eliminate bias is unrelated because no discriminatory or statistically skewed behavior is shown. Secure output handling is important when model-generated output is consumed by downstream applications and could lead to injection or execution vulnerabilities. Here, however, the immediate issue is disclosure of internal information directly to a user. Cookies also do not address the problem; they are associated with maintaining web sessions and are not a general mitigation for server-side request forgery. Therefore, DLP most directly addresses the exposed information.

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

Basic Concept: When an AI chatbot powered by RAG retrieves and outputs sensitive patient information such as names, medical histories, or identifiers, the risk of Protected Health Information (PHI) disclosure must be mitigated. CompTIA SecAI+ Study Guide covers data protection techniques for AI systems handling sensitive health data.

Why A is Correct: Masking replaces sensitive data values such as patient names, dates of birth, medical record numbers, and diagnoses with redacted or anonymized equivalents in the chatbot ' s output. Even if the RAG system retrieves records containing patient information, masking ensures that the sensitive fields are obscured before the response is presented to the user. This directly prevents PHI disclosure while allowing the chatbot to provide useful responses based on the underlying data patterns.

Why B is Wrong: Classification involves categorizing data by its sensitivity level such as public, internal, confidential, or restricted. While it identifies which data requires protection, classification alone does not transform or obscure the sensitive values in chatbot outputs.

Why C is Wrong: Data minimization is a privacy principle that limits data collection to only what is necessary for the specified purpose. While valuable as a design principle when building the RAG knowledge base, it is a data governance strategy rather than a technical output control that can be applied to mitigate existing PHI disclosure in chatbot responses.

Why D is Wrong: Normalization is a data processing technique that scales numerical values to a standard range or standardizes data formats. It is a preprocessing step for improving model training efficiency, not a data protection technique for preventing patient information disclosure in AI outputs.

Part 1 — Select the protocol or cipher

System component

Select

API gateway

TLS 1.2

Database storage

CAMELLIA

AI model storage

HMAC-SHA512

Part 2 — Select the data-protection technique

Enter the techniques from the first row to the fifth row in this exact order:

Row Data modification Select

1 The name field is removed, while patient_id and dob remain De-identification

2 ip_addr and name are removed, leaving cookie and uid Anonymization

3 The card number is replaced by 0x0193828829 Tokenization

4 sensitivity: " SECRET " is added Classification

5 Part of the PIN is replaced by XXXX Masking

See Explanation

Why these are the intended answers

API gateway → TLS 1.2

The API gateway handles data moving between the client and backend systems. TLS is the only listed transport-security protocol and therefore protects the data in transit . OWASP recommends encrypting sensitive data in transit by using TLS with secure parameters.

Database storage → CAMELLIA

CAMELLIA is a symmetric block cipher suitable for encrypting substantial quantities of stored data. It is therefore the valid storage-encryption choice among the listed options.

Do not select AES-512 . AES-512 is not a standardized AES variant. NIST defines only AES-128, AES-192, and AES-256 .

AI model storage → HMAC-SHA512

The scenario separately emphasizes protection against loss or modification of intellectual property. HMAC-SHA512 supplies message authentication and integrity verification, allowing unauthorized modification of the AI model to be detected. HMAC is not confidentiality encryption, but it is the most appropriate listed additional control for protecting model integrity. OWASP specifically identifies HMACs as cryptographic controls for stored-data integrity.

Why the other options are not selected

SHA-2 512: Hashing only; no secret key and no encryption.

Elliptical curve: A family of cryptographic techniques, not a specific storage or transport protocol.

ECDH: Used for key agreement, not direct bulk-data encryption.

AES-512: Invalid AES key size.

RSA-2048: Primarily used for asymmetric encryption, signatures, or key transport; inefficient for bulk database or model encryption.

CAMELLIA: Appropriate symmetric encryption for stored data.

HMAC-SHA512: Integrity and authenticity, not confidentiality.

Final Part 2 order

De-identification

Anonymization

Tokenization

Classification

Masking

Explanation

De-identification removes an explicitly identifying field—in this case, the person’s name—while retaining other fields needed for processing. The remaining patient ID and date of birth could potentially permit re-identification when combined with other information, so this is de-identification rather than complete anonymization. OWASP describes de-identification as deleting, scrambling, or pseudonymizing direct and indirect identifiers.

Anonymization removes identifying attributes so that the displayed record is not directly tied to the named individual. Here, both the name and IP address are removed.

Tokenization substitutes a sensitive value with a non-sensitive representative token. The original payment-card number is replaced with the hexadecimal-style value 0x0193828829. OWASP recognizes tokenization as a method for reducing exposure of stored sensitive data.

Classification labels information according to sensitivity. Adding sensitivity: " SECRET " does not conceal or transform the PIN; it categorizes the record so appropriate controls can be applied. OWASP recommends classifying processed, stored, and transmitted data and applying controls based on that classification.

Masking obscures only part of a sensitive value while preserving its general format. Changing 999-99-9999 to 999-99-XXXX is partial masking.

Basic Concept: AI-specific threat modeling requires consulting resources that catalogue adversarial attacks specifically developed for AI and ML systems. General cybersecurity frameworks may miss AI-unique attack vectors such as model inversion, data poisoning, and adversarial examples. CompTIA SecAI+ Study Guide identifies MITRE ATLAS as the authoritative source for AI system TTPs.

Why D is Correct: MITRE ATLAS provides a comprehensive, curated knowledge base of adversarial tactics, techniques, and procedures specifically targeting AI and ML systems, derived from real-world attack case studies. Analyzing ATLAS enables the architect to enumerate realistic AI-specific attacks applicable to the system being threat-modeled, which directly answers the question of which attacks can be performed.

Why A is Wrong: Using an LLM to map attack paths introduces uncertainty and potential hallucination risk. LLMs may generate plausible-sounding but inaccurate attack paths and cannot guarantee comprehensive coverage of AI-specific attack techniques.

Why B is Wrong: Quantifying risk of known vulnerabilities is a risk assessment step that occurs after identifying which attacks are possible. The architect must first identify attack possibilities before quantifying their risk impact.

Why C is Wrong: OWASP Top 10 covers web application vulnerabilities and, in its LLM edition, certain LLM-specific risks. However, MITRE ATLAS provides a more comprehensive and structured catalog of AI and ML-specific adversarial TTPs for systematic threat modeling.

Basic Concept: Generative AI systems in healthcare settings incur costs from multiple operational activities. Understanding the cost drivers specific to generative AI helps administrators implementaccurate cost monitoring and controls. CompTIA SecAI+ Study Guide covers AI cost management under securing AI systems.

Why C is Correct: Storage retrieval and prompt processing are the two primary cost drivers for generative AI systems in healthcare. Storage retrieval refers to the cost of querying vector databases or document stores in RAG-based AI systems to fetch relevant patient records, clinical guidelines, or historical data for context. Prompt processing encompasses the token-based cost of the LLM processing the combined retrieved content and user query to generate a response. Together these two activities represent the billable units that drive generative AI costs in healthcare RAG deployments, making them the most accurate basis for cost calculation and monitoring.

Why A is Wrong: Connection access and exchange gateway costs relate to network infrastructure and API gateway usage fees. While there may be minor costs associated with API calls, these are not the primary cost drivers for generative AI systems where the dominant expenses are computational token processing and data retrieval operations.

Why B is Wrong: Encryption and decryption processing costs relate to cryptographic operations for data security. While encryption is important for healthcare data protection under HIPAA, cryptographic processing overhead is minimal compared to the substantial token-based LLM processing and storage retrieval costs that dominate generative AI operational expenses.

Why D is Wrong: Catalog servicing and exchange processing are terms associated with data catalog management and data exchange infrastructure. These are not recognized primary cost components of generative AI systems in healthcare, where storage retrieval and token-based prompt processing are the established cost measurement criteria.

Basic Concept: Dynamic Application Security Testing (DAST) tests running applications by sending various inputs to discover vulnerabilities. AI can significantly enhance DAST by intelligently generating diverse, targeted test payloads that traditional tools might miss. CompTIA SecAI+ covers AI augmentation of security testing methodologies.

Why C is Correct: Payload creation is highly suitable for AI automation during DAST. AI can generate diverse, contextually appropriate attack payloads such as SQL injection strings, XSS vectors, command injection attempts, and format string exploits tailored to the specific application ' s behavior observed during testing. AI can learn from the application ' s responses to previous payloads and generate increasingly targeted inputs, discovering vulnerabilities more efficiently than static payload databases.

Why A is Wrong: DDoS attacks are volume-based attacks designed to overwhelm network or application infrastructure. Automating DDoS during DAST is inappropriate as it would disrupt service availability rather than discover application security vulnerabilities, and it is harmful to legitimate operations.

Why B is Wrong: Data poisoning is an attack targeting AI/ML model training data integrity. It is relevant to securing AI systems but is not a DAST technique for testing web or software application security vulnerabilities during dynamic testing.

Why D is Wrong: Threat modeling is a structured analysis process performed before development or testing to identify potential threats and design appropriate countermeasures. It is a planning activity, not an attack technique that can be automated during dynamic application security testing.

Basic Concept: LLM API pricing is primarily based on token consumption — the number of tokens processed in both input prompts and output responses. Controlling token usage is the most direct lever for managing and reducing LLM API costs. CompTIA SecAI+ Study Guide covers AI cost management and resource controls under securing AI systems.

Why D is Correct: Adjusting token limits directly caps the maximum number of tokens used per request for both input and output. By setting appropriate token limits, the organization prevents excessively long prompts or verbose responses from consuming unnecessary tokens, directly translating to lower API costs and providing hard budget control.

Why A is Wrong: Prompt templates standardize how queries are structured, which can indirectly improve efficiency. However, they do not enforce a hard cap on token usage and cannot prevent costs from escalating with large volumes or verbose responses.

Why B is Wrong: Increasing CPU and memory addresses computational infrastructure performance on the client side. LLM API costs are billed by the API provider based on token usage, not on the client ' s hardware resources.

Why C is Wrong: Reducing model size means using a smaller, less powerful model version. While this may lower cost per token, it is a model selection decision, not an ongoing operational control that can be adjusted to manage cost in real time.

Basic Concept: A replay attack occurs when an attacker captures a valid authentication token or credential and reuses it to impersonate a legitimate user. Preventing replay attacks requires ensuring that captured credentials cannot be successfully reused after a defined period or after their intended single use. CompTIA SecAI+ Study Guide covers replay attack prevention under AI system authentication.

Why C is Correct: Expiring session tokens have a limited validity window, typically a few minutes to hours. If an attacker captures a token, they can only use it until it expires. Short expiration times dramatically reduce the window of opportunity for replay attacks. This is the most direct and effective control specifically targeting replay attack prevention, as expired tokens are rejected even if intercepted.

Why A is Wrong: IdP federation enables single sign-on across multiple systems using federated identity providers. While it standardizes authentication, it does not inherently prevent replay attacks on captured tokens unless combined with short token expiration and proper validation.

Why B is Wrong: SSH certificate authentication uses cryptographic certificates for strong authentication. While more secure than password-based SSH, certificates alone do not prevent replay attacks unless they include timestamps, nonces, or other anti-replay mechanisms that invalidate captured credentials.

Why D is Wrong: IAM access keys are long-lived credentials that provide programmatic access to services. They are typically static and do not expire automatically, making them vulnerable to replay attacks if intercepted. They are less suitable for replay attack prevention than expiring session tokens.