CHALLENGE 4 - Close Recovery Readiness Gate
The sponsor asks whether the first close package can be approved now because backups completed and reports loaded successfully. The administration lead can either approve now or delay briefly to complete recovery evidence for the systems in scope. Which path is most defensible?

• A. Approve now because report loading and backup completion satisfy close-cycle needs.
• B. Cancel the close rehearsal because recovery validation was not completed before reporting began.
• C. Approve now and attach recovery validation to the later SAP HANA Cloud transition plan.
• D. Delay briefly to complete recoverability evidence before first close sign-off.

A regional hospitality group runs SAP HANA for occupancy and revenue analytics. SAP HANA cockpit shows the database as available, but the operations team notices that a performance alert appears only after the reporting peak has already passed. The monitoring history shows that the alert condition existed during the peak window, but the alert evaluation schedule was changed during an administration cleanup. Reports eventually complete, so the support team suggests accepting the current behavior.
The constraint is that the administrator must ensure monitoring supports timely operational response, not only after-the-fact review. The next reporting peak must be covered by alert evaluation that reflects the active workload window.
Which action best addresses the alert timing issue?

• A. Raise the alert threshold so fewer delayed alerts appear in SAP HANA cockpit.
• B. Restart the database before the next peak so alert evaluation begins from a clean runtime state.
• C. Align the alert evaluation schedule with the reporting peak window and validate that alerts trigger during the active workload period.
• D. Accept the current monitoring behavior because reports eventually complete after the reporting peak.

A regional home improvement retailer uses SAP HANA for replenishment analytics in an on-premises administration environment. After a scheduled start, SAP HANA cockpit shows the database as available. During post-start validation, the administrator sees that a configuration parameter change is visible in the approved change record, but the active administration check still reports the old parameter value. Reports continue to run, and the service owner wants to close the maintenance window.
The constraint is that the administrator must verify the active configuration state before closure. The team must not accept the change record as sufficient evidence when the system artifact still shows the previous value.
What should the administrator do next?

• A. Update the change record with an additional note confirming that reports continue to run after startup.
• B. Restart the database again so the approved change record is automatically synchronized with the runtime check.
• C. Apply or activate the approved parameter change in the active administration context, then validate that the runtime check shows the approved value.
• D. Close the maintenance window because database availability and running reports prove that the change did not disrupt operations.

A regional food distribution company performs a recovery readiness exercise for its SAP HANA system before a seasonal ordering peak. The backup catalog shows the latest backup as complete, but the recovery checklist references an older backup point from the previous exercise. The operations team asks whether the exercise can be signed off because the latest backup itself completed successfully.
The constraint is that the recovery readiness record must demonstrate alignment between the selected recovery point, available backup evidence, and the intended exercise objective. The sign-off cannot rely on unrelated historical checklist entries.
Which action should the administrator take?

• A. Update the checklist to reference the current validated recovery point and confirm that it aligns with the available backup evidence before sign-off.
• B. Use the older backup point because it was already referenced in the previous recovery exercise.
• C. Sign off the exercise because the latest backup completed successfully.
• D. Create a new checklist entry after the seasonal peak to avoid delaying current operations.

A regional pharmaceutical distributor completes an SAP HANA installation rehearsal for a new on-premises administration environment. The installer reports completion, and the database can be started. During validation, SAP HANA cockpit shows the system as available, but the operations checklist shows that the database explorer connection was created using a temporary validation name instead of the final administration naming standard. The infrastructure team wants to accept the environment because the connection works.
The constraint is that the administrator must confirm a handover-ready installation, including administration evidence that will remain usable after acceptance. The team must not rely on a temporary validation artifact as the final operational reference.
What should the administrator do before accepting the installation handover?

• A. Defer connection naming cleanup until the first production monitoring cycle confirms database availability.
• B. Rename the administration evidence in the checklist only, without changing the actual database explorer connection.
• C. Accept the installation because the database starts and the temporary database explorer connection works.
• D. Create and verify the final database explorer connection using the approved administration naming standard, then repeat validation.