A regional textile manufacturer is preparing an SAP HANA lifecycle update rehearsal for an on-premises database. The database is available, and the update package has been staged. During the final review, the administrator finds that the rollback checkpoint in the runbook still references the previous rehearsal's backup timestamp. The current backup completed successfully, but the rollback section was not updated before the approval meeting.
The constraint is that the rehearsal must begin only after rollback evidence matches the current lifecycle activity. The administrator must prevent execution from starting with a recovery reference that belongs to an earlier rehearsal.
What should the administrator do before approving the lifecycle update rehearsal?

CHALLENGE 1 - Hypercare Configuration Record Traceability
During hypercare review, customer service test users can open outage analytics reports from both SAP HANA systems. The installed stabilization database has its active configuration documented, but the upgraded service reporting system has one post-upgrade value recorded only in a support handover note. What should the administrator do before accepting the hypercare comparison?

CHALLENGE 3 - Cloud Modernization Evidence Boundary
The modernization lead wants the SAP HANA Cloud database included in the same readiness status because it is provisioned and has a limited outage analytics dataset. The cloud environment has not completed the startup, monitoring, or recovery evidence package used for active hypercare systems. What is the best response?

CHALLENGE 3 - Cloud Readiness Evidence Separation
The modernization lead wants the SAP HANA Cloud database included in the same readiness status as the on-premises SIT systems because the cloud database is provisioned. The cloud environment has only limited test data and no complete monitoring or recovery evidence package. What is the best response?

A regional medical equipment distributor restarts SAP HANA after a maintenance window. SAP HANA cockpit shows the database as available, and a small set of administrator checks passes. However, the configuration worksheet requires a post-start parameter verification, and the validation note still contains the parameter values captured before maintenance. A warehouse analytics user confirms that one dashboard opens successfully.
The constraint is that the administrator must close the maintenance window only after confirming the active configuration state. General availability and one successful dashboard cannot substitute for validation that the configured runtime values match the expected post-maintenance baseline.
What should the administrator do next?