Authentic WGU Certification Exam Managing-Cloud-Security Questions Answers

NIST SP 800-37 provides a detailed guide for implementing the Risk Management Framework (RMF). Managing Cloud documentation explains that this framework offers a structured process for integrating security and risk management into system development and operational activities.

NIST SP 800-37 outlines steps such as categorizing systems, selecting and implementing security controls, assessing effectiveness, authorizing systems, and continuous monitoring. This lifecycle-based approach helps organizations manage risk in cloud and traditional environments consistently.

ISO 31000 provides general risk management principles, ISO 27001 focuses on information security management systems, and PCI DSS is a compliance standard. Therefore, NIST SP 800-37 is the correct guide for implementing the RMF.

The phase of software design that integrates individual code components and verifies their interoperability is Testing, specifically integration testing. After developers write and unit-test individual modules, those modules must be combined into a complete system. The testing phase ensures that these modules communicate properly, data flows correctly, and overall functionality meets requirements.

Planning establishes project goals, coding builds individual components, and training prepares users. None of these directly verify interoperability. Testing is critical because even well-functioning components may fail when combined, due to interface mismatches, unexpected data structures, or dependency issues.

Cloud-based systems often integrate microservices, APIs, and third-party services. Testing validates that these distributed components interact seamlessly. Proper testing reduces defects, supports reliability, and ensures a consistent end-user experience. It also aligns with DevOps practices, where continuous integration and automated testing pipelines quickly identify and remediate interoperability issues.

Tabletop testing is the disaster recovery testing method with the least impact on production systems. Managing Cloud guidance explains that tabletop exercises are discussion-based scenarios where stakeholders walk through response procedures without executing actual system changes.

This approach allows teams to validate roles, responsibilities, communication paths, and decision-making processes. Tabletop testing is cost-effective, low-risk, and ideal for early validation of disaster recovery and business continuity plans.

Dry runs and full tests involve actual system actions and can impact production. Unit testing focuses on individual components. Therefore, tabletop testing is the correct answer.