All Managing-Cloud-Security Test Inside WGU Questions

To provide a comprehensive report of system usage, the most important elements are user identifications (IDs) and access timestamps. These data points record who accessed the system, at what time, and for how long. Together, they allow the analyst to determine frequency and duration of use, which is essential for both operational auditing and security oversight.

Other options, such as informational logs or error logs, may provide context but do not directly answer the requirement of identifying users and usage patterns. For instance, 802.1x logs are related to network authentication, while commands or error timestamps reveal activity details but not the overall access history.

Collecting and analyzing IDs and timestamps supports compliance with regulatory frameworks like ISO 27001 and SOC 2, which require clear audit trails. It also provides accountability and supports investigations in case of unauthorized access or misuse. By including these elements, the analyst ensures the report meets internal and external requirements for system monitoring.

Without a clear understanding of infrastructure and software, the leadership team must first conduct an inventory of assets. An asset inventory provides a comprehensive list of hardware, software, and services that support business operations.

Creating checklists, defining criteria, and assigning roles are important, but they rely on knowing what assets exist. Without an inventory, the disaster recovery plan would miss critical dependencies, making recovery incomplete or impossible.

Performing an inventory supports business impact analysis, risk assessments, and recovery prioritization. It ensures that all critical systems are accounted for and appropriate recovery strategies can be designed. Asset inventories are a foundational best practice for disaster recovery and continuity planning.

Data seizure is the risk associated with legal authorities removing or accessing a person’s information stored in a public cloud. Managing Cloud guidance explains that cloud data is subject to the laws and legal processes of the jurisdiction in which it resides.

In some cases, government agencies may compel cloud service providers to disclose or seize data as part of legal investigations. This can occur without the data owner’s direct involvement and may affect confidentiality, privacy, and business operations. Public cloud environments increase this risk because infrastructure is shared and often spans multiple jurisdictions.

Remote wiping is a data destruction technique, vendor lock-in relates to dependency on providers, and data masking protects sensitive data. Therefore, data seizure is the correct risk.

Baselining is the process of establishing a reference point for the standard configuration of systems, networks, or applications. This baseline represents the approved, secure state. By continuously comparing the current environment to the baseline, organizations can detect deviations, unauthorized changes, or misconfigurations.

Patch management involves updating systems, deployment refers to installing new systems, and capacity management focuses on resource planning. While important, these do not establish a standard state for comparison.

Baselining is essential for change management and security auditing. It supports configuration management databases (CMDBs), intrusion detection, and compliance requirements. When deviations are detected, they can be escalated for remediation or formally approved through change control processes.