Cloud Digital Leader Practice Question: A solutions architect is explaining why using…

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Managed databases are always significantly cheaper than self-managed databases on VMs

  Why it's wrong here

  Cloud provider pricing for managed databases typically includes a premium per vCPU, GB, and I/O operation to cover the provider's automated administration (backups, patching, failover). For stable, large workloads with low administrative overhead or when DBA talent is already available in-house, a self-managed database on a VM can be significantly less expensive in infrastructure costs alone. The managed option only tends to be cheaper—or comparable—when you factor in soft costs like DBA salaries, manual intervention, and downtime risk. Hence, the absolute statement that managed databases are always significantly cheaper is false.

• ✓

  Managed database services automate operational tasks like backups, patching, HA failover, and scaling — freeing engineering teams to focus on application development rather than database administration

  Why this is correct

  This is the core value proposition of managed databases. The cloud provider handles: automated daily backups with point-in-time recovery, OS and database software patching, automatic failover for high availability, and storage scaling. Engineering teams avoid the specialized DBA work required for self-managed databases.

• ✗

  Managed databases guarantee better query performance than self-managed databases for all workload types

  Why it's wrong here

  Query performance is fundamentally workload-specific and tied to the underlying hardware, storage architecture, configuration parameters, and query tuning. Managed databases usually abstract away hardware-level tuning, and their storage may be shared or network-attached, which can introduce latency for certain high-throughput or low-latency workloads. In contrast, a self-managed database on a dedicated VM or bare-metal server can be fine-tuned with customized kernel parameters, high-performance local SSDs, and specialized engines. Therefore, a managed service cannot guarantee better performance universally—only for the common use cases it was optimized for.

• ✗

  Managed databases provide stronger data encryption than self-managed databases on VMs

  Why it's wrong here

  Both managed and self-managed databases can be configured to use identical encryption standards, such as AES-256 for data at rest and TLS 1.3 for data in transit. The strength of encryption is determined by the cipher suite, key length, and key management practices—not by the deployment model. While managed services often simplify key rotation and integrate with IAM/KMS, a self-managed database on a VM can achieve the equivalent cryptographic posture if properly configured. Therefore, claiming that managed databases inherently provide stronger encryption is incorrect.

Go deeper

Related to this question