Building User-Friendly dApp Interfaces BDC Practice Questions (Page 1)

Questions 1–5

1. 1foundation · easy

   What is a common approach to simplify wallet setup for non-technical users in a dApp?

   • AAutomatically create a wallet for the user and store the private key on the dApp's server.
   • BProvide a step-by-step guide that explains how to install a wallet extension and create an account.
   • CSkip wallet setup entirely and allow users to interact with the blockchain without authentication.
   • DRequire users to write down their private key and enter it into the dApp to log in.
   Reveal Solution Discussion Select an answer first
2. 2application · medium

   A dApp team is designing an onboarding flow for non-technical users. The flow must help users understand the importance of their seed phrase without overwhelming them. Which approach is best?

   • ASkip the seed phrase backup and rely on social login to recover the wallet.
   • BOffer to store the seed phrase in the dApp's cloud storage for the user.
   • CShow the seed phrase once and ask the user to confirm they have written it down.
   • DUse a step-by-step wizard that explains each part of the seed phrase and asks the user to re-enter a few randomly selected words to confirm.
   Reveal Solution Discussion Select an answer first
4. 3application · medium

   A dApp for a charity allows donors to contribute ETH. During usability testing, non-technical users report confusion after clicking 'Donate' because the MetaMask popup appears without explanation, and they are unsure whether the transaction was sent. Which two improvements best address this feedback?

   • AShow a toast notification that says 'Transaction sent' immediately after the user clicks Donate, before MetaMask approval.
   • BAdd a pre-transaction modal explaining the next step and a post-transaction success screen with a link to the transaction hash.
   • CAutomatically switch the user's MetaMask network to the mainnet before the transaction and disable the popup.
   • DUse a hardware wallet instead of MetaMask to eliminate the popup and provide on-device confirmation.
   Reveal Solution Discussion Select an answer first
5. 4application · medium

   A dApp submits a transaction to the user's MetaMask wallet. After the user approves it, the UI shows a spinner that never resolves, even though the transaction is later mined. What is the most likely cause and the best fix?

   • AThe user's MetaMask is set to a private network; instruct the user to switch to the mainnet.
   • BThe dApp is using an outdated Web3 library; upgrade to the latest version of ethers.js or web3.js.
   • CThe dApp is polling the wrong network; switch the UI to poll the network the wallet is connected to.
   • DThe dApp is not listening for the transaction receipt; implement a receipt listener or polling loop that updates the UI when the transaction is confirmed.
   Reveal Solution Discussion Select an answer first
6. 5expert · hard

   A dApp for a global remittance service is targeting users in regions with unreliable internet connections. The team wants to simplify onboarding and key management, but also ensure the dApp works on low-end mobile devices. Which approach best meets these constraints?

   • ARequire users to install a full desktop node to ensure reliability.
   • BUse a custodial wallet service that handles all transactions on the server, so users do not need to manage keys.
   • CUse a lightweight web interface with a social login that creates a non-custodial wallet, and cache the dApp assets for offline access to the interface.
   • DBuild a native mobile app that requires a constant internet connection and stores private keys on the device.
   Reveal Solution Discussion Select an answer first