Free WGU Managing-Cloud-Security Practice Exam with Questions & Answers | Set: 2

Arollbackis the safeguard that restores a system to its previous, stable state when a new code release introduces issues. In DevOps workflows, rollbacks provide a rapid recovery mechanism, reducing downtime and minimizing customer impact.

Staging, code review, and testing are preventive controls that reduce the likelihood of defects reaching production, but once a bug has already been deployed, rollback is the corrective control.

Rollback strategies often rely on version control systems, container orchestration, or infrastructure-as-code automation to quickly revert to earlier configurations. This practice is essential for maintaining reliability and availability, especially in cloud environments with continuous deployment pipelines.

TheChange Management Board (CMB), also called the Change Advisory Board (CAB), is the formal authority responsible for reviewing, assessing, and approving planned modifications to IT environments. This group ensures that proposed changes align with business objectives, do not introduce unnecessary risks, and comply with security and regulatory requirements.

Event management teams focus on monitoring events, problem management teams handle root-cause analysis, and executive boards provide strategic direction but are not operational approval authorities. Only the CMB has the explicit role of validating technical and security implications before implementation.

By involving the CMB, organizations enforce structured governance, minimize disruptions, and establish accountability. This practice is central in ITIL and ISO/IEC 20000 standards, ensuring that operational integrity and security are preserved during change cycles.

The categories mentioned—relational, nonrelational, key-value, and document-oriented—refer to different types of databases. Relational databases (SQL) organize data into tables with rows and columns, nonrelational databases (NoSQL) provide flexibility for unstructured data, key-value stores map identifiers to values, and document-oriented databases manage data in formats such as JSON or BSON.

Object-based storage and volumes are alternative storage architectures but are not described by these categories. XML is a data format, not a storage type.

In the cloud, database services are offered as managed solutions, reducing the administrative burden on organizations. Properly managing database storage is critical for data governance, confidentiality, and compliance. Databases are also central to security strategies, where access control, encryption, and auditing are applied.

Thus, the correct answer is database storage, which encompasses multiple architectures that address different performance, scalability, and data management needs.

Trust in digital certificates comes from their issuance by aCertificate Authority (CA). A CA is a trusted entity that validates identities and signs certificates. In internal environments, organizations often operate aprivate CAto issue certificates for users, systems, and services.

If certificates were generated by individual private keys or systems without central authority, there would be no unified trust chain, and validating authenticity across the organization would be impossible. A certificate repository server only distributes certificates but cannot establish trust.

By using an organizational CA server, all certificates are linked to a root of trust. Systems configured to trust the organization’s CA will trust any certificate it issues. This allows secure internal communications (TLS, VPN, email signing) and ensures scalability as new services come online. It also supports compliance with enterprise PKI policies.

Theprocurementfunction is directly responsible for vendor selection and contract management, including risk assessments of new or renewed vendor relationships. This ensures that third-party providers meet security, compliance, and performance requirements.

Software development and quality assurance focus on product creation and validation. Marketing manages branding and outreach. None of these directly involve evaluating external vendor risk.

Procurement integrates due diligence, contract clauses, and performance monitoring into enterprise risk management. This reduces exposure to third-party threats and ensures compliance with frameworks such as ISO 27036 (supplier relationships) and NIST vendor risk management guidelines.

ASecurity Operations Center (SOC)is a centralized facility that allows administrators to monitor, detect, investigate, and respond to cybersecurity events in real time. SOC teams leverage tools such as SIEM (Security Information and Event Management), threat intelligence, and incident response playbooks.

ERTs and DRTs are teams focused on emergencies and disaster recovery, respectively, but they do not provide continuous monitoring. A NOC focuses on performance and availability of IT infrastructure but not on security threats.

By establishing a SOC, organizations ensure 24/7 visibility into security events, coordinated incident handling, and compliance with standards such as ISO 27001 and SOC 2. SOCs are essential in cloud environments where threats evolve rapidly, and centralized expertise is needed to minimize impact.

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.

In cloud environments, the provider’s role in thechain of custodyprimarily involvescollecting and preserving digital evidencewhen incidents or investigations occur. Because providers manage the infrastructure, they have direct access to logs, storage systems, and virtual machines necessary for evidence collection.

Backup policies and incident response may involve collaboration, but they remain customer responsibilities in many service models. Data classification and analysis are business-driven tasks, which customers must handle.

Providers must ensure that evidence collection is forensically sound and documented properly to maintain legal admissibility. This responsibility is critical in maintaining trust and ensuring compliance with laws and contractual obligations. It reinforces the shared responsibility model by clearly defining which aspects of digital forensics belong to the provider.

Continuous monitoring is the control that allows organizations to actively verify that a cloud provider is fulfilling contractual and compliance obligations. This involves automated collection and analysis of operational, security, and performance data. It enables organizations to ensure that service-level agreements (SLAs) are being honored and that compliance requirements are being met in real time.

While regulatory oversight is provided by external authorities and incident management is reactive in nature, continuous monitoring is a proactive approach. It allows customers to maintain visibility into provider operations. Confidential computing focuses on data protection but does not verify contract adherence.

By employing continuous monitoring, organizations establish transparency and accountability. It also supports audit processes by providing evidence that controls remain effective over time. This reduces risk associated with outsourcing critical functions to a cloud provider and ensures resilience against potential provider-side failures.

The unplanned event described is adisruptionof service. In IT service management frameworks like ITIL, disruptions occur when an incident prevents normal service delivery. The goal of incident management is to restore service quickly and minimize impact on customers.

A bug refers to a software defect, which may cause disruptions but is not synonymous with the event itself. An error represents a fault, while change refers to deliberate modifications. Only disruption captures the unplanned nature of service unavailability.

Recognizing incidents as disruptions helps organizations apply structured processes such as escalation, root-cause analysis, and communication. It ensures resilience in cloud-based environments where uptime is a key performance indicator and customer trust is closely tied to availability.