- A
Giving the fintech startup direct database access to the bank's customer records system for maximum data sharing
Why wrong: Direct database access to a bank's core systems is a severe security and compliance risk. APIs provide governed, audited, controlled access without exposing the underlying data store.
- B
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
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.
- C
The bank should acquire the fintech startup and consolidate all technology onto the bank's legacy infrastructure
Why wrong: Acquisition and consolidation are business strategy options, but they would eliminate the fintech's innovation advantage by forcing it onto legacy bank infrastructure. The partnership model preserves the fintech's agility.
- D
The fintech should build all required banking infrastructure independently to avoid dependency on the bank's legacy systems
Why wrong: Building banking infrastructure independently would require the fintech to obtain banking licenses, build compliance systems, and manage regulated operations — eliminating the value of the partnership. The partnership exists precisely to avoid this.
Quick Answer
The answer is an API-first Open Banking architecture. This pattern is correct because it enables the bank to expose regulated capabilities like account information, payment initiation, and KYC verification through managed, secure APIs, allowing the fintech to build innovative digital experiences on top without direct access to core banking systems. On the Google Cloud Digital Leader exam, this tests your understanding of how cloud-native API management supports secure, compliant partnerships under frameworks like PSD2, often appearing in scenario-based questions about bank-fintech collaboration. A common trap is choosing a simple microservices or hybrid cloud pattern, but the key distinction is the explicit exposure of regulated services through governed APIs. Remember the mnemonic "BANK" — Build APIs, No direct access, Keep compliance.
Cloud Digital Leader Why cloud technology is transforming business Practice Question
This GCDL practice question tests your understanding of why cloud technology is transforming business. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
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?
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
Option B is correct because 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.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
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 to a bank's core systems is a severe security and compliance risk. APIs provide governed, audited, controlled access without exposing the underlying data store.
- ✓
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.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
The bank should acquire the fintech startup and consolidate all technology onto the bank's legacy infrastructure
Why it's wrong here
Acquisition and consolidation are business strategy options, but they would eliminate the fintech's innovation advantage by forcing it onto legacy bank infrastructure. The partnership model preserves the fintech's agility.
- ✗
The fintech should build all required banking infrastructure independently to avoid dependency on the bank's legacy systems
Why it's wrong here
Building banking infrastructure independently would require the fintech to obtain banking licenses, build compliance systems, and manage regulated operations — eliminating the value of the partnership. The partnership exists precisely to avoid this.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may 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.
Detailed technical explanation
How to think about this question
Under the hood, an API-first Open Banking architecture typically uses OAuth 2.0 for authorization and OpenID Connect for authentication, with APIs defined by standards like the UK Open Banking Specification or Berlin Group XS2A. The bank deploys an API gateway (e.g., Kong, Apigee) to enforce rate limiting, request validation, and audit logging, while the fintech consumes these APIs via RESTful endpoints. A real-world example is the partnership between BBVA and fintechs like Mint, where BBVA exposes account aggregation APIs without sharing direct database access.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Why cloud technology is transforming business — study guide chapter
Learn the concepts, then practise the questions
- →
Why cloud technology is transforming business practice questions
Targeted practice on this topic area only
- →
All GCDL questions
507 questions across all exam domains
- →
Google Cloud Digital Leader study guide
Full concept coverage aligned to exam objectives
- →
GCDL practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related GCDL practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Why cloud technology is transforming business practice questions
Practise GCDL questions linked to Why cloud technology is transforming business.
Fundamental cloud concepts practice questions
Practise GCDL questions linked to Fundamental cloud concepts.
Google Cloud products, services, and solutions practice questions
Practise GCDL questions linked to Google Cloud products, services, and solutions.
Scaling with Google Cloud operations practice questions
Practise GCDL questions linked to Scaling with Google Cloud operations.
Trust and security with Google Cloud practice questions
Practise GCDL questions linked to Trust and security with Google Cloud.
GCDL fundamentals practice questions
Practise GCDL questions linked to GCDL fundamentals.
GCDL scenario practice questions
Practise GCDL questions linked to GCDL scenario.
GCDL troubleshooting practice questions
Practise GCDL questions linked to GCDL troubleshooting.
Practice this exam
Start a free GCDL practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this GCDL question test?
Why cloud technology is transforming business — This question tests Why cloud technology is transforming business — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: 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 — Option B is correct because 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.
What should I do if I get this GCDL question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 11, 2026
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.