C_DBADM sample questions & answers

Larkspur Outfitters, a national outdoor-apparel retailer, runs SAP HANA to support both its point-of-sale posting workload and its evening sales-analytics reporting. During go-live a junior administrator places a small, frequently-accessed configuration table — read and updated many times per second by the checkout process — into the same store type used for the large, wide sales-history table that analysts scan for aggregate reporting. After go-live the checkout team reports that individual single-record lookups and updates on the small table feel slower than expected under peak till traffic, while the analytics team is satisfied with reporting speed. The administrator confirms the table is loaded into memory, that the data content is correct, and that no errors appear in processing. A senior administrator asks the junior to correct the design so the small, transactional configuration table sits in the store type suited to frequent single-record access, while leaving the wide analytics table where it already performs well. The junior must identify which in-memory store fundamentally fits each access pattern rather than adjusting query text or adding hardware.

Which correction aligns each table with the in-memory store that fits its access pattern?

Meridian Home & Garden, a regional home-improvement retail chain, is preparing its first on-premises SAP HANA installation to support store-replenishment processing. The infrastructure team, eager to hit a fixed cutover date, procures a server chosen mainly on price and begins the lifecycle-management installation before completing any capacity assessment. Early in the run, the administrator notices the operating system on the chosen server is a general Linux build the team already had licensed, and that no formal estimate of the memory and compute the HANA workload will require was ever produced. A senior administrator halts the work, concerned that starting installation without confirming platform suitability risks an unsupported or under-provisioned system that will fail under real replenishment volumes. The administrator must correct the sequence so the platform is validated as suitable before the installation proceeds, addressing the prerequisites that were skipped rather than pushing the current install through to meet the date.

Which action corrects the skipped prerequisites before the installation should proceed?

Cobblestone Grocers, a supermarket cooperative, has just completed an on-premises SAP HANA installation and wants a newly hired administrator to begin day-to-day monitoring and administration through the web-based administration tool for on-premises and hybrid systems. The administrator opens the tool but reports that the target database is not yet available to work with: no monitoring cards for services, memory, or alerts appear for it, because the database has not been made known to the tool as an administrable resource. A colleague suggests the tool must be broken and proposes falling back to running ad-hoc commands from the command-line SQL client for every routine check instead. The lead administrator wants monitoring and administration done through the intended web tool and asks the new administrator to make the database appear there with its monitoring cards, correcting the setup step that was missed rather than abandoning the tool.

Which action makes the database appear in the web administration tool with its monitoring cards?

Tidewater Mercantile, a coastal department-store retailer, runs SAP HANA behind its online-order and inventory processing. During a promotional weekend, the administration tool raises a memory-usage alert and one analytics-heavy service is consuming an unusually large share of memory. The infrastructure manager, under pressure, wants to immediately order and add more memory to the server to clear the alert. Before approving spend, the administrator uses the monitoring and SQL-workload views and finds the spike coincides with a single, poorly-written analytical statement scanning far more data than the report needs, repeatedly submitted during the promotion; overall data volumes have not grown and no other service is under pressure. The administrator must decide the correct first response to the memory alert, distinguishing the underlying cause from the visible symptom rather than treating added hardware as the automatic fix while the offending statement keeps running.

What is the correct first response to the memory-usage alert?

Grindelwald Savings Bank runs its payments-processing database on SAP HANA. A large, frequently updated column table that records intraday transfer postings receives a heavy burst of writes each morning as branches open. During that burst, an administrator notices that read queries against this table slow noticeably, and monitoring shows the write-optimized delta portion of the table has grown large while relatively little has moved into the read-optimized main storage. Outside the morning burst, the table performs normally. Memory is not exhausted, no expensive individual statement stands out, and other tables behave as expected. A junior administrator, seeing the delta grow, wants to schedule the delta merge to run continuously every few minutes throughout the day so the delta never accumulates. The lead administrator asks for the correct handling of the delta merge for this write-heavy table, so that reads stay fast without the merge itself becoming a source of avoidable overhead during the busiest window.

How should the delta merge be handled for this write-heavy table?

Portmeadow Building Society runs its core deposits database on SAP HANA on-premises, with a recurring data backup of the database area scheduled to run automatically overnight. One morning an administrator reviewing the backup catalog notices that no new data backup entry appeared for the previous night; the most recent successful data backup is now two nights old. Investigation shows the scheduled overnight data backup did not complete because the configured backup destination was temporarily unavailable when the job ran, and the schedule did not retry. The database itself is healthy and online, ongoing transaction capture is unaffected, and today's scheduled run has not yet reached its window. The operations manager wants the data-area protection restored to a current state without waiting until the next automatic overnight run, and asks the administrator for the correct action to close the gap left by the missed scheduled data backup.

What is the correct action to restore current data-area protection after the missed scheduled backup?