Which scenario is typically well-suited for NoSQL databases?

• A. SQL databases are best for accounting with strict schemas; NoSQL is suitable for real-time analytics or content stores.
• B. NoSQL cannot scale to large datasets.
• C. SQL has flexible schema and eventual consistency.
• D. NoSQL supports ACID transactions across tables.

Answer: (A)

The main idea is that NoSQL databases excel when you need to handle large, varied data without a rigid schema, and you want to scale out easily. Real-time analytics and content stores are classic cases: you accumulate diverse kinds of data (texts, JSON, multimedia, logs), you need fast ingest and query performance, and you may not know all data fields in advance. NoSQL databases are designed to be schema-flexible and to scale horizontally to accommodate big data and high throughput, which makes them a natural fit for those scenarios.

In contrast, accounting and similar transactional workloads benefit from SQL databases because of strong consistency and a fixed schema, where precise, multi-record transactions and data integrity are crucial. The other statements either misstate NoSQL’s scaling capabilities or mix up typical characteristics of SQL versus NoSQL. That’s why the choice describing NoSQL as suitable for real-time analytics or content stores is the best fit.