D-DP-FN-01 Leak Questions

Governance, Risk, and Compliance is the integrated organizational discipline specifically structured to plan and implement security and operational controls in a way that reliably achieves business objectives (governance), while systematically identifying and addressing risk (risk management), and simultaneously ensuring adherence to both internally defined policy and externally mandated regulatory requirements (compliance). This combination directly and comprehensively matches the question's requirement, planning and implementing controls while ensuring compliance with both internal and external policies, making GRC the correct, purpose-built process framework for this need. The Secure Product Life Cycle (A) is a development-focused methodology concerned with embedding security practices throughout the stages of designing, building, and releasing a product or software, a narrower, engineering-oriented process rather than the organization-wide governance and compliance planning framework the question describes. GDPR (C) is a specific piece of European Union legislation governing the protection of personal data; it is one example of an external regulatory requirement an organization might need to comply with, but it is a regulation itself, not a general process framework for planning and implementing controls across both internal and external policy domains broadly. LSASS (D) is a Windows operating system component responsible for enforcing local security policy and handling authentication, a specific technical subsystem rather than an organizational planning process. GRC is correct.

Reference topic: Securing the Data Protection Environment - Governance, Risk, and Compliance (GRC) Processes.

Alerting is the management function responsible for actively notifying administrators about events occurring within the data protection environment, ranging from informational status changes to warnings about degrading conditions to fatal notifications about component failures, essentially providing timely, proactive communication about both current events and emerging or impending threats to protection services. This notification role is what distinguishes alerting as a discrete management capability, separate from the underlying data-gathering activities that feed it. Tracking unauthorized access and configuration changes (A) more specifically describes auditing or security monitoring functions, which may generate alerts as an output but is itself a narrower, security-focused activity rather than the general definition of alerting. Analyzing the efficiency of protection components and services (B) describes performance analysis or reporting, a related but distinct management function concerned with evaluating how well components are performing over time, rather than issuing real-time notifications. An availability status check (C) describes monitoring, the continuous or periodic process of assessing whether components are up, healthy, or degraded, which supplies the raw status information that the alerting function then translates into actionable notifications, but monitoring and alerting remain separate functions within the standard data protection management model. Notification of events and threats correctly defines alerting.

Reference topic: Managing the Data Protection Environment - Monitoring, Alerting, and Reporting Functions.

Primary storage performance degrades as more capacity is consumed and as I/O contention increases across a growing, heterogeneous mix of active and inactive data. Archiving relocates infrequently accessed, fixed data out of expensive, high-performance primary storage onto separate archive media, which reduces the working set that primary storage must index, scan, and serve, freeing I/O bandwidth and capacity for genuinely active workloads. This is the standard tiered-storage remedy for the described symptom and does not require destroying or permanently losing any data, since archived content remains retrievable when needed. Configuring alerts (A) provides visibility into the utilization problem but does not resolve it; it is a monitoring, not a remediation, action. A single-tier system with archiving 'enabled' (C) is an internally inconsistent option, since true archiving requires separating data onto a distinct tier or storage class rather than keeping everything on one undifferentiated tier. Deleting old files (D) may free space but is destructive, risks permanent data loss, and ignores retention or compliance obligations that archiving is specifically designed to satisfy while still relieving primary storage load. Moving data to archive storage is therefore the correct, non-destructive fix.

Reference topic: Replication and Data Archiving - Storage Tiering and Archiving for Performance.