Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Blockchain Exam CBSA Topic 3 Question 61 Discussion

Actual exam question for Blockchain's BTA Certified Blockchain Solution Architect exam
Question #: 61
Topic #: 3
[All BTA Certified Blockchain Solution Architect Questions]

If a hard fork occurs on a public blockchain software and 20 running nodes choose not to update, what can be said about those 20 nodes?

Show Suggested Answer Hide Answer
Suggested Answer: A

Contribute your Thoughts:

Lynelle
1 days ago
I agree with that, those nodes are essentially on a different network.
upvoted 0 times
...
Felicitas
2 days ago
I think if 20 nodes do not update after a hard fork, they are operating on a different blockchain.
upvoted 0 times
...
Nohemi
24 days ago
Consensus, schmensensus! I just want to know if I can still get my hands on those sweet, sweet blockchain fees. Option C sounds promising to me.
upvoted 0 times
...
Christoper
26 days ago
I'm leaning towards option D - they won't be able to achieve consensus if they're not on the same network as the updated nodes. That's the whole point of a hard fork, right?
upvoted 0 times
...
Tyisha
27 days ago
Oh, I don't know. Option C about them being flagged for removal and unable to collect fees seems a bit harsh. That can't be right, can it?
upvoted 0 times
...
Tonette
28 days ago
I'm not so sure about that. Wouldn't they be considered 'out of compliance' if they don't update? That's what option B is suggesting.
upvoted 0 times
...
Kimberely
1 months ago
Hmm, I think option A is the correct answer. If the nodes don't update, they'll effectively be on a different blockchain network, right? That's what a hard fork is all about.
upvoted 0 times
...
Florinda
1 months ago
This question is tricky! I'm not sure if I fully understand the implications of a hard fork and what it means for the nodes that don't update. I guess we'll have to really think this through.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77