Cloud Digital Leader Why cloud technology is transforming business Practice Question
A retail bank is building a partnership with a fintech startup. The bank provides regulated financial services infrastructure and customer reach; the fintech provides innovative digital experiences. Which cloud architectural pattern most naturally enables this kind of bank-fintech partnership?
⚠ Common exam trap
Many exam-takers confuse 'data sharing' with 'direct database access' (Option A), failing to recognize that secure, API-mediated access is the correct architectural pattern for regulated partnerships, not raw data exposure.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
An API-first Open Banking architecture where the bank exposes regulated capabilities (accounts, payments, KYC) through managed APIs that the fintech builds innovative experiences on top of
An API-first Open Banking architecture allows the bank to expose regulated capabilities (e.g., account information, payment initiation, KYC verification) through managed, secure APIs. The fintech can then build innovative digital experiences on top of these APIs without direct access to the bank's core systems, ensuring compliance, security, and loose coupling. This pattern aligns with PSD2 and Open Banking standards, enabling partnership without compromising regulatory control.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Giving the fintech startup direct database access to the bank's customer records system for maximum data sharing
Why it's wrong here
Direct database access would expose the bank's customer records system to an external third party without any governance layer, breaking the principle of least privilege and creating an uncontrolled blast radius. Banks are subject to strict regulations such as GDPR and PSD2, which mandate granular consent, audit logging, and data minimization—none of which a raw database link can provide. Any rogue query or compromised credential from the fintech side could jeopardize the entire core banking system, making this a severe security and compliance failure rather than a data-sharing win.
- ✓
An API-first Open Banking architecture where the bank exposes regulated capabilities (accounts, payments, KYC) through managed APIs that the fintech builds innovative experiences on top of
Why this is correct
This is the Open Banking / BaaP pattern. The bank's APIs provide the regulated foundation (PSD2, open banking standards); the fintech builds customer-facing innovation on top. API management (like Apigee) provides authentication, rate limiting, versioning, and analytics for the partnership. This is exactly how modern bank-fintech partnerships work.
- ✗
The bank should acquire the fintech startup and consolidate all technology onto the bank's legacy infrastructure
Why it's wrong here
Acquiring the fintech and migrating its technology onto the bank's legacy infrastructure would strip away the very agility the bank hoped to gain. Monolithic core banking platforms are not designed for the rapid, test-and-learn development cycles of a modern fintech, and forcing integration would incur massive cost, latency, and organizational friction. The unique value of the partnership lies in preserving the fintech's independent speed and innovation, so consolidation would effectively destroy the asset the bank wanted to leverage.
- ✗
The fintech should build all required banking infrastructure independently to avoid dependency on the bank's legacy systems
Why it's wrong here
Building independent banking infrastructure means the fintech would have to obtain a full banking license, meet capital adequacy requirements, and implement compliance, fraud, and AML systems from scratch—a multi-year, capital-intensive effort completely outside its core competency. Such duplication would not only delay time-to-market but would also erase the strategic reason for the partnership: to ride on the bank's existing regulated foundation while focusing on customer experience. The dependency the fintech fears is precisely what the partnership model transforms into a managed, contractual relationship.
Go deeper
Related to this question
Learn chapter
Cloud Digital Transformation
Key term
General Data Protection Regulation
A European Union law that gives individuals control over their personal data and sets strict rules for how organizations collect, store, and process that data.
Key term
Security
Security in IT is the practice of protecting systems, networks, and data from unauthorized access, damage, or theft.
About these practice questions
One of 829 original GCDL practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This GCDL practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the GCDL exam.