MENU
To develop smart contracts:
Suggested Answer: B
Get Premium CBDE Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
18 comments · newest first
MA
Mammie
11 months ago
I thought you should always test locally first, not the other way around.
RO
Royal
11 months ago
I think testing with beta customers is crucial before mainnet.
KA
Kati
11 months ago
Wait, why would you deploy to mainnet so quickly? Seems risky!
FR
Fredric
12 months ago
Totally agree, testing on a test-net first makes more sense.
AL
Albina
12 months ago
Starting with a local blockchain is a solid move!
ON
Ona
12 months ago
I’m not sure about C; it feels backwards to test on a test-net before a local simulation. I think that could lead to more issues.
VE
Veronique
1 year ago
I feel like we practiced a question similar to this, and I think B was the answer we chose then too. It just seems safer to test with beta customers first.
PO
Portia
1 year ago
I'm a bit unsure, but I thought starting with a local blockchain was the best way to catch early bugs. Maybe A is right?
GL
Glennis
1 year ago
I remember we discussed the importance of testing on a test-net before going to main-net, so I think option B makes sense.
AN
Annmarie
1 year ago
I think the best approach is to start with the testnet, get feedback from beta customers, and then move to the local in-memory blockchain for more testing. That way, I can make sure the smart contract is working as expected before I even touch the mainnet. Slow and steady wins the race, right?
IS
Isaac
1 year ago
Okay, I've got this. The key is to start with a local in-memory blockchain and unit tests, then move to a testnet to work out any last issues before deploying to the mainnet. That way, I can ensure the smart contract is rock-solid before it goes live. Gotta be thorough, you know?
NO
Noah
1 year ago
Hmm, this is a tricky one. I'm a bit confused about the order of the steps. Should I start with the testnet or the local blockchain? I'll need to review my notes on the development process to make sure I get this right.
EV
Evelynn
1 year ago
I'm feeling pretty confident about this question. I think the best approach is to start with a local in-memory blockchain and unit tests, then move to a testnet before deploying to the mainnet. That way, I can catch any issues early on and make sure the smart contract is working properly.
RO
Rose
1 year ago
Hmm, I'm a bit unsure about this one. The question mentions both language and knowledge requirements, so I'm not sure if Skills-based Routing alone will be enough. Maybe we need to look at the other options as well.
DU
Dustin
1 year ago
I'm a little confused by the wording of this question. I'll need to re-read the choices carefully to make sure I understand what the tool is actually used for.
BR
Britt
1 year ago
Okay, I think I've got this. The alarm statuses are normal, warning, and closure. The last option about insufficient data is probably a distractor.
CH
Charlena
1 year ago
I'm feeling pretty good about option A. The "le 16" qualifier seems to be the most straightforward way to match all the IP prefixes in the specified range. I'm going to go with that as my final answer.
VE
Veronika
1 year ago
The routing process enabled by default on all interfaces seems like a fundamental feature, but I wonder if it actually makes troubleshooting easier in this case.