MENU
When considering smart contracts and the blockchain it's good:
Suggested Answer: C
Get Premium CBDE Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
44 comments · newest first
IN
India
11 months ago
Surprised anyone would choose A. That sounds risky!
JA
Janine
11 months ago
Totally agree with B! Easier to manage and test that way.
ME
Melinda
11 months ago
C is interesting, but can we really trust traditional systems?
MI
Miesha
12 months ago
A sounds like a nightmare. Complexity isn't always better.
JA
Jacquline
12 months ago
I think B makes the most sense. Keep it simple!
DI
Dianne
12 months ago
I recall a debate in class about the trade-offs of complexity versus maintainability, and I lean towards option B for simplicity in smart contracts.
CE
Celestina
1 year ago
I feel like option C could be a good compromise, focusing on Ether transfers while keeping other logic off-chain. But I'm not completely confident about that.
RO
Roslyn
1 year ago
I think we practiced a question similar to this, and the answer was about only moving essential parts to the blockchain. It makes sense for readability and testing.
DE
Desirae
1 year ago
I remember discussing how moving everything to the blockchain could lead to unnecessary complexity, but I'm not sure if that's always a bad thing.
SH
Shenika
1 year ago
I'm pretty confident that Option B is the way to go. Minimizing the blockchain footprint while still taking advantage of its capabilities is usually the best approach.
BL
Blair
1 year ago
Option C makes the most sense to me. Keeping the Ether transfers on the blockchain while leaving the other logic off seems like a good way to get the benefits without the complexity.
AN
Antonio
1 year ago
Hmm, this is a tricky one. I'm not sure if I fully understand the tradeoffs between the different options. I'll need to think this through carefully before deciding.
MO
Mozell
1 year ago
I think the key here is to balance the benefits of the blockchain with the complexity it can introduce. Option B seems like the best approach - only move the essential parts to the blockchain and keep the rest in traditional systems.
AD
Adela
1 year ago
Okay, let me think this through step-by-step. The key seems to be preventing incorrect information from populating the FDB of VPLS 1. I'll need to consider the options and choose the one that best addresses that.
NI
Nieves
1 year ago
Hmm, this looks like a tricky networking question. I'll need to carefully read through the options and think about the Exadata X9M-2 Database Server's specifications.
CU
Curt
1 year ago
This seems pretty straightforward. I'd just grab the SSID from the return_val data and pass it directly to the send_to_application function. Shouldn't take more than a few lines of code to get this done.
AU
Audry
1 year ago
B all the way. I don't want to be the one trying to debug a blockchain-powered grocery list, you know?
EA
Earleen
1 year ago
Daron: Definitely, debugging a blockchain-powered grocery list does not sound like fun.
DA
Daron
1 year ago
User 2: Yeah, it's important to avoid unnecessary complexity when it comes to smart contracts.
DE
Denny
1 year ago
User 1: I agree, keeping it simple with just the necessary parts on the blockchain makes sense.
VE
Vernice
1 year ago
Alright, who's the comedian that suggested option A? That's just asking for trouble, like trying to fit a square peg in a round hole.
DA
Dan
1 year ago
Loise: Definitely, we don't want to overcomplicate things by moving everything to the blockchain.
LO
Loise
1 year ago
User 2: I agree, keeping it simple and only using the blockchain when necessary makes sense.
GA
Gary
1 year ago
User 1: Option B seems like the most practical approach.
FA
Fannie
2 years ago
Whoa, option A? Are we trying to create a blockchain monster here? No thank you, I'll take B and keep things simple.
MA
Marti
1 year ago
Herminia: Exactly, no need to complicate things by moving everything onto the blockchain.
HE
Herminia
1 year ago
User 2: Yeah, keeping it simple with just the necessary parts on the blockchain makes sense.
MA
Malinda
1 year ago
User 1: I agree, option B seems more practical and less overwhelming.
LA
Lashaunda
2 years ago
C seems like the sweet spot to me. Keep the Ether transfers on the blockchain, but let the rest live in a traditional system. Best of both worlds!
FR
Francisca
1 year ago
True, having a balance between security and simplicity is key.
GR
Gracia
1 year ago
It could be, but it might also make the smart contracts more complex and harder to maintain.
LE
Lenita
1 year ago
But wouldn't it be more secure to have everything on the same system?
FR
Frederica
1 year ago
I agree, keeping only the Ether transfers on the blockchain makes sense.
YO
Yoko
2 years ago
Definitely B. Why complicate things when you can just put the critical stuff on the blockchain and keep the rest in a regular database? Efficiency, people!
CA
Carol
1 year ago
I think it's important to carefully consider what really needs to be on the blockchain to avoid unnecessary complexity.
KE
Keith
1 year ago
I agree, keeping it simple is key. Plus, it makes it easier for others to understand the smart contract.
BE
Beth
2 years ago
I think option B is the way to go. Putting everything on the blockchain just sounds like a headache waiting to happen.
YE
Yen
1 year ago
Yeah, option B seems like the most practical choice for smart contracts.
IR
Ira
1 year ago
Option C seems like a good compromise, focusing on value-transfer.
DE
Delmy
1 year ago
I think option A could work too, but it might be too much to handle.
MA
Marica
2 years ago
I agree, keeping it simple with option B makes sense.
WI
William
2 years ago
I see both sides, but I lean towards option C. Keeping only Ether transfers on the blockchain seems like a good balance.
EN
Ena
2 years ago
I disagree, I believe option A is better. Having everything on the same system makes it easier to maintain.
SH
Shala
2 years ago
I think option B is the best approach. We shouldn't overcrowd the blockchain with unnecessary logic.