Financial Services Perspective Quiz
This quiz tests your understanding of the consortium choice, privacy, key management, and review-board issues.
Multiple Choice Questions
- What criterion is offered for judging whether a problem needs blockchain?
- A) Whether the data volume is large enough
- B) Whether you can write "why this problem must have no arbiter" in one sentence — if not, compare alternatives first
- C) Whether there are five or more participating institutions
- D) Whether real-time processing is required
Show Answer
Answer: B) Whether you can write "why this problem must have no arbiter" in one sentence — if not, compare alternatives first
Explanation: The chapter uses "agreeing without a trusted arbiter" as a starting question for comparing blockchain's costs and benefits. If one organization controls the data or the parties trust an arbiter, start with database/audit-log alternatives and compare the actual independent-verification and governance requirements. Do not infer universally zero value from institution count. When tamper detection is the main requirement, signed append-only logs, hash chains or WORM storage may satisfy it with simpler operations.
- What must be assessed before claiming that a network choice satisfies financial compliance?
- A) Throughput and fees
- B) Assess counterparty identification and data-location obligations for the actual activity and jurisdiction
- C) Governance and error handling
- D) Development convenience and hiring
Show Answer
Answer: B) Assess counterparty identification and data-location obligations for the actual activity and jurisdiction
Explanation: Public and permissioned systems can use different controls. Consortium membership alone proves neither KYC/AML nor privacy compliance; obtain the appropriate legal/compliance assessment.
- What substantive value remains when choosing a consortium chain, and why should review define it that way?
- A) Censorship resistance — a value regulators also recognize
- B) Reduced inter-institution reconciliation cost — because writing "decentralized, operating without trust" collapses under the question "then who controls membership?"
- C) Permissionless participation — because it guarantees scalability
- D) No arbiter needed — because no operating party remains
Show Answer
Answer: B) Reduced inter-institution reconciliation cost — because writing "decentralized, operating without trust" collapses under the question "then who controls membership?"
Explanation: Going consortium removes much of the public chain's value — censorship resistance, permissionless participation, no arbiter needed — because a party controls membership and that party is effectively an arbiter. What remains substantively is "making institutions see the same data so reconciliation work disappears," which is real value. Defining value that way from the start is defensible in review.
- What is the particular risk of storing data encrypted on a blockchain?
- A) Performance degradation from encryption
- B) Historical ciphertext copies may persist, and a key compromise can expose records encrypted under that key
- C) Encrypted data is excluded from consensus
- D) The encryption key is stored on the chain alongside
Show Answer
Answer: B) Historical ciphertext copies may persist, and a key compromise can expose records encrypted under that key
Explanation: Re-encrypting new records does not erase old copies. Permissioned private-data purge has different semantics; validate retention, key lifecycle and legal requirements rather than asserting every chain has identical deletion behavior.
- Where does PoS validator key management clash with ordinary HA wisdom?
- A) Keys must be replicated to several regions
- B) Uncoordinated signers can produce conflicting slashable messages for the same validator
- C) HSMs do not support multiple instances
- D) Key rotation requires downtime
Show Answer
Answer: B) Uncoordinated signers can produce conflicting slashable messages for the same validator
Explanation: Use fencing and preserved slashing-protection history. A deliberately distributed signer needs proven coordination; duplicated identical signatures are not automatically equivalent to a slashable conflict.
- What kind of answer does the review question "how do you reverse an incorrect transaction" require?
- A) Present a technical procedure for rolling back the chain
- B) Process, not technology — keep the original and issue a compensating transaction to correct the outcome, the same concept as a reversing entry in accounting
- C) The consortium operator deletes the block
- D) Explain that immutability is a strength so nothing needs reversing
Show Answer
Answer: B) Process, not technology — keep the original and issue a compensating transaction to correct the outcome, the same concept as a reversing entry in accounting
Explanation: The immutability marketed as a strength is a problem in financial operations. Incorrect transactions, mistaken transfers, and system errors happen, and institutions have obligations and procedures to correct them. The answer is issuing a compensating transaction rather than "rolling back the chain," and review needs that procedure and its approval authority documented. This also connects to the absence of atomicity when integrating with existing infrastructure (Saga/outbox patterns).
- Which two items are identified as most underprepared in financial-services review?
- A) Performance measurement and cost estimation
- B) Error correction procedures and an exit strategy
- C) Network configuration and firewall policy
- D) Development staffing and training plans
Show Answer
Answer: B) Error correction procedures and an exit strategy
Explanation: For error correction, "it cannot be reversed" becomes a weakness in review, and the answer must be prepared as process (compensating transactions) rather than technology. The exit strategy is almost never prepared — on consortium dissolution, member withdrawal, or system shutdown, financial data carries retention obligations so "we turned off the chain" is not the end. The ledger's export format, retention party, withdrawing-member data handling, and record access must be in the consortium agreement, with the technical design supporting it.
- What is the most substantive difficulty integrating with existing financial infrastructure, and the direction of response?
- A) The throughput gap — solved by adding chain nodes
- B) The absence of atomicity — an existing DB transaction and a chain transaction cannot be bound into one atomic unit, so eventual-consistency approaches like Saga/outbox must go into the design early
- C) Time synchronization — solved with NTP configuration
- D) Protocol differences — solved with a gateway translation
Show Answer
Answer: B) The absence of atomicity — an existing DB transaction and a chain transaction cannot be bound into one atomic unit, so eventual-consistency approaches like Saga/outbox must go into the design early
Explanation: A failure between writing to the DB and submitting the chain transaction creates an inconsistency, and they cannot be bound in a distributed transaction. Saga or outbox patterns are needed, connected to the compensating-transaction procedure. Being an architecture decision, it must be addressed early in design — bolted on later, data consistency problems surface in production. Adding full-node replicas does not automatically increase base-chain write/consensus capacity, although it can increase aggregate RPC/read capacity and availability.
- Which stage must come before technical validation in a realistic adoption path?
- A) PoC and pilot
- B) Agree participant roles, governance and the measurable benefit compared with simpler alternatives
- C) Infrastructure sizing and cost estimation
- D) Building the monitoring stack
Show Answer
Answer: B) Agree participant roles, governance and the measurable benefit compared with simpler alternatives
Explanation: Do not assert that one institutional arrangement has universally zero value or automatic compliance. The review concerns explicit requirements, trust assumptions and operational responsibilities.