Evaluating the use of virtualization addresses a logical design consideration. Managing Cloud documentation explains that logical design focuses on system architecture, virtualization layers, network segmentation, and service delivery models.
Virtualization determines how workloads are abstracted from physical hardware, how resources are shared, and how isolation is enforced between workloads. Decisions related to hypervisors, virtual machines, containers, and orchestration platforms fall under logical architecture rather than physical layout or environmental controls.
Regulatory considerations involve compliance requirements, environmental considerations include power and cooling, and physical considerations address space and hardware placement. Therefore, virtualization is a logical design consideration.

Examining configuration data is the appropriate methodology to determine whether other similar instances were potentially exposed during the same attack. Managing Cloud principles explain that configuration analysis identifies shared settings, permissions, or misconfigurations across cloud resources.
By reviewing configuration data, security teams can identify patterns such as overly permissive access controls, shared credentials, or insecure templates that may affect multiple instances. This helps assess blast radius and identify additional affected systems.
Application logs and network flows help investigate specific events, while generalized log review focuses on activity. Configuration analysis uniquely identifies systemic exposure. Therefore, examining configuration data is the correct answer.

Offsite backups are an effective countermeasure against vendor lock-in and lock-out risks. Managing Cloud principles explain that maintaining copies of data outside a single cloud provider reduces dependency and ensures continued access if services become unavailable.
Offsite backups enable organizations to migrate data, recover from provider outages, or exit a provider relationship without losing critical information. This control supports business continuity, portability, and resilience.
Video surveillance addresses physical security, disk redundancy improves availability within the same provider, and training programs improve awareness but do not reduce dependency. Therefore, offsite backups are the correct security control.

Failover should occur prior to the crisis event when an impending disaster is identified. Managing Cloud principles explain that proactive failover allows organizations to maintain service continuity by transitioning operations to alternate systems before disruption occurs.
Early failover reduces downtime, minimizes data loss, and avoids the risks associated with reactive responses during an active crisis. Cloud environments support automated or planned failover mechanisms that can be triggered by warning systems, ensuring seamless continuity.
Failover during or after the crisis increases the likelihood of service interruption. Therefore, initiating failover before the event is the correct approach.

The Stored Communications Act (SCA) is a United States jurisdictional data protection law enacted to limit and regulate forced disclosure of electronic communications by internet service providers. Managing Cloud principles describe the SCA as a legal framework that governs how stored electronic communications and customer data may be accessed by government entities.
The act establishes requirements for warrants, subpoenas, and court orders before service providers can disclose stored data. This protection is particularly relevant in cloud environments, where service providers store large volumes of customer data on behalf of organizations.
The other options are incorrect. APP8 and APP11.1 are Australian Privacy Principles, and GDPR applies to the European Union. Therefore, the Stored Communications Act is the correct U.S. jurisdictional protection.