Pass the WGU Courses and Certificates Managing-Cloud-Security Questions and answers with ExamsMirror

Thecomputecomponent of a cloud platform encompasses resources used to run workloads, includingcontainers, virtual machines, and storage tied directly to those workloads. Compute services are the foundation of cloud infrastructure, enabling execution of applications and management of data.

Security, monitoring, and networking are supporting components but do not include execution environments. Compute resources scale elastically, allowing organizations to match demand and optimize cost.

By combining containers and storage within compute, cloud platforms allow rapid deployment, portability, and isolation of applications. This component underpins modern architectures like Kubernetes and serverless computing, providing agility and efficiency.

When sharing personal data with a trusted third party, organizations must ensure that the recipient understands and adheres to theorganization’s privacy policy and handling practices. This ensures consistent treatment of personal information across entities and aligns with consent provided by individuals.

Audit results and contractual notices are internal matters, while federal laws define obligations but do not substitute for organizational policies. By explicitly sharing policies and practices, organizations reinforce accountability and ensure compliance with privacy regulations such as GDPR, HIPAA, or CCPA.

This communication sets expectations for data use, retention, and disclosure. It also provides a defensible framework in case of regulatory inquiries, showing that due diligence was performed when transferring data to third parties.

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.

The correct contractual safeguard is anescrow agreement. Data escrow involves storing critical data or software with a neutral third party, which can release it to the customer if the provider fails to meet obligations, such as bankruptcy or service discontinuation.

Indemnification covers liability, offboarding manages termination processes, and encryption secures data but does not ensure availability if the provider disappears.

Escrow provisions protect business continuity by guaranteeing customer access to data regardless of provider viability. They are especially important for organizations handling mission-critical workloads or long-term regulatory obligations in the cloud.

By analyzing natural events that could impact data centers and assessing the risks associated with each, the leadership team isdefining the disaster criteria. This step determines what conditions or events qualify as disasters requiring activation of the recovery plan.

An asset inventory identifies systems, but here the focus is on external events. A disaster declaration process occurs during an actual event, and identifying actions comes later when response strategies are created.

Defining disaster criteria is essential to avoid ambiguity during crises. It establishes thresholds such as “category 4 hurricanes,” “regional power outages exceeding 12 hours,” or “seismic events over a set magnitude.” Clear criteria ensure consistent decision-making and timely activation of recovery procedures.

Apipelinerefers to the structured process of moving code from development to production, encompassing implementation, review, automated testing, and deployment. In DevOps, this is known as a CI/CD pipeline (Continuous Integration/Continuous Deployment).

An iteration refers to a development cycle, a baseline represents a stable reference configuration, and a framework provides structure but not a deployment sequence. Only pipeline accurately captures the sequential, automated flow of code into production.

Pipelines enhance efficiency, consistency, and quality assurance by automating repetitive tasks, reducing human error, and ensuring that code changes are validated before reaching production. They are essential for modern cloud-native applications where rapid deployment is expected.

TheSarbanes-Oxley (SOX) Act of 2002was enacted to restore investor confidence after major corporate accounting scandals. It requires publicly traded corporations to maintain accurate financial reporting and implement internal controls to safeguard the integrity of disclosed information.

GLBA focuses on protecting consumer financial data, GDPR is a European regulation governing privacy, and the CLOUD Act addresses cross-border law enforcement access to data. Only SOX directly mandates financial disclosure and corporate accountability.

SOX compliance includes maintaining audit trails, securing data integrity, and ensuring that executives certify financial statements. Failure to comply carries severe penalties, both civil and criminal. For cloud environments, SOX compliance extends to ensuring IT systems used for financial data are secure, monitored, and auditable.

TheProcess for Attack Simulation and Threat Analysis (PASTA)is a risk-centric threat modeling methodology that explicitly focuses on simulating real-world attacks from an adversary’s perspective. Unlike STRIDE or DREAD, which classify threats and rate severity, PASTA evaluates how an attacker would exploit vulnerabilities step by step.

PASTA has seven stages, including defining objectives, decomposing applications, and simulating attacks. This methodology helps organizations understand both technical and business risks by looking at the application as an attacker would.

STRIDE categorizes threats, DREAD provides scoring, and ATASM emphasizes architecture and mitigation. While valuable, they are not primarily attack-simulation frameworks. PASTA enables proactive testing of defenses against realistic adversary behaviors, making it especially relevant in modern cloud and DevSecOps environments.

The cloud data life cycle defines distinct stages that data goes through from its origin until its disposal. TheCreatephase is the very first stage, and this is where data is generated or captured by systems, applications, or users. At this point, data does not yet have context for storage or use, so it must be appropriately categorized and classified. Activities like labeling, marking, tagging, and assigning metadata are critical because they establish the foundation for enforcing controls throughout the rest of the life cycle.

Classification ensures that data is aligned with sensitivity levels, regulatory requirements, and business value. For example, financial records may be labeled “confidential” while general marketing content may be marked “public.” These distinctions guide how encryption, access controls, and monitoring will be applied in subsequent phases such as storage, sharing, or use.

According to industry frameworks, starting security at theCreatephase ensures that controls “follow the data” across environments. Without proper classification at creation, organizations risk mismanaging sensitive data downstream.

Continuous auditingin the context of Information Rights Management (IRM) allows organizations to monitor access events in real time. It records who accessed a file, when, and how often. This enables organizations to enforce accountability and detect unusual access patterns, which are crucial for both security monitoring and compliance reporting.

Automatic expiration sets a time limit on file availability, while dynamic policy control adjusts permissions based on context (such as location or device). Persistent protection ensures files remain encrypted and controlled wherever they travel. While each feature is valuable, only continuous auditing provides the tracking and visibility into usage required by the scenario.

This approach aligns with governance requirements, providing an audit trail that supports incident response and compliance with data protection regulations. Continuous auditing strengthens both operational security and accountability.