What is a key consideration when identifying the node type for a database-centric workflow on ECS?

Question

Options

• AColor depth of the monitor
• BStorage I/O and throughput capabilities
• CThe brand of hardware components
• DThe operating system's graphical user interface

• A
  2% (1)
• B
  94% (47)
• C
  4% (2)

Explanation

Storage I/O and throughput capabilities (B) are critical when selecting a node type for database-centric workloads on ECS because databases are inherently data-intensive - they constantly read from and write to disk. A node with insufficient I/O bandwidth or throughput creates a bottleneck that degrades query performance, replication speed, and overall application responsiveness, regardless of how much CPU or RAM the instance has.

Why the distractors are wrong:

• A (Color depth of monitor): Display properties have zero bearing on server-side compute or storage performance.
• C (Brand of hardware): Cloud infrastructure abstracts away vendor specifics; workload characteristics - not brand loyalty - drive instance selection.
• D (OS graphical interface): Database servers run headlessly; the GUI is irrelevant and is typically disabled on production nodes to conserve resources.

Memory tip: Think "database = data movement." Whenever you see database in an infrastructure question, your instinct should jump to storage performance (IOPS, throughput, latency) - those are the metrics that make or break a data-heavy workload.

No community discussion yet for this question.