The most important input into the assessment of the risk of shadow IT usage is the classification of the data that is being processed, stored, or transmitted by the unauthorized applications or devices. This determines the level of confidentiality, integrity, and availability that is required for the data and the potential impact of a breach or loss. Business benefits of shadow IT, application-related expenses, and volume of data are less important inputs that may affect the risk analysis, but not as much as the data classification. References = Risk IT Framework, 2nd Edition, page 28; CRISC Review Manual, 6th Edition, page 98.

Key Control Indicators (KCIs) are metrics used to monitor the performance of controls. Their primary benefit is the early detection of control degradation, allowing organizations to take corrective actions before issues escalate into significant problems.
Reference:ISACA CRISC Review Manual, 7th Edition, Chapter 3: Risk Response and Reporting, Section:
Control Monitoring and Reporting.

Code review could BEST detect an in-house developer inserting malicious functions into a web-based application, because it is a process that involves examining and verifying the source code of the application for any errors, vulnerabilities, or malicious functions. Code review can help to identify and remove any unauthorized or harmful code that the developer may have inserted, either intentionally or unintentionally, and to ensure that the application meets the quality and security standards and requirements. The other options are not as effective as code review, because:
Option A: Segregation of duties is a control that involves separating the roles and responsibilities of the developer from those of the tester, the approver, and the deployer, to prevent any conflict of interest or misuse of authority. Segregation of duties can help to reduce the risk of the developer inserting malicious functions into the web-based application, but it does not detect them.
Option C: Change management is a process that involves controlling and documenting any changes to the web-based application, such as new features, enhancements, or bug fixes, to ensure that they are authorized, tested, and approved. Change management can help to track and monitor the changes that the developer may have made to the web-based application, but it does not detect the malicious functions.
Option D: Audit modules are components that are embedded in the web-based application to record and report the activities and transactions that occur within the application, such as user login, data input, or data output.
Audit modules can help to audit and review the performance and functionality of the web-based application, but they do not detect the malicious functions. References = Risk and Information Systems Control Study Manual, 7th Edition, ISACA, 2020, p. 214.

Peak bandwidth usage is the most helpful in defining an early-warning threshold associated with insufficient network bandwidth. Peak bandwidth usage is the maximum amount of data that is transferred over a network connection at a given time. It indicates the highest demand and stress on the network resources and capacity.
By monitoring the peak bandwidth usage, the organization can identify the potential bottlenecks, slowdowns, and disruptions that may occur due to insufficient network bandwidth. The organization can also plan and allocate the network bandwidth accordingly to meet the peak demand and avoid service degradation. The other options are not as helpful as peak bandwidth usage, as they do not reflect the actual or potential network performance issues that may arise due to insufficient network bandwidth. References = Risk and Information Systems Control Study Manual, Chapter 4: Risk and Control Monitoring and Reporting, Section 4.3: Key Risk Indicators, page 197.

The primary consideration for determining recovery priorities in a disaster recovery situation is the impact of business disruption on the organization's mission, objectives, and stakeholders. Business disruption can result in loss of revenue, reputation, customer satisfaction, market share, and competitive advantage. Therefore, the recovery priorities should be based on the criticality of the business processes and functions that support the organization's value proposition and strategic goals. Data security (A), recovery costs (B), and recovery resource availability (D) are important factors, but they are secondary to the impact of business disruption.
Data security should be ensured throughout the recovery process, but it does not determine the recovery order.
Recovery costs should be balanced with the benefits of restoring the business operations, but they do not reflect the urgency of the recovery. Recovery resource availability should be assessed and allocated according to the recovery priorities, but it does not define the recovery sequence. (Risk and Information Systems Control Review Questions, Answers & Explanations Manual, 5th Edition, page 982)