Governing bodies should be formally tasked during business continuity management testing. Managing Cloud principles explain that governance entities provide oversight, accountability, and assurance that continuity objectives align with organizational strategy and risk tolerance.
Their involvement ensures testing outcomes are reviewed at the appropriate level, deficiencies are addressed, and resources are allocated for remediation. Governance participation also supports compliance and audit requirements.
Operational staff and consultants may participate, but formal tasking resides with governing bodies.
Therefore, governing bodies are the correct answer.

Before an application can store a token, it must first receive the token from the tokenization server.
Managing Cloud guidance outlines that tokenization workflows follow a defined sequence: the application submits sensitive data, the tokenization server generates a token, and then the token is returned to the application.
Only after the token has been successfully returned can the application replace the original sensitive data and store the token instead. This ensures that sensitive data is not retained within the application environment, reducing exposure and simplifying compliance requirements.
The other steps occur earlier in the process. An authorized application must request tokenization, and the sensitive data must be sent to the tokenization server before a token can be generated. Therefore, the immediate step before storing the token is the tokenization server returning the token to the application.

The primary safeguard against licensing risk is ensuring the organization has thecorrect type of license.
Software licenses define usage rights, limitations, and legal obligations. Using software outside of license terms can lead to legal penalties, financial fines, and reputational damage.
Location of licenses is a management issue, not a risk control. Restricting usage to closed-source or open- source alone is not practical, as both models require compliance with license agreements.
Correct licensing includes verifying user counts, subscription terms, geographic restrictions, and intended use.
It also involves monitoring for unauthorized installations and conducting regular audits. Proper license management ensures legal compliance, cost control, and operational continuity.

A Database Activity Monitor (DAM) is specifically designed to identify and stop attack-based commands from executing on a SQL server. Managing Cloud documentation explains that DAM solutions monitor database traffic in real time, inspecting queries and commands for malicious patterns such as SQL injection, privilege escalation, and unauthorized data access attempts.
Unlike traditional firewalls, which primarily filter network traffic, a DAM understands database-specific protocols and SQL command structures. This allows it to detect abnormal or unauthorized queries that may bypass perimeter defenses. When a suspicious command is identified, the DAM can alert administrators, block the execution, or log the activity for forensic analysis.
The other options do not provide this level of database-specific protection. A host-based firewall controls traffic to and from a server but does not analyze SQL commands. A hardware security module focuses on key management and cryptographic operations. A cloud access and security broker enforces security policies between cloud consumers and providers but does not inspect SQL commands directly. Therefore, the database activity monitor is the correct device for stopping attack-based SQL commands.

Moving all services to the cloud provides the highest overall cost savings for organizations implementing BCDR. Managing Cloud guidance explains that cloud-based services reduce capital expenditures, eliminate the need for secondary physical data centers, and leverage on-demand scalability.
Cloud platforms offer built-in redundancy, geographic distribution, and automated recovery capabilities that significantly lower the cost of maintaining separate disaster recovery infrastructure. Pay-as-you-go pricing ensures organizations only pay for resources when needed, further reducing operational expenses.
Hot sites and cross-site replication incur ongoing costs, while tape backups offer lower cost but do not support rapid recovery. Therefore, migrating services to the cloud delivers the most comprehensive cost savings.