Free Practice Questions for CompTIA CY0-001 Exam

Basic Concept: Security posture management for AI systems involves assessing and improving the overall security state of AI deployments, including identifying risks, implementing controls, and maintaining ongoing compliance. Appropriate frameworks provide structure for this assessment. CompTIA SecAI+ Study Guide identifies NIST AI RMF as the primary framework for AI risk and posture management.

Why B is Correct: The NIST AI Risk Management Framework provides comprehensive, actionable guidance for managing and improving AI security and risk posture across the entire AI lifecycle. It includes the GOVERN, MAP, MEASURE, and MANAGE functions that directly address posture management activities including risk identification, assessment, and control implementation for ML use cases. Its technical depth and ML-specific guidance make it ideal for this summarization task.

Why A is Wrong: OECD standards provide high-level policy principles for AI governance at an international level. They lack the technical specificity and operational guidance needed to summarize posture management impact on a specific ML use case.

Why C is Wrong: The EU AI Act is a regulatory compliance framework establishing legal requirements for AI systems. While it addresses risk management, its focus is on legal compliance rather than technical posture management guidance for ML systems.

Why D is Wrong: A Generative Adversarial Network is an AI architecture for generating synthetic data, not a framework or standard. It has no relevance as a reference for AI security posture management.

Option A is correct because a system prompt contains the developer- or platform-defined instructions that establish how the AI should behave throughout an interaction. It can define the model’s role, objectives, prohibited actions, response style, tool-use boundaries, and security constraints before the user submits a request. That description matches an input supplied by a developer to govern later AI interactions. Option B is the end user’s prompt or request; it expresses what the user wants in a particular turn and normally has lower authority than system-level instructions. Option C, zero-shot prompting, describes asking the model to perform a task without providing an example. Option D, multi-shot prompting, supplies multiple examples to demonstrate the desired input or output pattern. Neither zero-shot nor multi-shot identifies the authority or source of the instruction. In a secure AI application, system instructions should be protected from unauthorized modification, tested for conflicts, and reinforced with technical controls rather than treated as the sole security boundary. The essential distinction is prompt hierarchy: system instructions configure persistent behavior, while user prompts request individual tasks.

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

Option D is correct because the failure is an authorization problem: every external customer can receive sensitive information even though only some customers are permitted to use it. Role-based access control assigns permissions to defined customer roles and requires the API to evaluate the caller’s role before returning protected fields or invoking sensitive model functions. Properly implemented, RBAC supports least privilege and separates ordinary customers from approved sensitive-data users. Option A may route customers to different models, but model selection does not itself enforce who is authorized to receive data. Option B changes model behavior and training data, yet retraining cannot replace an access-control decision at the API boundary. Option C may improve network isolation, but placing the model in a VPC does not stop an authenticated external customer from receiving information that the API exposes. The organization should also apply field-level filtering, deny-by-default policies, logging, and authorization testing. NIST’s RBAC model assigns users to roles and associates each role with permitted privileges, directly supporting this control.

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

Data leakage is the most applicable risk because an internal chatbot commonly interacts with organizational information that may include confidential documents, customer information, employee records, credentials, intellectual property, and other sensitive content. CompTIA SecAI+ specifically identifies accidental data leakage as an AI risk and sensitive information disclosure as an attack or failure condition affecting AI systems. Internal chatbots can expose information when retrieval permissions are too broad, conversation context crosses security boundaries, prompts contain confidential material, or model responses reproduce information that the requesting user should not receive. Prompt injection is an important chatbot attack vector, but it describes deliberate manipulation of model instructions rather than the broader organizational risk emphasized here. Model theft concerns unauthorized acquisition or reproduction of a model. Unauthorized access concerns gaining access to resources without proper authorization and is generally addressed through model, data, agent, network, and API access controls. In contrast, information leakage can occur even when legitimate employees are using the chatbot normally. Protecting sensitive data through access controls, minimization, masking, classification, and monitoring is therefore fundamental to internal chatbot security.

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

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: Advances in AI generative technology have enabled the creation of highly realistic synthetic video and audio content that convincingly impersonates real individuals. These AI-generated impersonations are called deepfakes and represent a significant threat for corporate fraud, misinformation, and social engineering. CompTIA SecAI+ covers deepfakes under basic AI concepts and cybersecurity threats.

Why C is Correct: The scenario describes a video in which the CEO ' s likeness was convincingly replicated to deliver a false message about bankruptcy. This is a textbook deepfake attack — AI-generated synthetic media using the target ' s face and potentially voice to make it appear they said something they never said. Deepfake technology uses GANs and CNNs to create this type of convincing impersonation, and the attack specifically exploited AI generation for deception.

