SAP C_DBADM_2601 Prüfungsthemen:
| Abschnitt | Gewichtung | Ziele |
|---|---|---|
| Datenbankverwaltung und Konfiguration | 11 % – 20 % | - Benutzer- und Berechtigungsverwaltung - Ressourcenverwaltung und -zuweisung - Systemkonfiguration und Parameter |
| Sicherung und Wiederherstellung | 11 % – 20 % | - Hochverfügbarkeit und Notfallwiederherstellung - Sicherungsstrategien und deren Umsetzung - Wiederherstellungsverfahren und Anwendungsfälle |
| Überwachung und Fehlerbehebung | 11 % – 20 % | - Fehlerdiagnose und Problemlösung - Überwachungswerkzeuge und Messwerte - Leistungsanalyse und -optimierung |
| Architektur und Bereitstellung von SAP HANA | 11 % – 20 % | - Bereitstellungsvarianten: Vor-Ort-System und Cloud - Installations- und Aktualisierungsverfahren - Architekturkomponenten und Grundlagen |
| Datenbanksicherheit | 11 % – 20 % | - Prüfverfahren und Einhaltung von Vorschriften - Datenschutz und Zugriffskontrolle - Sicherheitseinstellungen und Verschlüsselung |
| Migration und Integration | 11 % – 20 % | - Integration in SAP-Systemlandschaften - Datenübertragung und Replikation - Migration auf SAP HANA Cloud |
SAP Certified - Database Administrator - SAP HANA C_DBADM_2601 Prüfungsfragen mit Lösungen
CHALLENGE 1 - Supplier Allocation Readiness for Shared Material Demand
A plant buyer argues that urgent materials should allow local supplier substitution whenever the expected allocation pattern does not appear quickly enough during rehearsal. The cutover office is concerned that this approach will create unpredictable post-go-live support demands. Which decision is most appropriate?
- A. Pause all supplier-allocation validation until the legacy system is fully shut down
- B. Permit local supplier substitution for all urgent materials because speed is more important during rehearsal
- C. Remove shared-demand materials from rehearsal scope and validate only plant-specific items
- D. Preserve centrally governed allocation behavior and confirm whether shared-demand materials enter purchasing execution with aligned sourcing assumptions
Antwort: D 🗳️
Erklärung: (Nur für DeutschPrüfung-Mitglieder sichtbar)
A regional wholesale distributor runs SAP HANA in a mixed landscape: one on-premises production database and one SAP HANA Cloud database for newer workloads. After a storage maintenance window, the on-premises database starts, but business users report that the most recent sales corrections are missing. In the administration view, the database status is green, the last full backup completed successfully two nights ago, and the latest log backup timestamp is much older than expected.
The operations lead wants recovery completed quickly, but the team must avoid losing committed transactions that were already acknowledged before the outage. The environment allows both cockpit-based checks and command-level administration.
What is the best next action to restore service while addressing the upstream cause of the recovery gap?
- A. Restart the SAP HANA services again to force log processing and then repeat the recovery with the same backup set.
- B. Verify why log backups stopped, re-establish log backup continuity if possible, and then recover using the latest valid full backup plus available log backups.
- C. Create a new full backup now and use that backup as the baseline for transactional recovery of the missing changes.
- D. Restore the latest full backup immediately and reopen the database for users because the database is already running normally.
Antwort: B 🗳️
Erklärung: (Nur für DeutschPrüfung-Mitglieder sichtbar)
CHALLENGE 1 - First Close Configuration Traceability
During first close rehearsal, claims analytics reports load successfully from the upgraded SAP HANA system. The final administration record does not show whether the post-upgrade configuration adjustment was active during the rehearsal. What should the administrator do before accepting the close reporting evidence?
- A. Apply the SAP HANA Cloud setting to the upgraded system to standardize the landscape.
- B. Reconcile the active configuration state with the final administration record before sign-off.
- C. Remove the configuration adjustment from the review because reports loaded successfully.
- D. Accept the evidence because successful report loading confirms close readiness.
Antwort: B 🗳️
Erklärung: (Nur für DeutschPrüfung-Mitglieder sichtbar)
A regional environmental testing company operates SAP HANA on-premises for laboratory turnaround analytics and is preparing a separate SAP HANA Cloud environment for migration rehearsal. During an administration review, the landscape worksheet shows one shared "administration owner" for both environments, but the operational evidence comes from different tools. SAP HANA cockpit confirms the on-premises system status, while SAP HANA Cloud Central confirms the cloud database status. The worksheet does not show which owner must act on each environment-specific alert or readiness item.
The constraint is that the administrator must make the landscape worksheet actionable without changing the assigned team structure. The handover must distinguish current operations from cloud migration readiness.
Which action best resolves the landscape ownership issue?
- A. Treat the on-premises SAP HANA cockpit status as the controlling readiness signal for both environments.
- B. Keep the shared owner entry because both systems are SAP HANA databases and the same team supports them.
- C. Remove the SAP HANA Cloud readiness items until the migration rehearsal becomes the active operational workload.
- D. Split the worksheet by environment, evidence source, and operational responsibility while retaining the same administration team.
Antwort: D 🗳️
Erklärung: (Nur für DeutschPrüfung-Mitglieder sichtbar)
A regional healthcare supply wholesaler runs SAP HANA for distribution analytics. SAP HANA cockpit shows the database as available, but the operations dashboard displays normal response time while a workload review shows a short queue increase during invoice analytics processing. Users reported a delay during the same interval. The support lead suggests increasing response-time thresholds because the dashboard did not show a severe issue.
The constraint is that the administrator must explain the delay using consistent monitoring evidence before changing thresholds. The next invoice analytics cycle must remain observable without masking the symptom.
Which action best supports correct troubleshooting?
- A. Increase response-time thresholds so minor delays no longer appear as operational concerns.
- B. Compare the dashboard interval with workload queue evidence, validate the timing relationship, and investigate the queue source before changing thresholds.
- C. Restart SAP HANA before the next invoice analytics cycle to reset both response-time and queue measurements.
- D. Ignore the workload queue increase because the operations dashboard showed normal response time.
Antwort: B 🗳️
Erklärung: (Nur für DeutschPrüfung-Mitglieder sichtbar)






1455 Kundenbewertungen

