Decentralized Application (dApp) Architecture Flashcards
7 cards from real Blockchain Technology practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 Decentralized Application (dApp) Architecture flashcards as text
Which is a valid reason to split a dApp into multiple smaller contracts?
Answer: Modularity, upgradeability, and gas limits
Splitting contracts improves modularity and works around per-contract size and gas constraints.
What is the function of a multisig wallet in dApp governance architecture?
Answer: Require multiple approvals for actions
Multisig wallets require several signers to authorize sensitive operations, reducing single-key risk.
Why is reentrancy a key concern in dApp contract design?
Answer: External calls can re-enter before state updates
Reentrancy lets a malicious contract call back in before balances update, draining funds.
What does the checks-effects-interactions pattern protect against?
Answer: Reentrancy and inconsistent state
Performing checks and state changes before external interactions prevents reentrancy exploits.
In a dApp, what is the benefit of using events plus an indexer over polling contract storage?
Answer: Efficient, queryable history without heavy RPC load
Indexed events give fast, rich queries while polling storage is slow and RPC-intensive.
Which statement about smart contract immutability is true for dApp design?
Answer: Deployed bytecode generally cannot be changed
Once deployed, contract code is fixed, which is why upgrade patterns use proxies.
What is a 'view' function's role in dApp frontend interaction?
Answer: Read state without a gas-costing transaction
View/pure functions read data via a local call (eth_call) without sending a state-changing transaction.