Free Practice Questions for CompTIA CY0-001 Exam

Basic Concept: When AI models are deployed in production, they interact with real data including sensitive business information, personal data, and confidential records. The intersection of AI capabilities and sensitive data creates significant security risks. CompTIA SecAI+ Exam Objectives identify data exposure as the primary production security risk for AI deployments.

Why D is Correct: Data exposure is the primary security risk in production AI deployments. AI models in production process sensitive data through queries and responses, and vulnerabilities such as prompt injection, model inversion attacks, insecure output handling, and misconfigured access controls can expose confidential training data, user PII, proprietary information, or system credentials. The consequences include regulatory violations, legal liability, and reputational damage, making data exposure the most critical ongoing security concern.

Why A is Wrong: GPU acceleration is a performance optimization technique that uses graphics processors for faster AI computation. While hardware security is important, GPU acceleration itself is not a security risk — it is a performance feature that does not inherently expose data.

Why B is Wrong: Model overfitting is a model quality issue where a model performs poorly on new data after memorizing training data too specifically. While it can indirectly contribute to data memorization, it is primarily a performance and generalization concern during development rather than a primary production security risk.

Why C is Wrong: Model encryption is a security control used to protect AI model weights from unauthorized access, not a risk itself. Framing a protection mechanism as a primary risk conflates controls with threats.

Basic Concept: Securing AI systems requires a structured, end-to-end approach that addresses security at every phase of the AI model ' s lifecycle from data collection through training, testing, deployment, and ongoing monitoring. CompTIA SecAI+ Study Guide identifies the Model Development Life Cycle as the foundational framework for AI system security.

Why B is Correct: A secure Model Development Life Cycle (MDLC) integrates security practices at every stage of AI model development specifically tailored to ML workflows. It encompasses secure data handling, training data validation, model testing for adversarial robustness, secure deployment practices, and ongoing monitoring. Unlike generic software development lifecycles, the MDLC addresses ML-specific risks such as data poisoning, model drift, and adversarial attacks.

Why A is Wrong: Guardrail testing and security validation are important components of the MDLC but represent only the testing phase. They do not encompass the full lifecycle of security practices needed from data acquisition through production monitoring.

Why C is Wrong: Implementing comprehensive security architecture is a broad statement that describes an outcome rather than a specific actionable practice. It does not provide the structured, ML-specific guidance of an MDLC.

Why D is Wrong: A secure SDLC is designed for traditional software development and covers code security, testing, and deployment. While relevant to AI application development, it does not specifically address ML model-specific risks such as training data security, model integrity, and inference-time attacks.

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: 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: Balancing automation with human oversight in vulnerability management requires understanding where AI adds efficiency and where human judgment is irreplaceable. CompTIA SecAI+ Study Guide emphasizes human-in-the-loop principles for high-stakes security decisions, particularly code changes in production systems.

Why A is Correct: Having AI handle triage and ticket creation leverages its ability to rapidly process and categorize large volumes of vulnerability findings, while requiring a software engineer to review and merge code changes maintains essential human oversight for production deployments. This balance maximizes automation benefits (faster triage at scale) while ensuring that actual code modifications to a million-line codebase receive appropriate human review before deployment.

Why B is Wrong: Having humans triage but AI merge code reverses the appropriate division. Manual triage of millions of lines worth of vulnerabilities is where the bottleneck exists. Allowing AI to autonomously merge code changes without human code review oversight creates unacceptable risk of introducing defects or vulnerabilities.

Why C is Wrong: Full manual triage and manual merging eliminates AI automation entirely, failing to address the speed requirement for reducing mean time to fix in a large codebase.

Why D is Wrong: Full AI automation including merging code changes removes essential human oversight from production code deployment. In a million-line codebase, autonomous AI code merging without human review could introduce critical errors or security vulnerabilities.

Basic Concept: A chatbot that learns from user prompts is vulnerable to data poisoning through conversational injection. Malicious users can deliberately introduce false information that the chatbot incorporates into its knowledge, corrupting responses for subsequent users. CompTIA SecAI+ Study Guide identifies this as a real-time data poisoning vector requiring guardrail controls.

Why D is Correct: Guardrails prevent the chatbot from accepting and incorporating unverified, irrelevant, or potentially malicious information injected by users. They enforce boundaries on what the chatbot can learn from user interactions, validate that information aligns with the system ' s purpose and known facts, and block outputs based on poisoned knowledge. Guardrails are specifically designed to prevent the type of conversational data poisoning demonstrated where a user ' s false claim corrupted the model ' s subsequent responses.

Why A is Wrong: Data encryption protects the confidentiality of data in transit and at rest. It does not prevent a chatbot from accepting and acting on false information that users deliberately inject into the conversation.

Why B is Wrong: API rate limiting restricts the frequency of requests. While it can limit the number of poisoning attempts a single user can make, it does not prevent the chatbot from learning from and propagating false information when requests are made at an acceptable rate.

Why C is Wrong: Transfer learning is a training technique that adapts knowledge from one domain to another. It is a model development approach, not a runtime control that prevents users from injecting false information into a deployed chatbot.

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: 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: AI systems can inadvertently reveal sensitive information such as PII, credentials, or internal data in their outputs when not properly controlled. Sensitive information disclosure is a critical OWASP LLM Top 10 risk. CompTIA SecAI+ Study Guide covers both vulnerability identification and appropriate data protection controls for AI outputs.

Why D is Correct: The scenario describes the AI system outputting sensitive information in its responses, which is a sensitive information disclosure vulnerability. The appropriate control is masking, which replaces sensitive data values such as credit card numbers, SSNs, or API keys with redacted or tokenized equivalents in the model ' s outputs before they are returned to users. This prevents the AI from disclosing sensitive data while still providing useful responses.

Why A is Wrong: Prompt injection involves crafting inputs to override model instructions. If the penetration test revealed sensitive information, the primary vulnerability is the disclosure of that sensitive data, not the injection mechanism itself. EDR monitors endpoint behavior, not AI output content.

Why B is Wrong: Model hallucinations produce fabricated information rather than disclosing real sensitive data. The described scenario involves actual sensitive information being revealed, not fictitious content generation.

Why C is Wrong: Jailbreaking circumvents safety restrictions but the primary harm demonstrated is sensitive data exposure. RBAC manages access permissions but does not prevent the model from including sensitive data in responses once access is granted.

Why E is Wrong: Role impersonation involves the AI pretending to be a different entity. This may be a secondary technique used by the penetration tester but the primary vulnerability described is the disclosure of actual sensitive information in the output.