A RACI chart is a tool used to clarify the roles and responsibilities in processes, projects, or operations. In the context of cloud compliance, documenting these responsibilities in a RACI chart ensures that all parties within the enterprise are aware of their specific obligations regarding compliance with laws and regulations. This helps in creating a clear, organized view of how each part of the organization contributes to overall compliance, facilitating better coordination and accountability.
Reference = The answer is informed by general best practices in cloud compliance and governance, which recommend the use of RACI charts or similar tools to delineate responsibilities clearly. While I can't reference specific documents from the CCAK or related resources, these practices are widely accepted in the field of cloud security and compliance.

A corrective control is a measure taken to correct or reduce the impact of an error, deviation, or unwanted activity1. Corrective control can be either manual or automated, depending on the type of control used. Corrective control can involve procedures, manuals, systems, patches, quarantines, terminations, reboots, or default dates1. A Business Continuity Plan (BCP) is an example of a corrective control.
Unsuccessful access attempts being automatically logged for investigation is an example of a corrective control because it is a response to a potential security incident that aims to identify and resolve the cause and prevent future occurrences2. Logging and investigating failed login attempts can help detect unauthorized or malicious attempts to access sensitive data or systems and take appropriate actions to mitigate the risk.
The other options are examples of preventive controls, which are designed to prevent problems from occurring in the first place3. Preventive controls can include:
A central antivirus system installing the latest signature files before allowing a connection to the network: This is a preventive control because it prevents malware infection by blocking potentially harmful connections and updating the antivirus software regularly4.
All new employees having standard access rights until their manager approves privileged rights: This is a preventive control because it prevents unauthorized access by enforcing the principle of least privilege and requiring approval for granting higher-level permissions5.
Privileged access to critical information systems requiring a second factor of authentication using a soft token: This is a preventive control because it prevents credential theft or compromise by adding an extra layer of security to verify the identity of the user.
Reference:
What is a corrective control? - Answers1, section on Corrective control Detective controls - SaaS Lens - docs.aws.amazon.com2, section on Unsuccessful login attempts Internal control: how do preventive and detective controls work?3, section on Preventive Controls What Are Security Controls? - F54, section on Preventive Controls The 3 Types of Internal Controls (With Examples) | Layer Blog5, section on Preventive Controls What are the 3 Types of Internal Controls? - RiskOptics - Reciprocity, section on Preventive Controls

The shift-left concept of code release cycles is an approach that moves testing, quality, and performance evaluation early in the development process, often before any code is written. The goal of shift-left testing is to anticipate and resolve software defects, bugs, errors, and vulnerabilities as soon as possible, reducing the cost and time of fixing them later in the production stage. To achieve this, shift-left testing relies on automation tools and techniques that enable continuous integration, continuous delivery, and continuous deployment of code. Automation also facilitates collaboration and feedback among developers, testers, security experts, and other stakeholders throughout the development lifecycle. Therefore, the incorporation of automation to identify and address software code problems early is a sign that an organization has adopted a shift-left concept of code release cycles. Reference:
The 'Shift Left' Is A Growing Theme For Cloud Cybersecurity In 2022
Shift left vs shift right: A DevOps mystery solved
How to shift left with continuous integration

Transparent data encryption (TDE) is used for data and log files at rest. This means that TDE encrypts the database files on the disk and decrypts them when they are read into memory. TDE protects the data from unauthorized access or theft if the physical media, such as drives or backup tapes, are stolen or lost. TDE does not encrypt data across communication channels, data currently being processed, or data in random access memory (RAM). These types of data require different encryption methods, such as SSL/TLS, column encryption, or memory encryption12.
Reference:
Transparent data encryption (TDE) - SQL Server | Microsoft Learn
Transparent Data Encryption - Oracle Help Center