Free WGU Managing Cloud Security Managing-Cloud-Security Exam Questions

Reporting the work on the news is considered legal fair use of a copyrighted item. Managing Cloud guidance explains that fair use allows limited use of copyrighted material without permission when the purpose is commentary, criticism, education, or news reporting.

In news reporting, copyrighted material may be referenced or partially reproduced to inform the public, provided it does not replace the original work or cause financial harm to the copyright owner. This principle supports transparency and public awareness while balancing intellectual property rights.

The other activities typically require authorization from the copyright holder. Performing a work publicly, exporting it, or broadcasting it generally involves distribution or commercial use, which falls outside fair use protections. Therefore, reporting the work in the news is the correct example of legal fair use.

The primary safeguard against licensing risk is ensuring the organization has the correct type of license. Software licenses define usage rights, limitations, and legal obligations. Using software outside of license terms can lead to legal penalties, financial fines, and reputational damage.

Location of licenses is a management issue, not a risk control. Restricting usage to closed-source or open-source alone is not practical, as both models require compliance with license agreements.

Correct licensing includes verifying user counts, subscription terms, geographic restrictions, and intended use. It also involves monitoring for unauthorized installations and conducting regular audits. Proper license management ensures legal compliance, cost control, and operational continuity.

A Web Application Firewall (WAF) allows customers to redirect traffic as part of securing cloud-hosted applications. Managing Cloud principles explain that WAFs operate at the application layer and can inspect, filter, allow, block, or redirect HTTP and HTTPS traffic based on defined security rules.

Traffic redirection is commonly used to route suspicious or malicious requests away from protected applications, forward traffic to alternate services, or enforce secure communication paths. WAFs can also integrate with load balancers and content delivery networks to manage traffic flow efficiently while protecting applications from attacks such as SQL injection, cross-site scripting, and denial-of-service attempts.

The other options do not provide traffic redirection. SIEM systems aggregate and analyze logs, intrusion detection and prevention systems focus on detection and blocking, and cryptographic key management handles encryption keys. Therefore, a web application firewall is the correct answer.

Securing the hypervisor is the primary security measure that controls virtualization in the cloud. Managing Cloud principles explain that the hypervisor is the foundational component that enables multiple virtual machines to share the same physical hardware.

If the hypervisor is compromised, all hosted workloads are at risk. Therefore, securing the hypervisor through hardening, access control, patching, and monitoring is critical to maintaining isolation between virtual machines and preventing privilege escalation.

Monitoring and logging provide visibility, dedicated hosting reduces shared risk, and managing image assets supports consistency, but none directly control virtualization. Therefore, securing the hypervisor is the correct answer.

The software agent management plane must support auto-scaling and elasticity because traditional security tools are not designed for the speed and scale of cloud environments. Managing Cloud guidance explains that cloud workloads can be created, scaled, and terminated rapidly, often within minutes or seconds.

If security management systems cannot scale at the same pace, workloads may operate without protection or monitoring. Elastic security management ensures that agents are deployed, configured, and decommissioned automatically as workloads scale up or down.

The other options do not directly explain the need for elasticity. Network isolation, reduced services, and firewall port usage are not the primary drivers. Therefore, the need to match cloud velocity makes option C correct.

The General Data Protection Regulation (GDPR) is the legal framework concerned with the privacy of data belonging to citizens of the European Union and the European Economic Area (EU/EEA). Managing Cloud principles explain that GDPR establishes comprehensive rules governing the collection, processing, storage, and transfer of personal data.

GDPR applies to organizations both within and outside the EU/EEA if they process personal data of EU residents. It enforces strict requirements related to data protection, consent, breach notification, and individual rights. Cloud service providers and consumers must ensure compliance when handling EU personal data.

The other options apply to different jurisdictions or data types. HIPAA governs healthcare data in the United States, COPPA protects children's online privacy in the U.S., and APPI applies to Japan. Therefore, GDPR is the correct framework.

Patch management is a core process implemented during the hardening of an operating system and its workloads. Managing Cloud principles explain that OS hardening involves reducing vulnerabilities by applying security patches, updates, and fixes to eliminate known weaknesses.

