A regional healthcare analytics team uses SAP HANA for overnight reporting. SAP HANA cockpit shows normal database availability, but the monitoring dashboard has not updated several performance indicators since the previous evening. Users can still run reports, and no service outage is visible. A support analyst suggests ignoring the stale indicators because the database is responding to queries.
The constraint is that the administrator must restore trustworthy monitoring before the next overnight reporting cycle. The team needs evidence that monitoring data reflects the current system state, not only that the database can execute user requests.
Which action best addresses the monitoring issue?

• A. Investigate the monitoring collection state, correct the collection gap, and validate that current indicators update before the next cycle.
• B. Increase alert thresholds until the stale indicators no longer affect operational review decisions.
• C. Restart user reporting sessions so the dashboard can display fresh performance values from new executions.
• D. Approve the next cycle because successful report execution proves that monitoring data is not required.

解説: (CertJuken メンバーにのみ表示されます)

CHALLENGE 2 - Replenishment Analytics Monitoring Baseline
The database team can either tune memory-related settings now to improve evening replenishment analytics or first preserve baseline monitoring evidence and tune only if current evidence supports it. Which option is most defensible?

• A. Tune now and use the improved replenishment runtime as the remediation success measure.
• B. Preserve baseline monitoring evidence first, then approve tuning if current evidence supports it.
• C. Reject all tuning until all store analytics reporting moves to SAP HANA Cloud.
• D. Replace monitoring review with merchandising user feedback because the reports are business-facing.

解説: (CertJuken メンバーにのみ表示されます)

A regional office equipment company completes an SAP HANA upgrade rehearsal for an on-premises database. The database starts after the upgrade, and SAP HANA cockpit shows the system as available. During validation, the administrator finds that the operations runbook still references the pre-upgrade administration sequence for start, monitoring, and backup checks. The technical lead wants to approve the rehearsal because the upgraded system is running.
The constraint is that the administrator must ensure the runbook reflects the upgraded lifecycle state before using the rehearsal to approve production execution. The decision must not rely only on successful startup.
What should the administrator do before accepting the rehearsal?

• A. Keep the pre-upgrade runbook because the administration sequence worked before the upgrade rehearsal.
• B. Update the runbook for the upgraded lifecycle state, execute the administration sequence, and accept only after validation passes.
• C. Approve the rehearsal because the upgraded database starts and SAP HANA cockpit shows availability.
• D. Create a new data backup and use backup completion as proof that the post-upgrade runbook is valid.

解説: (CertJuken メンバーにのみ表示されます)

A subscription services provider operates SAP HANA in a mixed environment. After a planned configuration adjustment intended to improve throughput, administrators observe that nightly batch processing finishes on time, but interactive analyst queries now show intermittent delays. Monitoring shows no broad system outage, and memory consumption remains stable. CPU peaks occur only during specific interactive workload windows.
The platform owner wants a correction that preserves the batch improvement while avoiding a broad reversal of the recent tuning changes. The team must decide based on actual workload behavior rather than a general assumption that the entire configuration set should be rolled back.
What is the best next step?

• A. Move the interactive workload to the cloud database without further analysis because the current landscape already supports mixed deployment.
• B. Reverse all recent configuration changes immediately because any slowdown after tuning proves the full change set was invalid.
• C. Compare the changed configuration against the affected workload pattern and adjust only the setting that is degrading interactive execution behavior.
• D. Increase system memory allocation first because stable memory use indicates the system is close to its capacity boundary.

CHALLENGE 4 - Release Recoverability Evidence Gate
Backups completed for the upgraded reporting system and the newly installed UAT database before testing began. Recovery validation for the UAT database is scheduled but not complete, and the upgraded system has only backup completion evidence. What should happen before final UAT sign-off supports release approval?

• A. Replace recovery validation with dashboard availability because this is not production cutover.
• B. Perform recovery validation only if reporting becomes unavailable during UAT.
• C. Approve sign-off because completed backups are enough for release continuity.
• D. Complete recovery validation and document startup behavior for the release systems.

解説: (CertJuken メンバーにのみ表示されます)