Multiple Choice
Consider the following scenario: A solo app developer wants to create their own cryptocurrency and build a blockchain based that allows users to buy and sell second-hand items with that cryptocurrency from each other. Before the transaction is considered complete, the purchaser must put the funds in an escrow service and the sender must enter the courier tracking number into that same escrow. Time is of the essence and this developer doesn't want to worry about networking of infrastructure. This app must be fully autonomous or "decentralized". Which architecture would best solve the product need?
A) Ethereum for token creation and escrow service; User-facing features built with web technologies and deployed through IPFS
B) Ethereum for token creation; Traditional multitier API and database for escrow service; User-facing features built in web technologies then minified unto a String and deployed to an Ethereum Smart Contract
C) Hyperledger Fabric for the escrow service and token creation using chaincode; User-facing features built with Hyperledger Composer
D) The product cannot be built. Fully decentralized apps are not yet possible for user interface
Correct Answer:

Verified
Correct Answer:
Verified
Q49: The fabric framework is implemented on _programming
Q50: Transactions can only be added to a
Q51: The _of the tree is the topmost
Q52: Bitcoin uses what proof of work consensus
Q53: Which one of the following is true
Q55: What is the difference in using Go-Ethereum
Q56: What are two challenges with using a
Q57: What are some likely repercussions that could
Q58: In Ethereum a block contains two very
Q59: The "Nothing-at-Stake" problem that could be realized