A laboratory services company runs SAP HANA for sample throughput reporting. The database remains available, but SAP HANA cockpit shows a recurring warning for long-running statements during the evening batch reporting period. The reporting job completes, yet the next morning dashboard refresh is slower than expected. A support coordinator proposes increasing dashboard timeout values because the reports eventually finish.
The constraint is that the administrator must correct the operational cause rather than mask the symptom. The system must remain available, and any adjustment must be based on monitoring evidence from the affected execution window.
Which response best fits the monitoring evidence?

• A. Increase dashboard timeout values so users can wait longer for the morning refresh to complete.
• B. Analyze the long-running statement pattern during the batch period and adjust the workload timing or configuration based on the validated cause.
• C. Disable the evening reporting job until dashboard refresh times return to the expected level.
• D. Restart the database after evening reporting so long-running statement history does not affect the next dashboard cycle.

CHALLENGE 4 - SIT Recovery Evidence Sequencing
Backups completed before SIT began for the upgraded and newly installed SAP HANA databases. The installed test database has recovery validation scheduled before the second SIT cycle, but it is not yet complete. What should happen before releasing the next SIT cycle?

• A. Release the cycle because completed backups are enough for integration testing continuity.
• B. Replace recovery validation with dashboard availability because SIT is not production.
• C. Release the cycle and perform recovery validation only if the database becomes unavailable.
• D. Complete recovery validation and document startup behavior before release approval.

A regional medical devices distributor is preparing an SAP HANA upgrade rehearsal for an on-premises database. The upgrade package is available, and the database is currently running. Before the rehearsal begins, the administrator compares the maintenance checklist with the validation output and finds that the prerequisite check was completed before the latest package was staged. SAP HANA cockpit still shows normal availability, and the technical lead wants to proceed because the system has not reported an error.
The constraint is that the administrator must base the upgrade decision on preparation evidence that matches the current package state. The rehearsal should not begin from validation output created before the final staged artifact was present.
What should the administrator do before starting the rehearsal?

• A. Add a note to the checklist explaining that the prerequisite check was completed before package staging.
• B. Restart the database so the earlier prerequisite output can be refreshed during the upgrade startup sequence.
• C. Rerun the prerequisite validation after confirming the final staged package, then start only if the current checks pass.
• D. Proceed with the rehearsal because the database is available and no current SAP HANA cockpit error is visible.

A regional publishing group is preparing an SAP HANA administration runbook for a mixed landscape that includes an on-premises database and an SAP HANA Cloud environment. The draft runbook uses one lifecycle calendar for both environments. During review, the administrator notices that the calendar combines an on-premises upgrade window, SAP HANA Cloud availability checks, and migration rehearsal milestones into one approval step. SAP HANA cockpit confirms the on-premises database is available, and SAP HANA Cloud Central confirms the cloud environment is running.
The constraint is that the runbook must support correct operational decisions for each environment without treating mixed lifecycle evidence as one shared approval state.
Which action best improves the runbook before operational use?

• A. Separate lifecycle validation steps by environment and require evidence specific to each SAP HANA administration activity.
• B. Use the on-premises upgrade window as the controlling lifecycle event for the entire mixed landscape.
• C. Remove migration rehearsal milestones from the runbook until the SAP HANA Cloud environment becomes the active workload target.
• D. Approve the runbook because both SAP HANA environments are available in their administration tools.