Cloud Digital Leader Why cloud technology is transforming business Practice Question

Answer analysis

Option-by-option breakdown

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

• ✗

  Lower storage costs for paper documents by digitizing them in Cloud Storage.

  Why it's wrong here

  Scanned PDFs placed in Cloud Storage reduce physical storage costs and allow easier indexing, but they are inert objects unless consumed by an intelligent layer. Without Document AI or other extraction services to parse the scanned content, underwriters must still open each PDF, manually interpret financial data, and key the same information into the loan system—the same bottleneck as paper. Lower storage cost does not accelerate the decision loop; it only addresses a minor cost, not the critical path.

• ✓

  Cloud-based AI/ML services and workflow automation that process applications end-to-end without manual steps.

  Why this is correct

  Managed AI services such as Document AI extract key-value pairs from loan applications and financial statements, while auto-scaled workflow systems (e.g., Cloud Workflows or Dataflow) route verified data to risk-scoring models and trigger conditional approvals. This eliminates manual data entry, cross-department handoffs, and human review bottlenecks, shrinking processing time from weeks to hours. Because the entire end-to-end pipeline runs server-free, decisions can be made in near-real-time without human intervention.

• ✗

  Moving the bank's email system to a cloud-based provider.

  Why it's wrong here

  Migrating email to a cloud provider like Google Workspace is a simple lift-and-shift that enhances mail reliability, anti-spam filtering, and internal collaboration, but it does not touch the loan origination and underwriting pipeline. Loan decisions still require manual document review and approval sign-offs, so the two-week processing cycle remains unchanged. Email is a communication tool, not a transactional component of the application workflow.

• ✗

  Using Cloud SQL instead of on-premises Oracle database.

  Why it's wrong here

  Swapping Oracle for a managed Cloud SQL instance (e.g., PostgreSQL or MySQL) simplifies database administration, improves availability, and reduces licensing costs, but the application code that processes loans is unchanged. If the loan system still relies on human agents to validate documents and assign risk scores, the database migration will not compress processing time from 14 days to 24 hours. A managed database does not inherently provide business logic automation—workflow orchestration and ML inference are separate services that must be explicitly built.

Go deeper

Related to this question