Question 190
During a regulated services maintenance window, the integrator finds that a department requests a single shared folder tree with per-team permissions and ordinary desktop file operations. The team must make a decision specific to this observed storage behavior, not an unrelated platform change. Which corrective or deployment decision most directly addresses the demonstrated requirement or fault?
- Choose a supported management architecture consistent with isolation and lifecycle needs.
- Specify a supported file service and directory-permission model for the requirement.
- Select supported encrypted storage and least-privilege operations with recoverable key management.
- Select a supported low-latency block solution sized to the measured workload envelope.
Explanation
Correct Answer
B:Specify a supported file service and directory-permission model for the requirement. This response addresses the technical dependency: user collaboration through shared folders is a file-service requirement rather than independent raw LUN presentation. Acceptance should establish that a pilot client can browse the expected hierarchy and access only permitted folders.
Incorrect Answers
A:Choose a supported management architecture consistent with isolation and lifecycle needs. This approach addresses a different storage condition: a regulated environment has restricted outbound connectivity and requires local service while considering centralized cloud management. Here, the differentiating evidence is that a pilot client can browse the expected hierarchy and access only permitted folders. It is not the most direct answer because user collaboration through shared folders is a file-service requirement rather than independent raw LUN presentation.
C:Select supported encrypted storage and least-privilege operations with recoverable key management. This approach addresses a different storage condition: a healthcare application needs encrypted stored records and access separation, not simply a faster drive tier. Here, the differentiating evidence is that a pilot client can browse the expected hierarchy and access only permitted folders. It is not the most direct answer because user collaboration through shared folders is a file-service requirement rather than independent raw LUN presentation.
D:Select a supported low-latency block solution sized to the measured workload envelope. This approach addresses a different storage condition: a customer proposes a capacity-optimized file archive for a transactional database that needs consistently low block-I/O latency. Here, the differentiating evidence is that a pilot client can browse the expected hierarchy and access only permitted folders. It is not the most direct answer because user collaboration through shared folders is a file-service requirement rather than independent raw LUN presentation.
Question 191
During a laboratory virtualization cutover, the integrator finds that a department requests a single shared folder tree with per-team permissions and ordinary desktop file operations. The team must make a decision specific to this observed storage behavior, not an unrelated platform change. Which repeatable operating practice best reduces recurrence or avoids the same design error?
- Audit service dependencies and offline recovery procedures before deployment.
- Test encrypted data recovery and administrator separation before go-live.
- Capture client compatibility and ACL acceptance tests before purchase.
- Test retrieval costs, immutability behavior and retention before adoption.
Explanation
Correct Answer
C:Capture client compatibility and ACL acceptance tests before purchase. This safeguard targets the known exposure before another incident. Operations should confirm that a pilot client can browse the expected hierarchy and access only permitted folders.
Incorrect Answers
A:Audit service dependencies and offline recovery procedures before deployment. This approach addresses a different storage condition: a regulated environment has restricted outbound connectivity and requires local service while considering centralized cloud management. Here, the differentiating evidence is that a pilot client can browse the expected hierarchy and access only permitted folders. It is not the most direct answer because user collaboration through shared folders is a file-service requirement rather than independent raw LUN presentation.
B:Test encrypted data recovery and administrator separation before go-live. This approach addresses a different storage condition: a healthcare application needs encrypted stored records and access separation, not simply a faster drive tier. Here, the differentiating evidence is that a pilot client can browse the expected hierarchy and access only permitted folders. It is not the most direct answer because user collaboration through shared folders is a file-service requirement rather than independent raw LUN presentation.
D:Test retrieval costs, immutability behavior and retention before adoption. This approach addresses a different storage condition: a media archive requires metadata-driven retrieval of large objects and automatic retention policies, not mutable shared-disk access. Here, the differentiating evidence is that a pilot client can browse the expected hierarchy and access only permitted folders. It is not the most direct answer because user collaboration through shared folders is a file-service requirement rather than independent raw LUN presentation.
Question 192
During a financial-services workload review, the integrator finds that a department requests a single shared folder tree with per-team permissions and ordinary desktop file operations. The team must make a decision specific to this observed storage behavior, not an unrelated platform change. Which risk assessment most accurately describes the effect of leaving this specific dependency unresolved?
- Deferring correction can leave the observed condition unresolved: a healthcare application needs encrypted stored records and access separation, not simply a faster drive tier. The underlying constraint remains that data confidentiality depends on supported encryption and restricted access, not capacity or spindle count.
- Deferring correction can leave the observed condition unresolved: a customer demands virtually no acknowledged-write loss across two data centers and a vendor proposes periodic asynchronous copies without a caveat. The underlying constraint remains that periodic asynchronous replication may leave a recoverable gap after sudden failure, unlike correctly implemented synchronous acknowledgement.
- Deferring correction can leave the observed condition unresolved: a hospital only has local snapshots but requires restoration at a separate location after complete array failure. The underlying constraint remains that local snapshots alone share the source-array failure domain and do not constitute independently accessible backups.
- Deferring correction can leave the observed condition unresolved: a department requests a single shared folder tree with per-team permissions and ordinary desktop file operations. The underlying constraint remains that user collaboration through shared folders is a file-service requirement rather than independent raw LUN presentation.
Explanation
Correct Answer
D:Deferring correction can leave the observed condition unresolved: a department requests a single shared folder tree with per-team permissions and ordinary desktop file operations. The underlying constraint remains that user collaboration through shared folders is a file-service requirement rather than independent raw LUN presentation. The continued impact follows the identified mechanism: user collaboration through shared folders is a file-service requirement rather than independent raw LUN presentation.
Incorrect Answers
A:Deferring correction can leave the observed condition unresolved: a healthcare application needs encrypted stored records and access separation, not simply a faster drive tier. The underlying constraint remains that data confidentiality depends on supported encryption and restricted access, not capacity or spindle count. This approach addresses a different storage condition: a healthcare application needs encrypted stored records and access separation, not simply a faster drive tier. Here, the differentiating evidence is that a pilot client can browse the expected hierarchy and access only permitted folders. It is not the most direct answer because user collaboration through shared folders is a file-service requirement rather than independent raw LUN presentation.
B:Deferring correction can leave the observed condition unresolved: a customer demands virtually no acknowledged-write loss across two data centers and a vendor proposes periodic asynchronous copies without a caveat. The underlying constraint remains that periodic asynchronous replication may leave a recoverable gap after sudden failure, unlike correctly implemented synchronous acknowledgement. This approach addresses a different storage condition: a customer demands virtually no acknowledged-write loss across two data centers and a vendor proposes periodic asynchronous copies without a caveat. Here, the differentiating evidence is that a pilot client can browse the expected hierarchy and access only permitted folders. It is not the most direct answer because user collaboration through shared folders is a file-service requirement rather than independent raw LUN presentation.
C:Deferring correction can leave the observed condition unresolved: a hospital only has local snapshots but requires restoration at a separate location after complete array failure. The underlying constraint remains that local snapshots alone share the source-array failure domain and do not constitute independently accessible backups. This approach addresses a different storage condition: a hospital only has local snapshots but requires restoration at a separate location after complete array failure. Here, the differentiating evidence is that a pilot client can browse the expected hierarchy and access only permitted folders. It is not the most direct answer because user collaboration through shared folders is a file-service requirement rather than independent raw LUN presentation.
Question 193
During a private-cloud commissioning project, the integrator finds that a media archive requires metadata-driven retrieval of large objects and automatic retention policies, not mutable shared-disk access. The team must make a decision specific to this observed storage behavior, not an unrelated platform change. Which targeted initial diagnostic best isolates the technical issue before altering production configuration?
- Confirm the application uses supported object API operations and retention metadata.
- Document data-at-rest encryption, key custody, role separation and backup requirements.
- Measure expected IOPS, 95th percentile latency and host access protocol before selecting a platform.
- Confirm SMB or NFS compatibility, file namespace and identity requirements.
Explanation
Correct Answer
A:Confirm the application uses supported object API operations and retention metadata. This verification tests the suspected mechanism: object storage is a suitable abstraction for large unstructured objects addressed by identifiers and metadata. The confirming result is that the application retrieves a sample object by identifier after lifecycle policy processing.
Incorrect Answers
B:Document data-at-rest encryption, key custody, role separation and backup requirements. This approach addresses a different storage condition: a healthcare application needs encrypted stored records and access separation, not simply a faster drive tier. Here, the differentiating evidence is that the application retrieves a sample object by identifier after lifecycle policy processing. It is not the most direct answer because object storage is a suitable abstraction for large unstructured objects addressed by identifiers and metadata.
C:Measure expected IOPS, 95th percentile latency and host access protocol before selecting a platform. This approach addresses a different storage condition: a customer proposes a capacity-optimized file archive for a transactional database that needs consistently low block-I/O latency. Here, the differentiating evidence is that the application retrieves a sample object by identifier after lifecycle policy processing. It is not the most direct answer because object storage is a suitable abstraction for large unstructured objects addressed by identifiers and metadata.
D:Confirm SMB or NFS compatibility, file namespace and identity requirements. This approach addresses a different storage condition: a department requests a single shared folder tree with per-team permissions and ordinary desktop file operations. Here, the differentiating evidence is that the application retrieves a sample object by identifier after lifecycle policy processing. It is not the most direct answer because object storage is a suitable abstraction for large unstructured objects addressed by identifiers and metadata.
Question 194
During a hospital data-center migration, the integrator finds that a media archive requires metadata-driven retrieval of large objects and automatic retention policies, not mutable shared-disk access. The team must make a decision specific to this observed storage behavior, not an unrelated platform change. Which technology mechanism best explains why the current approach does not meet the stated requirement?
- Data confidentiality depends on supported encryption and restricted access, not capacity or spindle count.
- Object storage is a suitable abstraction for large unstructured objects addressed by identifiers and metadata.
- Transactional database sizing must satisfy latency, concurrency and block-access needs in addition to usable capacity.
- User collaboration through shared folders is a file-service requirement rather than independent raw LUN presentation.
Explanation
Correct Answer
B:Object storage is a suitable abstraction for large unstructured objects addressed by identifiers and metadata. This mechanism accounts for the observed behavior. Supporting evidence is that the application retrieves a sample object by identifier after lifecycle policy processing.
Incorrect Answers
A:Data confidentiality depends on supported encryption and restricted access, not capacity or spindle count. This approach addresses a different storage condition: a healthcare application needs encrypted stored records and access separation, not simply a faster drive tier. Here, the differentiating evidence is that the application retrieves a sample object by identifier after lifecycle policy processing. It is not the most direct answer because object storage is a suitable abstraction for large unstructured objects addressed by identifiers and metadata.
C:Transactional database sizing must satisfy latency, concurrency and block-access needs in addition to usable capacity. This approach addresses a different storage condition: a customer proposes a capacity-optimized file archive for a transactional database that needs consistently low block-I/O latency. Here, the differentiating evidence is that the application retrieves a sample object by identifier after lifecycle policy processing. It is not the most direct answer because object storage is a suitable abstraction for large unstructured objects addressed by identifiers and metadata.
D:User collaboration through shared folders is a file-service requirement rather than independent raw LUN presentation. This approach addresses a different storage condition: a department requests a single shared folder tree with per-team permissions and ordinary desktop file operations. Here, the differentiating evidence is that the application retrieves a sample object by identifier after lifecycle policy processing. It is not the most direct answer because object storage is a suitable abstraction for large unstructured objects addressed by identifiers and metadata.
Question 195
During a regional campus infrastructure refresh, the integrator finds that a media archive requires metadata-driven retrieval of large objects and automatic retention policies, not mutable shared-disk access. The team must make a decision specific to this observed storage behavior, not an unrelated platform change. Which focused observation best validates the suspected mechanism, rather than an unrelated condition?
- A documented management test confirms which actions remain possible when external management connectivity is blocked.
- A privilege test and key-recovery rehearsal confirm protected data access remains controlled.
- The application retrieves a sample object by identifier after lifecycle policy processing.
- A pilot client can browse the expected hierarchy and access only permitted folders.
Explanation
Correct Answer
C:The application retrieves a sample object by identifier after lifecycle policy processing. That result distinguishes the suspected cause from unrelated storage symptoms. The mechanism is that object storage is a suitable abstraction for large unstructured objects addressed by identifiers and metadata.
Incorrect Answers
A:A documented management test confirms which actions remain possible when external management connectivity is blocked. This approach addresses a different storage condition: a regulated environment has restricted outbound connectivity and requires local service while considering centralized cloud management. Here, the differentiating evidence is that the application retrieves a sample object by identifier after lifecycle policy processing. It is not the most direct answer because object storage is a suitable abstraction for large unstructured objects addressed by identifiers and metadata.
B:A privilege test and key-recovery rehearsal confirm protected data access remains controlled. This approach addresses a different storage condition: a healthcare application needs encrypted stored records and access separation, not simply a faster drive tier. Here, the differentiating evidence is that the application retrieves a sample object by identifier after lifecycle policy processing. It is not the most direct answer because object storage is a suitable abstraction for large unstructured objects addressed by identifiers and metadata.
D:A pilot client can browse the expected hierarchy and access only permitted folders. This approach addresses a different storage condition: a department requests a single shared folder tree with per-team permissions and ordinary desktop file operations. Here, the differentiating evidence is that the application retrieves a sample object by identifier after lifecycle policy processing. It is not the most direct answer because object storage is a suitable abstraction for large unstructured objects addressed by identifiers and metadata.
Question 196
During a private-cloud commissioning project, the integrator finds that a media archive requires metadata-driven retrieval of large objects and automatic retention policies, not mutable shared-disk access. The team must make a decision specific to this observed storage behavior, not an unrelated platform change. Which corrective or deployment decision most directly addresses the demonstrated requirement or fault?
- Select a supported low-latency block solution sized to the measured workload envelope.
- Specify a supported file service and directory-permission model for the requirement.
- Size the design to both usable space and realistic simultaneous performance demand.
- Design supported object storage with lifecycle and retention controls aligned to the application.
Explanation
Correct Answer
D:Design supported object storage with lifecycle and retention controls aligned to the application. This response addresses the technical dependency: object storage is a suitable abstraction for large unstructured objects addressed by identifiers and metadata. Acceptance should establish that the application retrieves a sample object by identifier after lifecycle policy processing.
Incorrect Answers
A:Select a supported low-latency block solution sized to the measured workload envelope. This approach addresses a different storage condition: a customer proposes a capacity-optimized file archive for a transactional database that needs consistently low block-I/O latency. Here, the differentiating evidence is that the application retrieves a sample object by identifier after lifecycle policy processing. It is not the most direct answer because object storage is a suitable abstraction for large unstructured objects addressed by identifiers and metadata.
B:Specify a supported file service and directory-permission model for the requirement. This approach addresses a different storage condition: a department requests a single shared folder tree with per-team permissions and ordinary desktop file operations. Here, the differentiating evidence is that the application retrieves a sample object by identifier after lifecycle policy processing. It is not the most direct answer because object storage is a suitable abstraction for large unstructured objects addressed by identifiers and metadata.
C:Size the design to both usable space and realistic simultaneous performance demand. This approach addresses a different storage condition: a new platform is sized only by combined capacity although analytics, VM boot storms and databases have different I/O patterns. Here, the differentiating evidence is that the application retrieves a sample object by identifier after lifecycle policy processing. It is not the most direct answer because object storage is a suitable abstraction for large unstructured objects addressed by identifiers and metadata.
Question 197
During a hospital data-center migration, the integrator finds that a media archive requires metadata-driven retrieval of large objects and automatic retention policies, not mutable shared-disk access. The team must make a decision specific to this observed storage behavior, not an unrelated platform change. Which repeatable operating practice best reduces recurrence or avoids the same design error?
- Test retrieval costs, immutability behavior and retention before adoption.
- Include deliberate single-fabric failure tests in design acceptance.
- Audit service dependencies and offline recovery procedures before deployment.
- Test encrypted data recovery and administrator separation before go-live.
Explanation
Correct Answer
A:Test retrieval costs, immutability behavior and retention before adoption. This safeguard targets the known exposure before another incident. Operations should confirm that the application retrieves a sample object by identifier after lifecycle policy processing.
Incorrect Answers
B:Include deliberate single-fabric failure tests in design acceptance. This approach addresses a different storage condition: a proposed mission-critical array has two controllers but every application host connects through one FC switch. Here, the differentiating evidence is that the application retrieves a sample object by identifier after lifecycle policy processing. It is not the most direct answer because object storage is a suitable abstraction for large unstructured objects addressed by identifiers and metadata.
C:Audit service dependencies and offline recovery procedures before deployment. This approach addresses a different storage condition: a regulated environment has restricted outbound connectivity and requires local service while considering centralized cloud management. Here, the differentiating evidence is that the application retrieves a sample object by identifier after lifecycle policy processing. It is not the most direct answer because object storage is a suitable abstraction for large unstructured objects addressed by identifiers and metadata.
D:Test encrypted data recovery and administrator separation before go-live. This approach addresses a different storage condition: a healthcare application needs encrypted stored records and access separation, not simply a faster drive tier. Here, the differentiating evidence is that the application retrieves a sample object by identifier after lifecycle policy processing. It is not the most direct answer because object storage is a suitable abstraction for large unstructured objects addressed by identifiers and metadata.
Question 198
During a regional campus infrastructure refresh, the integrator finds that a media archive requires metadata-driven retrieval of large objects and automatic retention policies, not mutable shared-disk access. The team must make a decision specific to this observed storage behavior, not an unrelated platform change. Which risk assessment most accurately describes the effect of leaving this specific dependency unresolved?
- Deferring correction can leave the observed condition unresolved: a proposed mission-critical array has two controllers but every application host connects through one FC switch. The underlying constraint remains that redundant array controllers cannot compensate for a single SAN fabric failure if all host paths share that fabric.
- Deferring correction can leave the observed condition unresolved: a media archive requires metadata-driven retrieval of large objects and automatic retention policies, not mutable shared-disk access. The underlying constraint remains that object storage is a suitable abstraction for large unstructured objects addressed by identifiers and metadata.
- Deferring correction can leave the observed condition unresolved: a customer demands virtually no acknowledged-write loss across two data centers and a vendor proposes periodic asynchronous copies without a caveat. The underlying constraint remains that periodic asynchronous replication may leave a recoverable gap after sudden failure, unlike correctly implemented synchronous acknowledgement.
- Deferring correction can leave the observed condition unresolved: a regulated environment has restricted outbound connectivity and requires local service while considering centralized cloud management. The underlying constraint remains that cloud-managed workflows may require outbound connectivity while on-system interfaces can provide certain supported local operations.
Explanation
Correct Answer
B:Deferring correction can leave the observed condition unresolved: a media archive requires metadata-driven retrieval of large objects and automatic retention policies, not mutable shared-disk access. The underlying constraint remains that object storage is a suitable abstraction for large unstructured objects addressed by identifiers and metadata. The continued impact follows the identified mechanism: object storage is a suitable abstraction for large unstructured objects addressed by identifiers and metadata.
Incorrect Answers
A:Deferring correction can leave the observed condition unresolved: a proposed mission-critical array has two controllers but every application host connects through one FC switch. The underlying constraint remains that redundant array controllers cannot compensate for a single SAN fabric failure if all host paths share that fabric. This approach addresses a different storage condition: a proposed mission-critical array has two controllers but every application host connects through one FC switch. Here, the differentiating evidence is that the application retrieves a sample object by identifier after lifecycle policy processing. It is not the most direct answer because object storage is a suitable abstraction for large unstructured objects addressed by identifiers and metadata.
C:Deferring correction can leave the observed condition unresolved: a customer demands virtually no acknowledged-write loss across two data centers and a vendor proposes periodic asynchronous copies without a caveat. The underlying constraint remains that periodic asynchronous replication may leave a recoverable gap after sudden failure, unlike correctly implemented synchronous acknowledgement. This approach addresses a different storage condition: a customer demands virtually no acknowledged-write loss across two data centers and a vendor proposes periodic asynchronous copies without a caveat. Here, the differentiating evidence is that the application retrieves a sample object by identifier after lifecycle policy processing. It is not the most direct answer because object storage is a suitable abstraction for large unstructured objects addressed by identifiers and metadata.
D:Deferring correction can leave the observed condition unresolved: a regulated environment has restricted outbound connectivity and requires local service while considering centralized cloud management. The underlying constraint remains that cloud-managed workflows may require outbound connectivity while on-system interfaces can provide certain supported local operations. This approach addresses a different storage condition: a regulated environment has restricted outbound connectivity and requires local service while considering centralized cloud management. Here, the differentiating evidence is that the application retrieves a sample object by identifier after lifecycle policy processing. It is not the most direct answer because object storage is a suitable abstraction for large unstructured objects addressed by identifiers and metadata.
Question 199
During a retail platform capacity review, the integrator finds that a customer demands virtually no acknowledged-write loss across two data centers and a vendor proposes periodic asynchronous copies without a caveat. The team must make a decision specific to this observed storage behavior, not an unrelated platform change. Which targeted initial diagnostic best isolates the technical issue before altering production configuration?
- Document data-at-rest encryption, key custody, role separation and backup requirements.
- Measure expected IOPS, 95th percentile latency and host access protocol before selecting a platform.
- Compare the required RPO to the guaranteed behavior of each supported replication policy.
- Confirm SMB or NFS compatibility, file namespace and identity requirements.
Explanation
Correct Answer
C:Compare the required RPO to the guaranteed behavior of each supported replication policy. This verification tests the suspected mechanism: periodic asynchronous replication may leave a recoverable gap after sudden failure, unlike correctly implemented synchronous acknowledgement. The confirming result is that a fault test measures last committed remote write and shows whether the selected mode meets the RPO.
Incorrect Answers
A:Document data-at-rest encryption, key custody, role separation and backup requirements. This approach addresses a different storage condition: a healthcare application needs encrypted stored records and access separation, not simply a faster drive tier. Here, the differentiating evidence is that a fault test measures last committed remote write and shows whether the selected mode meets the RPO. It is not the most direct answer because periodic asynchronous replication may leave a recoverable gap after sudden failure, unlike correctly implemented synchronous acknowledgement.
B:Measure expected IOPS, 95th percentile latency and host access protocol before selecting a platform. This approach addresses a different storage condition: a customer proposes a capacity-optimized file archive for a transactional database that needs consistently low block-I/O latency. Here, the differentiating evidence is that a fault test measures last committed remote write and shows whether the selected mode meets the RPO. It is not the most direct answer because periodic asynchronous replication may leave a recoverable gap after sudden failure, unlike correctly implemented synchronous acknowledgement.
D:Confirm SMB or NFS compatibility, file namespace and identity requirements. This approach addresses a different storage condition: a department requests a single shared folder tree with per-team permissions and ordinary desktop file operations. Here, the differentiating evidence is that a fault test measures last committed remote write and shows whether the selected mode meets the RPO. It is not the most direct answer because periodic asynchronous replication may leave a recoverable gap after sudden failure, unlike correctly implemented synchronous acknowledgement.
Question 200
During an enterprise storage deployment, the integrator finds that a customer demands virtually no acknowledged-write loss across two data centers and a vendor proposes periodic asynchronous copies without a caveat. The team must make a decision specific to this observed storage behavior, not an unrelated platform change. Which technology mechanism best explains why the current approach does not meet the stated requirement?
- Cloud-managed workflows may require outbound connectivity while on-system interfaces can provide certain supported local operations.
- Data confidentiality depends on supported encryption and restricted access, not capacity or spindle count.
- Transactional database sizing must satisfy latency, concurrency and block-access needs in addition to usable capacity.
- Periodic asynchronous replication may leave a recoverable gap after sudden failure, unlike correctly implemented synchronous acknowledgement.
Explanation
Correct Answer
D:Periodic asynchronous replication may leave a recoverable gap after sudden failure, unlike correctly implemented synchronous acknowledgement. This mechanism accounts for the observed behavior. Supporting evidence is that a fault test measures last committed remote write and shows whether the selected mode meets the RPO.
Incorrect Answers
A:Cloud-managed workflows may require outbound connectivity while on-system interfaces can provide certain supported local operations. This approach addresses a different storage condition: a regulated environment has restricted outbound connectivity and requires local service while considering centralized cloud management. Here, the differentiating evidence is that a fault test measures last committed remote write and shows whether the selected mode meets the RPO. It is not the most direct answer because periodic asynchronous replication may leave a recoverable gap after sudden failure, unlike correctly implemented synchronous acknowledgement.
B:Data confidentiality depends on supported encryption and restricted access, not capacity or spindle count. This approach addresses a different storage condition: a healthcare application needs encrypted stored records and access separation, not simply a faster drive tier. Here, the differentiating evidence is that a fault test measures last committed remote write and shows whether the selected mode meets the RPO. It is not the most direct answer because periodic asynchronous replication may leave a recoverable gap after sudden failure, unlike correctly implemented synchronous acknowledgement.
C:Transactional database sizing must satisfy latency, concurrency and block-access needs in addition to usable capacity. This approach addresses a different storage condition: a customer proposes a capacity-optimized file archive for a transactional database that needs consistently low block-I/O latency. Here, the differentiating evidence is that a fault test measures last committed remote write and shows whether the selected mode meets the RPO. It is not the most direct answer because periodic asynchronous replication may leave a recoverable gap after sudden failure, unlike correctly implemented synchronous acknowledgement.
HPE Storage Integrator Solutions (HPE0-J83) Practice Tests