Why A is Wrong: An on-path attack intercepts network communications between two parties to eavesdrop or modify traffic. It requires positioning in the network path, not creating synthetic media of a person ' s likeness.

Why B is Wrong: Phishing is a social engineering attack that uses deceptive messages typically via email to trick recipients into taking harmful actions such as clicking malicious links or providing credentials. While this attack has social engineering elements, the use of AI-generated video to impersonate the CEO specifically categorizes it as a deepfake attack.

Why D is Wrong: Social engineering broadly describes psychological manipulation tactics to deceive individuals. While deepfakes can be used as part of social engineering campaigns, the specific technical technique used — AI-generated synthetic video — makes deepfake the most precise and accurate categorization.

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.

Basic Concept: Threat modeling for any system, and especially for agentic AI systems with multiple interacting components, begins with understanding the system ' s architecture and where trust boundaries exist. Trust boundaries define where data and control flows cross between components with different trust levels, representing potential attack surfaces. CompTIA SecAI+ Study Guide aligns with STRIDE and MITRE ATLAS threat modeling methodologies.

Why B is Correct: Identifying trust boundaries between components is the foundational first step in threat modeling. Agentic systems often involve multiple components such as the orchestrator, tools, APIs, data sources, and external services with different trust levels. Understanding where these boundaries exist reveals where untrusted inputs cross into trusted components, enabling the architect to systematically identify threats at each boundary before proceeding to risk quantification and control application.

Why A is Wrong: Applying compensating controls based on exposure findings is the final step in threat modeling, occurring after threats have been identified and risks quantified. Controls cannot be appropriately designed without first understanding the system ' s trust boundaries and threat landscape.

Why C is Wrong: Calculating risk to resources based on data sensitivity is a risk assessment step that occurs after trust boundaries are mapped and potential threats are identified. Risk quantification requires knowing what threats exist at each boundary first.

Why D is Wrong: Scanning for OWASP Top 10 vulnerabilities is a technical vulnerability assessment activity. While valuable, it comes after the architectural analysis of trust boundaries and threat identification phases of threat modeling.

Basic Concept: Cybersecurity threats evolve continuously, with new attack variants emerging regularly. The choice between traditional statistical models and ML models for attack classification depends on which better handles the complexity and dynamism of the threat landscape. CompTIA SecAI+ covers ML model advantages for cybersecurity under basic AI concepts.

Why A is Correct: ML models can learn arbitrarily complex, non-linear relationships from training data and adapt to new patterns when retrained with updated data. For attack classification, this means ML can recognize sophisticated, multi-feature attack patterns that exceed the capabilities of simple statistical models and can be updated to detect new attack variants as the threat landscape evolves. This adaptability to complex and changing problems is the primary reason analysts prefer ML over static statistical approaches.

Why B is Wrong: ML model development pipelines are generally more complex than statistical models, requiring data preparation, feature engineering, model selection, training, validation, and deployment steps. Simplicity of development is not a characteristic advantage of ML over statistical models.

Why C is Wrong: ML models typically require large amounts of training data to perform well. Statistical models often perform better than ML with small datasets. Performance with small datasets is actually an advantage of statistical models over ML, not ML over statistical.

Why D is Wrong: Community support and expert availability are ecosystem considerations rather than technical reasons to prefer ML for cybersecurity classification tasks. These factors might influence tool selection but do not explain the fundamental technical preference for ML ' s superior handling of complex attack patterns.

Data balancing is the process specifically intended to correct disproportionate class distributions within a machine learning dataset. CompTIA SecAI+ lists data balancing as a distinct data-processing concept alongside data cleansing, verification, lineage, provenance, and augmentation. When one class substantially outnumbers another, the model may learn to favor the dominant class and perform poorly on underrepresented examples. Balancing techniques can modify this distribution through approaches such as oversampling minority classes, undersampling majority classes, assigning class weights, or generating suitable additional minority examples. The objective is to give the model adequate exposure to each relevant class and improve generalization across the complete problem space. Data augmentation creates additional or modified training examples and can sometimes contribute to balancing, but augmentation is broader and does not specifically mean adjusting class distribution. Data lineage records where data originated and how it changed throughout its lifecycle. Data cleansing removes or corrects inaccurate, duplicate, malformed, or otherwise unsuitable records. Because the question specifically asks about changing the representation of underrepresented classes, data balancing is the precise CompTIA concept being tested.

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