A dry run disaster recovery plan test requires broad organizational participation in a simulated disaster scenario without executing all production-impacting tasks. Managing Cloud principles explain that dry run testing validates coordination, communication, and procedural readiness while avoiding the risks of full operational disruption.
In a dry run, teams follow documented recovery steps conceptually or in limited execution, verifying that dependencies, responsibilities, and sequencing are correct. This approach provides higher fidelity than tabletop exercises, which are discussion-based, while avoiding the operational risks of full or parallel tests.
Parallel tests involve running recovery systems alongside production, and full tests execute all recovery actions, often causing service disruption. Therefore, a dry run offers a balanced method to test preparedness across the organization without full execution.

A Web Application Firewall (WAF) includes anti-distributed denial of service (DDoS) capabilities designed to protect cloud-hosted applications and underlying data storage from availability-based attacks. Managing Cloud principles state that WAFs sit in front of web applications and analyze incoming traffic to identify and block malicious requests, including high-volume attack patterns characteristic of DDoS attacks.
By filtering traffic at the application layer, a WAF prevents excessive or malicious requests from overwhelming backend services such as cloud storage systems and databases. Many WAF solutions implement rate limiting, traffic profiling, and behavioral analysis to distinguish legitimate users from attackers, ensuring continued access to cloud resources.
The other options do not provide DDoS protection. An XML gateway focuses on validating and securing XML-based messages. NDAM and ADAM solutions monitor database activity but do not mitigate network- level or application-layer flood attacks. Therefore, the Web Application Firewall is the correct security device for providing anti-DDoS protection in cloud environments.

The scenario arises because ofmultitenancy, a core cloud characteristic where multiple customers share the same physical infrastructure. If a storage device containing multiple tenants' data is seized as part of a case involving another customer, unrelated organizations may still be affected.
Virtualization enables resource abstraction, but multitenancy specifically introduces shared infrastructure risks. SaaS and PaaS are service models, not architectural characteristics.
Multitenancy offers efficiency and cost benefits but raises challenges for data sovereignty, legal jurisdiction, and evidentiary control. Providers mitigate these risks through encryption, logical isolation, and contractual terms. Customers must understand these implications when handling regulated or sensitive data in cloud environments.

A loss of policy control is a key risk when using a community cloud compared to a private cloud. Managing Cloud principles explain that community clouds are shared by multiple organizations with common objectives, compliance needs, or industry requirements.
Because governance is shared across participants, individual organizations may have reduced ability to enforce customized security policies, configurations, or controls. Policy decisions often require consensus, which can limit flexibility and slow response to emerging risks.
Private clouds provide full control over governance, security policies, and configurations. The other options are not inherent risks of community cloud models. Therefore, loss of policy control is the correct answer.

ISO/IEC 27050-1:2016 is the guide that addresses the international challenges of cloud forensics and is recognized as the premier standard for electronic discovery (eDiscovery). Managing Cloud documentation explains that eDiscovery involves identifying, collecting, preserving, and producing electronically stored information in legal proceedings.
This standard provides guidance for handling digital evidence across jurisdictions, which is especially important in cloud environments where data may reside in multiple countries. It establishes consistent processes and terminology to support legal defensibility and compliance.
The other ISO standards address evidence handling, investigation readiness, or incident management, but ISO
/IEC 27050 specifically focuses on eDiscovery. Therefore, ISO/IEC 27050-1:2016 is the correct answer.