Database and application migration UGO's source library portrait function is trained with the key indicators of the database as the characteristics, abstracting the whole picture of the database…

Question

Options

• ADB name and DB creation time
• BCPU and memory usage
• CTable and SQL Complexity
• DIOPS and QPS

• A
  28% (7)
• B
  72% (18)

Explanation

Options B, C, and D are correct because UGO's portrait function is designed to characterize the database's operational profile - meaning it captures metrics that reflect how the database performs and how complex its workload is, not just its identity metadata. CPU and memory usage (B) reveal the resource consumption pattern of the source database, which is essential for sizing and planning the target environment. Table and SQL complexity (C) captures structural and query-level complexity, helping assess migration effort and compatibility. IOPS and QPS (D) measure I/O throughput and query volume, defining the performance baseline that the migrated system must match.

Option A is incorrect because the database name and creation time are administrative metadata - they describe what the database is called and when it was created, but they provide no insight into workload behavior, performance characteristics, or migration difficulty, so they are not useful profiling indicators.

Memory tip: When thinking about what "portraits" a database for migration, focus on the three performance dimensions - compute resources (B), data/query structure (C), and I/O throughput (D). A name and a birthday tell you nothing about how hard the database works.

No community discussion yet for this question.