Get up-to-date Real Exam Questions for IIBA-CCA UPDATED [2026]
Pass IIBA IIBA-CCA Exam in First Attempt Guaranteed
NEW QUESTION # 28
The hash function supports data in transit by ensuring:
- A. a public key is transitioned into a private key.
- B. encrypted messages are not shared with another party.
- C. validation that a message originated from a particular user.
- D. a message was modified in transit.
Answer: D
Explanation:
A cryptographic hash function supports data in transit primarily by providing integrity assurance. When a sender computes a hash (digest) of a message and the receiver recomputes the hash after receipt, the two digests should match if the message arrived unchanged. If the message is altered in any way while traveling across the network-whether by an attacker, a faulty intermediary device, or transmission errors-the recomputed digest will differ from the original. This difference is the key signal that the message was modified in transit, which is what option B expresses. In practical secure-transport designs, hashes are typically combined with a secret key or digital signature so an attacker cannot simply modify the message and generate a new valid digest. Examples include HMAC for message authentication and digital signatures that hash the content and then sign the hash with a private key. These mechanisms provide integrity and, when keyed or signed, also provide authentication and non-repudiation properties.
Option A is more specifically about authentication of origin, which requires a keyed construction such as HMAC or a signature scheme; a plain hash alone cannot prove who sent the message. Option C is incorrect because keys are not "converted" from public to private. Option D relates to confidentiality, which is provided by encryption, not hashing. Therefore, the best answer is B because hashing enables detection of message modification during transit.
NEW QUESTION # 29
ITIL Information Technology Infrastructure Library defines:
- A. a set of security requirements that every business technology system must meet.
- B. how technology and hardware systems interface securely with one another.
- C. the standard set of components used in every business technology system.
- D. a standard of best practices for IT Service Management.
Answer: D
Explanation:
ITIL is a widely adopted framework that defines best-practice guidance for IT Service Management. Its focus is on how organizations design, deliver, operate, and continually improve IT services so they reliably support business outcomes. In cybersecurity and service delivery documentation, ITIL is often referenced because strong service management processes are foundational to secure operations. For example, ITIL practices such as incident management, problem management, change enablement, configuration management, and service continuity help ensure security controls are implemented consistently and that deviations are identified, tracked, and corrected.
ITIL does not define how hardware systems interface securely with one another; that is more aligned with architecture standards, security engineering, and network or platform design frameworks. It also does not prescribe a universal set of components for every technology system; that belongs to reference architectures and enterprise architecture standards. Likewise, ITIL is not primarily a security requirements standard. While ITIL supports security governance through practices like risk management, access management, and information security management integration, it does not itself serve as a mandatory security control catalog.
From a cybersecurity perspective, ITIL contributes by promoting repeatable processes, clear roles and responsibilities, measurable service levels, and continual improvement. These elements reduce operational risk, improve response effectiveness, and strengthen accountability-key requirements for maintaining confidentiality, integrity, and availability in production environments.
NEW QUESTION # 30
What operational practice would risk managers employ to demonstrate the effectiveness of security controls?
- A. Change Management
- B. Penetration Testing
- C. Security Awareness Training
- D. Metrics Reporting
Answer: D
Explanation:
Risk managers demonstrate the effectiveness of security controls by using metrics reporting because metrics provide objective, repeatable evidence that controls are operating as intended and are producing measurable outcomes. In cybersecurity governance, "control effectiveness" is shown through performance indicators and trend data, not just by stating that a control exists. Metrics translate technical activity into risk-relevant results that leadership can understand and act on.
Common control-effectiveness metrics include patch compliance rates and time-to-remediate critical vulnerabilities, percentage of systems meeting secure configuration baselines, multifactor authentication coverage, privileged access review completion rates, mean time to detect and respond, incident volume and severity trends, phishing simulation outcomes, and the percentage of logs successfully collected and retained for monitoring. Risk managers also use key risk indicators to track whether residual risk is increasing or decreasing, and they compare results against defined thresholds and risk appetite.
While penetration testing can validate exposure and reveal weaknesses, it is periodic and scenario-based; it does not continuously demonstrate ongoing control performance across the environment. Change management is essential for stability and risk reduction, but it is a process control rather than a reporting practice used to demonstrate effectiveness. Security awareness training improves user behavior, yet effectiveness still needs measurement through metrics such as completion rates and simulated phishing results. Therefore, metrics reporting is the operational practice most directly used to demonstrate control effectiveness.
NEW QUESTION # 31
What is an embedded system?
- A. It provides computing services in a small form factor with limited processing power
- B. It safeguards the cryptographic infrastructure by storing keys inside a tamper-resistant external device
- C. A system that is located in a secure underground facility
- D. A system placed in a location and designed so it cannot be easily removed
Answer: A
Explanation:
An embedded system is a specialized computing system designed to perform a dedicated function as part of a larger device or physical system. Unlike general-purpose computers, embedded systems are built to support a specific mission such as controlling sensors, actuators, communications, or device logic in products like routers, printers, medical devices, vehicles, industrial controllers, and smart appliances. Cybersecurity documentation commonly highlights that embedded systems tend to operate with constrained resources, which may include limited CPU power, memory, storage, and user interface capabilities. These constraints affect both design and security: patching may be harder, logging may be minimal, and security features must be carefully engineered to fit the platform's limitations.
Option C best matches this characterization by describing a small form factor and limited processing power, which are typical attributes of many embedded devices. While not every embedded system is "small," the key idea is that it is purpose-built, resource-constrained, and tightly integrated into a larger product.
The other options describe different concepts. A secure underground facility relates to physical site security, not embedded computing. Being hard to remove is about physical installation or tamper resistance, which can apply to many systems but is not what defines "embedded." Storing cryptographic keys in a tamper-resistant external device describes a hardware security module or secure element use case, not the general definition of an embedded system.
NEW QUESTION # 32
A software product that supports threat detection, and compliance and security incident management, through the collection and analysis of security events and other data sources, is known as a:
- A. software as a service (SaaS).
- B. threat risk assessment (TRA).
- C. security information and event management system (SIEM).
- D. cloud access security broker (CASB).
Answer: C
Explanation:
A security information and event management system (SIEM) is designed to centralize and analyze security-relevant data to support threat detection, compliance reporting, and incident management. SIEM platforms ingest logs and telemetry from many sources such as servers, endpoints, network devices, firewalls, intrusion detection systems, identity providers, cloud services, and business applications. They normalize and correlate these events so analysts can identify suspicious patterns that would be difficult to see in isolated logs, such as repeated failed logins followed by a successful login from an unusual location, privilege escalation, lateral movement indicators, or abnormal data access.
Cybersecurity operational guidance emphasizes SIEM value in three main areas. First, detection and alerting: correlation rules, behavioral analytics, and threat intelligence enrichment help surface high-risk activity. Second, incident response support: SIEM provides timelines, evidence preservation, triage context, and query capabilities that help responders scope and contain incidents. Third, compliance and audit readiness: centralized log retention, integrity controls, and reporting demonstrate that monitoring and control requirements are operating.
The other options do not match the definition. SaaS is a delivery model, not a specific security monitoring capability. A threat risk assessment is a process, not a software product for event collection and correlation. A CASB focuses on governing and protecting cloud application usage, whereas SIEM focuses on cross-environment event aggregation, correlation, and security operations monitoring.
NEW QUESTION # 33
NIST 800-30 defines cyber risk as a function of the likelihood of a given threat-source exercising a potential vulnerability, and:
- A. the resulting impact of that adverse event on the organization.
- B. the effectiveness of the control assurance framework.
- C. the pre-disposing conditions of the vulnerability.
- D. the probability of detecting damage to the infrastructure.
Answer: A
Explanation:
NIST SP 800-30 describes risk using a classic risk model: risk is a function of likelihood and impact. In this model, a threat-source may exploit a vulnerability, producing a threat event that results in adverse consequences. The likelihood component reflects how probable it is that a threat event will occur and successfully cause harm, considering factors such as threat capability and intent (or in non-adversarial cases, the frequency of hazards), the existence and severity of vulnerabilities, exposure, and the strength of current safeguards. However, likelihood alone does not define risk; a highly likely event that causes minimal harm may be less important than a less likely event that causes severe harm.
The second required component is the impact-the magnitude of harm to the organization if the adverse event occurs. Impact is commonly evaluated across mission and business outcomes, including financial loss, operational disruption, legal or regulatory consequences, reputational damage, and loss of confidentiality, integrity, or availability. This is why option D is correct: NIST's definition explicitly ties the risk expression to the resulting impact on the organization.
The other options may influence likelihood assessment or control selection, but they are not the missing definitional element. Detection probability and control assurance relate to monitoring and governance; predisposing conditions can shape likelihood. None replace the
NEW QUESTION # 34
The process by which organizations assess the data they hold and the level of protection it should be given based on its risk to loss or harm from disclosure, is known as:
- A. information categorization.
- B. information classification.
- C. internal audit.
- D. vulnerability assessment.
Answer: B
Explanation:
Information classification is the formal process of evaluating the data an organization creates or holds and assigning it a sensitivity level so the organization can apply the right safeguards. Cybersecurity policies describe classification as the foundation for consistent protection because it links the potential harm from unauthorized disclosure, alteration, or loss to specific handling and control requirements. Typical classification labels include Public, Internal, Confidential, and Restricted, though names vary by organization. Once data is classified, required protections can be specified, such as encryption at rest and in transit, access restrictions based on least privilege, approved storage locations, monitoring requirements, retention periods, and secure disposal methods.
This is not a vulnerability assessment, which focuses on identifying weaknesses in systems, applications, or configurations. It is also not an internal audit, which evaluates whether controls and processes are being followed and are effective. Option D, information categorization, is often used in some frameworks to describe assigning impact levels (for example, confidentiality, integrity, availability impact) to information types or systems, mainly to drive control baselines. While related, the question specifically emphasizes assessing data and deciding the level of protection based on risk from disclosure, which aligns most directly with classification programs used to govern labeling and handling rules across the organization.
A strong classification program improves security consistency, supports compliance, reduces accidental exposure, and helps prioritize controls for the most sensitive information assets.
NEW QUESTION # 35
Compliance with regulations is generally demonstrated through:
- A. penetration testing by ethical hackers.
- B. independent audits of systems and security procedures.
- C. extensive QA testing prior to system implementation.
- D. review of security requirements by senior executives and/or the Board.
Answer: B
Explanation:
Regulatory compliance is generally demonstrated through independent audits because regulators, customers, and partners typically require objective evidence that required controls exist and operate effectively. An independent audit is performed by a qualified party that is not responsible for running the controls being assessed, which strengthens credibility and reduces conflicts of interest. Cybersecurity and governance documents describe audits as a formal method to verify compliance against defined criteria such as laws, regulations, contractual obligations, or control frameworks. Auditors review policies and procedures, inspect system configurations, sample access and change records, evaluate logging and monitoring, test incident response evidence, and validate that controls are consistently performed over time. The outcome is usually a report, attestation, or findings with remediation plans-artifacts commonly used to prove compliance.
A Board or executive review supports governance and oversight, but it does not, by itself, provide independent verification that controls are functioning. QA testing focuses on product quality and functional correctness; it may include security testing but does not typically satisfy regulatory evidence requirements for ongoing operational controls. Penetration testing is valuable for identifying exploitable weaknesses, yet it is a point-in-time technical exercise and does not comprehensively demonstrate compliance with procedural, administrative, and operational requirements such as access governance, retention, training, vendor oversight, and continuous monitoring. Therefore, independent audits are the standard mechanism to demonstrate compliance in a defensible, repeatable way.
NEW QUESTION # 36
SSL/TLS encryption capability is provided by:
- A. controls.
- B. protocols.
- C. certificates.
- D. passwords.
Answer: B
Explanation:
SSL and its successor TLS are cryptographic protocols designed to provide secure communications over untrusted networks. The encryption capability comes from the TLS protocol suite, which defines how two endpoints negotiate security settings, authenticate, exchange keys, and protect data as it travels between them. During the TLS handshake, the endpoints agree on a cipher suite, establish shared session keys using secure key exchange methods, and then use symmetric encryption and integrity checks to protect application data against eavesdropping and tampering. Because TLS specifies these mechanisms and the sequence of steps, it is accurate to say that encryption capability is provided by protocols.
Certificates are important but they are not the encryption mechanism itself. Digital certificates primarily support authentication and trust by binding a public key to an identity and enabling verification through a trusted certificate authority chain. Certificates help prevent impersonation and man-in-the-middle attacks by allowing clients to validate the server's identity, and in mutual TLS they can validate both parties. However, certificates alone do not define how encryption is negotiated or applied; TLS does.
Passwords are unrelated to transport encryption; they are an authentication secret and do not provide session encryption for network traffic. "Controls" is too general: SSL/TLS is indeed a security control, but the question asks specifically what provides the encryption capability. That capability is implemented and standardized by the SSL/TLS protocols, which orchestrate key establishment and encrypted communication.
NEW QUESTION # 37
What is defined as an internal computerized table of access rules regarding the levels of computer access permitted to login IDs and computer terminals?
- A. Directory Management System
- B. Access Control List
- C. Access Control Entry
- D. Relational Access Database
Answer: B
Explanation:
An Access Control List (ACL) is a structured, system-maintained list of authorization rules that specifies who or what is allowed to access a resource and what actions are permitted. In many operating systems, network devices, and applications, an ACL functions as an internal table that maps identities such as user IDs, group IDs, service accounts, or even device/terminal identifiers to permissions like read, write, execute, modify, delete, or administer. When a subject attempts to access an object, the system consults the ACL to determine whether the requested operation should be allowed or denied, enforcing the organization's security policy at runtime.
The description in the question matches the classic definition of an ACL as a computerized table of access rules tied to login IDs and sometimes the originating endpoint or terminal context. ACLs are central to implementing discretionary access control and are also widely used in networking (for example, permitting or denying traffic flows based on source/destination and ports) and file systems (controlling access to folders and files).
An Access Control Entry (ACE) is only a single line item within an ACL (one rule for one subject). A "Relational Access Database" is not a standard security control term for authorization tables. A "Directory Management System" manages identities and groups, but it is not the same as the enforcement list attached to a specific resource. Therefore, the correct answer is Access Control List.
NEW QUESTION # 38
What privacy legislation governs the use of healthcare data in the United States?
- A. PIPEDA
- B. HIPAA
- C. PCI-DSS
- D. Privacy Act
Answer: B
Explanation:
In the United States, HIPAA, the Health Insurance Portability and Accountability Act, is the primary federal framework that governs how certain healthcare information must be protected and used. In cybersecurity and compliance documentation, HIPAA is most often discussed through its implementing rules, especially the Privacy Rule and the Security Rule. The Privacy Rule establishes when protected health information may be used or disclosed and grants individuals rights over their health information. The Security Rule focuses specifically on safeguarding electronic protected health information by requiring administrative, physical, and technical safeguards.
From a security controls perspective, HIPAA-driven programs typically include risk analysis and risk management, policies and workforce training, access controls based on least privilege, unique user identification, authentication controls, audit logging, integrity protections, transmission security such as encryption for data in transit, and contingency planning such as backups and disaster recovery. HIPAA also expects organizations to manage third-party risk through appropriate agreements and oversight when vendors handle protected health information.
The other options do not fit the question. The Privacy Act generally applies to U.S. federal agencies' handling of personal records, PIPEDA is a Canadian privacy law, and PCI-DSS is an industry security standard focused on payment card data rather than healthcare data. Therefore, HIPAA is the correct legislation for U.S. healthcare data protection requirements.
NEW QUESTION # 39
In the OSI model for network communication, the Session Layer is responsible for:
- A. presenting data to the receiver in a form that it recognizes.
- B. adding appropriate network addresses to packets.
- C. establishing a connection and terminating it when it is no longer needed.
- D. transmitting the data on the medium.
Answer: C
Explanation:
The OSI Session Layer (Layer 5) is responsible for establishing, managing, and terminating sessions between communicating applications. A session is the logical dialogue that allows two endpoints to coordinate how communication starts, how it continues, and how it ends. This includes controlling the "conversation" state, such as who can transmit at what time, maintaining the session so it stays active, and closing it cleanly when it is no longer needed. Because of this, option A best matches the Session Layer's core responsibilities.
In contrast, presenting data to the receiver in a recognizable form is the job of the Presentation Layer (Layer 6), which deals with formatting, encoding, compression, and often cryptographic transformation concepts. Adding appropriate network addresses to packets aligns to the Network Layer (Layer 3), where logical addressing and routing decisions occur, typically associated with IP addressing. Transmitting the data on the medium is handled at the Physical Layer (Layer 1), which concerns signals, cabling, and the actual movement of bits.
From a cybersecurity perspective, session management is important because weaknesses can enable session hijacking, replay, or fixation, especially when session identifiers are predictable, not protected, or not properly invalidated. Controls commonly include strong authentication, secure session token generation, timeout and reauthentication rules, and proper session termination to reduce exposure.
NEW QUESTION # 40
What common mitigation tool is used for directly handling or treating cyber risks?
- A. Standards
- B. Exit Strategy
- C. Business Continuity Plan
- D. Control
Answer: D
Explanation:
In cybersecurity risk management, risk treatment is the set of actions used to reduce risk to an acceptable level. The most common tool used to directly treat or mitigate cyber risk is a control because controls are the specific safeguards that prevent, detect, or correct adverse events. Cybersecurity frameworks describe controls as measures implemented to reduce either the likelihood of a threat event occurring or the impact if it does occur. Controls can be technical (such as multifactor authentication, encryption, endpoint protection, network segmentation, logging and monitoring), administrative (policies, standards, training, access approvals, change management), or physical (badges, locks, facility protections). Regardless of type, controls are the direct mechanism used to mitigate identified risks.
An exit strategy is typically a vendor or outsourcing risk management concept focused on how to transition away from a provider or system; it supports resilience but is not the primary tool for directly mitigating a specific cyber risk. Standards guide consistency by defining required practices and configurations, but the standard itself is not the mitigation-controls implemented to meet the standard are. A business continuity plan supports availability and recovery after disruption, which is important, but it primarily addresses continuity and recovery rather than directly reducing the underlying cybersecurity risk in normal operations. Therefore, the best answer is the one that represents the direct implementation of safeguards: controls.
NEW QUESTION # 41
Information classification of data is a level of protection that is based on an organization's:
- A. need for access by employees.
- B. risk to loss or harm from disclosure.
- C. retention for auditing purposes.
- D. timing of availability for automated systems.
Answer: B
Explanation:
Information classification is the practice of assigning data a sensitivity level so the organization can apply protections that match the business impact if the information is exposed, altered, or becomes unavailable. The core driver for classification is the risk of harm-especially harm caused by unauthorized disclosure. If disclosure would result in regulatory penalties, reputational damage, competitive disadvantage, contractual breach, or harm to customers and employees, the data is classified at a higher level and requires stronger controls. These controls commonly include tighter access restrictions (least privilege and role-based access), stronger authentication, encryption at rest and in transit, stricter handling and sharing rules, audit logging, monitoring, and secure disposal requirements.
While retention can be influenced by compliance obligations, it is not what determines the classification level; retention policies typically reference classification but do not define it. "Need for access" is managed through access control decisions, which are applied after the data's sensitivity is understood; classification informs who should have access, not the other way around. "Timing of availability" relates to availability requirements and service resilience, which are important, but classification schemes primarily focus on sensitivity and potential damage from inappropriate exposure, with integrity and availability considerations often handled as additional impact dimensions.
Therefore, the best verified basis for information classification is the organization's assessment of risk of loss or harm from disclosure.
NEW QUESTION # 42
Which scenario is an example of the principle of least privilege being followed?
- A. Certain users are granted administrative access to their network account, in case they need to install a web-app
- B. A manager who is conducting performance appraisals is granted access to HR files for all employees
- C. An application administrator has full permissions to only the applications they support
- D. All application and database administrators have full permissions to every application in the company
Answer: C
Explanation:
The principle of least privilege requires that users, administrators, services, and applications are granted only the minimum access necessary to perform authorized job functions, and nothing more. Option A follows this principle because the administrator's elevated permissions are limited in scope to the specific applications they are responsible for supporting. This reduces the attack surface and limits blast radius: if that administrator account is compromised, the attacker's reach is constrained to only those applications rather than the entire enterprise environment.
Least privilege is typically implemented through role-based access control, separation of duties, and privileged access management practices. These controls ensure privileges are assigned based on defined roles, reviewed regularly, and removed when no longer required. They also promote using standard user accounts for routine tasks and reserving administrative actions for controlled, auditable sessions. In addition, least privilege supports stronger accountability through logging and change tracking, because fewer people have the ability to make high-impact changes across systems.
The other scenarios violate least privilege. Option B grants excessive enterprise-wide permissions, creating unnecessary risk and enabling widespread damage from mistakes or compromise. Option C provides "just in case" administrative access, which cybersecurity guidance explicitly discourages because it increases exposure without a validated business need. Option D is overly broad because access to all HR files exceeds what is required for performance appraisals, which typically should be limited to relevant employee records only.
NEW QUESTION # 43
What terms are often used to describe the relationship between a sub-directory and the directory in which it is cataloged?
- A. Embedded Layers
- B. Parent and Child
- C. Multi-factor Tokens
- D. Primary and Secondary
Answer: B
Explanation:
Directories are commonly organized in a hierarchical structure, where each directory can contain sub-directories and files. In this hierarchy, the directory that contains another directory is referred to as the parent, and the contained sub-directory is referred to as the child. This parent-child relationship is foundational to how file systems and many directory services represent and manage objects, including how paths are constructed and how inheritance can apply.
From a cybersecurity perspective, understanding parent and child relationships matters because access control and administration often follow the hierarchy. For example, permissions applied at a parent folder may be inherited by child folders unless inheritance is explicitly broken or overridden. This can simplify administration by allowing consistent access patterns, but it also introduces risk: overly permissive settings at a parent level can unintentionally grant broad access to many child locations, increasing the chance of unauthorized data exposure. Security documents therefore emphasize careful design of directory structures, least privilege at higher levels of the hierarchy, and regular permission reviews to detect privilege creep and misconfigurations.
The other options do not describe this standard hierarchy terminology. "Primary and Secondary" is more commonly used for redundancy or replication roles, not directory relationships. "Multi-factor Tokens" relates to authentication factors. "Embedded Layers" is not a st
NEW QUESTION # 44
Violations of the EU's General Data Protection Regulations GDPR can result in:
- A. fines of €20 million or 4% of annual turnover, whichever is greater.
- B. mandatory upgrades of the security infrastructure.
- C. a complete audit of the enterprise's security processes.
- D. fines of €20 million or 4% of annual turnover, whichever is less.
Answer: A
Explanation:
The GDPR establishes a regulatory penalty framework intended to make privacy and data-protection obligations enforceable across organizations of any size. Under GDPR, the most severe administrative fines can reach up to €20 million or up to 4% of the organization's total worldwide annual turnover of the preceding financial year, whichever is higher. That "whichever is greater" clause is critical: it prevents large enterprises from treating privacy violations as a minor cost of doing business and ensures the sanction can scale with the organization's economic size and risk impact.
Cybersecurity governance and risk documents typically emphasize GDPR as a driver for enterprise risk management because the consequences extend beyond monetary fines. A confirmed violation often triggers regulatory investigations, mandatory corrective actions, and potential restrictions on processing activities. Organizations may also face indirect impacts such as breach notification costs, legal claims from affected individuals, reputational harm, loss of customer trust, and increased oversight by regulators and auditors.
From a controls perspective, GDPR penalties reinforce the need for strong security and privacy-by-design practices: data minimization, lawful processing, documented purposes, retention controls, encryption where appropriate, access control and least privilege, monitoring and incident response readiness, and evidence-based accountability through policies, records, and audit trails. Selecting option C correctly reflects GDPR's maximum fine structure and its risk-based deterrence model.
NEW QUESTION # 45
What is the first step of the forensic process?
- A. Examination
- B. Collection
- C. Analysis
- D. Reporting
Answer: B
Explanation:
The first step in a standard digital forensic process is collection because all later work depends on obtaining data in a way that preserves its integrity and evidentiary value. Collection involves identifying potential sources of relevant evidence and then acquiring it using controlled, repeatable methods. Typical sources include endpoint disk images, memory captures, mobile device extractions, server and application logs, cloud audit trails, email records, firewall and proxy logs, and authentication events. During collection, forensic guidance emphasizes maintaining a documented chain of custody, recording who handled the evidence, when it was acquired, how it was transported and stored, and what tools and settings were used. This documentation supports accountability and helps ensure evidence is admissible and defensible if used in disciplinary actions, regulatory inquiries, or legal proceedings.
Collection also includes steps to prevent evidence contamination or loss. Investigators may isolate systems to stop further changes, capture volatile data such as RAM before shutdown, use write blockers when imaging storage media, verify acquisitions with cryptographic hashes, and securely store originals while performing analysis on validated copies. Only after evidence is collected and preserved do teams move into examination and analysis, where artifacts are filtered, parsed, correlated, and interpreted to reconstruct timelines and determine cause and scope. Reporting comes later to communicate findings and support remediation.
NEW QUESTION # 46
What should organizations do with Key Risk Indicator KRI and Key Performance Indicator KPI data to facilitate decision making, and improve performance and accountability?
- A. Challenge, compare, and revise
- B. Collect, analyze, and report
- C. Prioritize, falsify, and report
- D. Achieve, reset, and evaluate
Answer: B
Explanation:
KRIs and KPIs are only useful when they are handled as part of a disciplined measurement lifecycle. Cybersecurity governance guidance emphasizes three essential activities: collect, analyze, and report. Organizations must first collect KRI and KPI data consistently from reliable sources such as vulnerability scanners, SIEM logs, IAM systems, ticketing platforms, and asset inventories. Collection requires defined metric owners, clear definitions, standardized time windows, and data quality checks so results are comparable across periods and business units.
Next, organizations analyze the data to understand what it means for risk and performance. Analysis includes trending over time, comparing results to targets and thresholds, correlating indicators to business outcomes, identifying outliers, and determining root causes. For KRIs, analysis highlights rising exposure or control breakdowns such as increasing critical vulnerabilities beyond SLA. For KPIs, analysis evaluates operational effectiveness such as mean time to detect and mean time to remediate.
Finally, organizations report results to the right audiences with the right level of detail. Reporting supports accountability by assigning actions, tracking remediation progress, and escalating when thresholds are exceeded. It also supports decision making by showing where investment, staffing, or control changes will have the greatest risk-reduction and performance impact. The other options are not standard, auditable metric management activities and do not reflect the established lifecycle used in cybersecurity measurement programs.
NEW QUESTION # 47
Which of the following would qualify as a multi-factor authentication pair?
- A. Something You Know and Something You Are
- B. Password and Token
- C. Encryption and Password
- D. Thumbprint and Encryption
Answer: A
Explanation:
Multi-factor authentication requires a user to prove identity using two or more different factor types. Cybersecurity standards describe the main factor categories as something you know (for example, a password or PIN), something you have (for example, a hardware token, smart card, or authenticator app producing a one-time code), and something you are (biometrics such as fingerprint, face, or iris). A valid MFA pair must come from different categories, not just two items from the same category or a mix of authentication with non-authentication concepts.
Option B is correct because it explicitly combines two distinct factor types: a knowledge factor and an inherence factor. This pairing is widely recognized as MFA because compromising one factor does not automatically compromise the other: an attacker who steals a password still needs the biometric, and spoofing a biometric does not provide the secret knowledge factor.
Option A is incorrect because "encryption" is not an authentication factor; it is a protection mechanism for confidentiality and integrity of data. Option D has the same problem: encryption is not a user factor. Option C can represent MFA in many real implementations if "token" is truly a possession factor; however, training materials and exam items often prefer the clearest, unambiguous factor-language pairing, which is why "Something You Know and Something You Are" is the best single answer here.
NEW QUESTION # 48
......
IIBA IIBA-CCA Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
| Topic 4 |
|
IIBA IIBA-CCA Study Guide Archives : https://pass4sure.guidetorrent.com/IIBA-CCA-dumps-questions.html