Patch management ensures that operating systems, applications, and dependencies are kept up to date with vendor-released security patches. This process reduces the attack surface and prevents exploitation of known vulnerabilities. Effective patch management includes testing, deployment, verification, and ongoing monitoring.

Change management governs how changes are approved, incident management handles security events, and security management is a broader governance function. Therefore, patch management is the correct process associated with OS hardening.

A cloud service customer is the role that subscribes to a software as a service (SaaS) application. Managing Cloud principles define the cloud service customer as the individual or organization that consumes cloud services provided by a cloud service provider.

In a SaaS model, the customer accesses applications through a subscription-based arrangement, typically via a web interface. The customer does not manage the underlying infrastructure or platform but is responsible for configuring user access and ensuring proper use of the service.

The cloud service provider delivers and manages the application, while ''cloud computing'' and ''cloud application'' are not roles. Therefore, the cloud service customer is the correct role.

The capability to rapidly create and destroy virtual systems as demand fluctuates is known as ephemeral computing. These short-lived resources are provisioned automatically when needed and decommissioned when demand subsides.

Resource scheduling helps allocate resources but does not imply temporary lifespans. High availability ensures continuous service, and maintenance mode is used for administrative tasks.

Ephemeral computing is central to elasticity in cloud environments, reducing costs and improving scalability. For example, containers or serverless functions may run only while needed and then disappear. This model optimizes utilization, lowers expenses, and supports modern application architectures that demand agility.

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.

By analyzing natural events that could impact data centers and assessing the risks associated with each, the leadership team is defining 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.

The requirement for a username, password, and security token describes authentication---the process of verifying the identity of a user. By requiring multiple factors (something you know + something you have), the organization is implementing multifactor authentication (MFA).

Authorization defines what resources a user can access after authentication. WAFs protect web applications, and ACLs specify rules for allowed or denied traffic, but neither validate user identity.

Authentication ensures that only legitimate users gain access to cloud resources. In hybrid environments, MFA is a strong safeguard against credential theft and phishing attacks, providing assurance that identities are genuine before authorization decisions are made.

A Type 1 hypervisor provides the most secure foundation and smallest attack footprint for virtual servers. Managing Cloud documentation explains that Type 1 hypervisors run directly on the host hardware without an underlying operating system.

By eliminating the host OS layer, Type 1 hypervisors reduce attack surface and improve isolation between virtual machines. This architecture enhances performance, stability, and security, making it the preferred choice for enterprise and cloud environments.

Type 2 hypervisors run on top of a host operating system, increasing complexity and vulnerability exposure. Application isolation and virtualization do not provide the same foundational security. Therefore, a Type 1 hypervisor is the correct choice.

The correct answer is electronic discovery (e-discovery). This process involves identifying, collecting, and producing electronically stored information (ESI) that may serve as evidence in legal proceedings. E-discovery ensures that relevant data such as emails, logs, or documents is preserved and made available in a legally defensible manner.

Chain of custody refers to documenting the handling of evidence once collected, while forensic imaging creates exact copies of digital media. Gap analysis identifies weaknesses in processes but is unrelated to evidence collection.

E-discovery is essential in both corporate and cloud contexts, as data is often distributed across multiple environments. Cloud providers may assist customers with e-discovery by providing tools for searching, tagging, and exporting relevant data. A sound e-discovery process ensures compliance with legal obligations and prevents spoliation of evidence.

The correct approach for sanitizing a USB thumb drive while preserving its usability is overwriting. Overwriting involves replacing the existing data on the device with random data or specific patterns to ensure that the original information cannot be recovered. This process leaves the physical device intact, allowing it to be reused securely.

Physical destruction, such as shredding, renders the device unusable. Degaussing only works on magnetic media like hard disks or tapes, not on solid-state or flash-based USB drives. Key revocation applies to cryptographic keys and not to physical devices.

By using overwriting, organizations comply with data sanitization standards while balancing operational efficiency. Many tools exist that perform multi-pass overwrites to meet regulatory requirements such as those from NIST or ISO. This ensures that sensitive data is removed while allowing the device to remain in circulation for continued use.