Which control objective ensures that modules cannot destroy or corrupt one another?

The control objective that ensures modules cannot destroy or corrupt one another is referred to as modular integrity. This concept focuses on maintaining the integrity of individual program modules within a software environment. It ensures that each module can operate independently without impacting the functionality or performance of other modules. This is crucial in systems design, as dependencies and interactions between modules can potentially lead to data corruption or operational failures if not properly managed.

By implementing measures that uphold modular integrity, organizations can prevent one module from inadvertently affecting another, thereby safeguarding overall system reliability and performance. This aspect is particularly important in accounting information systems, which rely on accurate and consistent data processing.

In contrast, data redundancy involves storing the same data in multiple locations, which can increase the risk of data inconsistency. System isolation refers to separating different systems to prevent interference but doesn't specifically address the integrity of modules. Access control is more concerned with who can access certain data or functionalities, rather than ensuring the integrity of modules themselves.