PDF D-DP-FN-01 Study Guide

Configuring the application across multiple availability zones ensures that if one zone experiences a partial outage, whether from a power event, network disruption, or localized infrastructure failure, the application instances running in the unaffected zones continue serving traffic without interruption, directly satisfying the requirement to keep operating through a partial system outage. This is an infrastructure-level resiliency design principle specifically intended to isolate the blast radius of a localized failure so it does not become a total outage. Stateless design (B) is a valuable complementary principle that makes it easier for any given instance to handle any request without depending on local session state, which supports scaling and failover, but on its own it does not guarantee continued operation during an outage unless it is paired with redundant infrastructure across which requests can be redirected. Microservices architecture (C) improves modularity and independent deployability of application components, and can support resilience patterns, but adopting microservices alone does not inherently provide the redundancy needed to survive a partial outage; a microservices application still running entirely within a single zone remains vulnerable. Synchronous replication (D) protects data consistency between sites but is a data protection mechanism, not an application availability design principle. Multiple availability zones is the correct, direct answer.

Reference topic: Fault Tolerance Techniques - Multi-Zone Application Resiliency.

Data availability is fundamentally expressed as a ratio: the amount of time a system was actually operational and accessible (uptime) relative to the total time it was expected to be operational, which by extension requires accurately capturing the amount of time it was not operational (downtime). Monitoring uptime (A) provides the direct measurement of how long systems were successfully available and functioning, forming one half of the availability equation. Calculating total downtime (B) provides the complementary measurement, capturing every period the system was unavailable, whether due to failure, maintenance, or other disruption, which is subtracted from total elapsed time to compute the availability percentage. Together, uptime and downtime are the two foundational, directly measurable inputs from which any meaningful availability metric (such as the standard formula of uptime divided by total time) is derived, making this pairing the correct answer. Excluding the time during backup restore (C) would artificially distort the availability calculation by omitting a period during which systems were arguably unavailable to normal use, undermining the accuracy of the measurement rather than contributing a valid, standard method for calculating availability. Calculating the mean time to report an incident (D) measures how quickly an issue is identified and communicated, a useful operational responsiveness metric, but it measures detection speed, not the actual proportion of time a system was available, making it unrelated to the availability calculation itself. Uptime and downtime are correct.

Reference topic: Managing the Data Protection Environment - Measuring Data Availability.

Deduplication identifies redundant data segments, whether identical files or identical sub-file blocks, across a dataset or over successive backup generations, and stores only a single physical instance of each unique segment while replacing all subsequent duplicate occurrences with lightweight pointers or references to that stored instance. This directly and substantially reduces the amount of physical storage capacity required to retain the same logical volume of data, which is the fundamental, primary purpose deduplication was designed to serve, particularly valuable in backup environments where the same or highly similar data is repeatedly captured across daily, weekly, and monthly backup cycles. Increased backup speed (A) can be a secondary, situational benefit in some architectures (particularly source-based deduplication, which reduces the volume of data that must be transmitted), but it is not deduplication's defining, primary purpose, and is not guaranteed in every implementation, since deduplication also introduces processing overhead. Simplifying backup configuration (B) is not an inherent function of deduplication technology at all; configuration complexity is unrelated to whether redundant data segments are being eliminated. Enhancing security (D) is unrelated to deduplication's function, which addresses storage efficiency, not confidentiality, integrity, or access control. Reducing storage requirements is correct.

Reference topic: Data Backup and Deduplication - Purpose and Benefits of Deduplication.

Image-based backup captures a complete, consistent snapshot of an entire virtual machine, its operating system, configuration, installed applications, and data, as a single unit at the hypervisor level, typically without requiring an agent inside the guest OS. This makes it uniquely suited to restoring an entire VM quickly and reliably, since the whole machine state, not just individual files, is preserved and can be powered back on essentially as it existed at capture time, which is invaluable for full disaster recovery or bare-metal-style VM restoration. Restoring individual files (A) is technically possible from an image, usually via file-level recovery tools that mount the image, but it is not the use case the technology is uniquely optimized for; dedicated file-level backup handles that more efficiently. Backing up application data only (B) understates the scope of image-based backup, which captures the full machine rather than isolating application data alone, and is arguably better served by application-aware agent-based backup for granular, consistent application recovery. Incremental backups (C) describe a backup frequency and data-capture method that can be applied to image-based backups but is not itself the unique use case image-based backup solves. Full VM restoration is the defining strength.

Reference topic: Data Backup and Deduplication - Image-Based (Virtual Machine) Backup.