MENU
How would a developer iteratively test and develop a smart contract without the overhead of the smart contract lifecycle process for every update?
Suggested Answer: C
Get Premium HFCP Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
In Hyperledger Fabric, the standard possibilities to configure parameters of a component, such as a peer or orderer, include using YAML configuration files, environment variables, and command-line interface (CLI) flags. This approach provides flexibility and allows for detailed control over the parameters that govern the behavior of these components .
37 comments · newest first
CL
Claribel
11 months ago
Wait, can you really run chaincode in development mode? Sounds cool!
VE
Veronika
11 months ago
D seems risky, testing on a production network? Really?
WY
Wynell
12 months ago
C is definitely not efficient, who would do that?
IR
Irma
12 months ago
I disagree, B just sounds like a hassle.
DO
Domingo
1 year ago
A is the way to go, development mode is super handy!
MA
Margarett
1 year ago
Using a production network for testing? That doesn’t sound right. I think it’s important to avoid that to prevent issues.
KA
Kayleigh
1 year ago
Manually updating the smart contract seems risky and time-consuming. I feel like that’s not the best method to iterate quickly.
CE
Cecily
1 year ago
I remember a practice question about testing smart contracts without deploying them each time. I think option A is the right approach.
CH
Charlette
1 year ago
I think running chaincode in development mode sounds familiar, but I'm not entirely sure how it works in practice.
TH
Thomasena
1 year ago
Okay, let me see here. I don't think manually updating the contract code or using a production network are good options. I'm leaning towards the development mode approach, but I want to double-check that.
JO
Johanna
1 year ago
Ah, I think I know the answer to this one. Running chaincode in development mode seems like the most efficient way to test updates without the full deployment process.
HU
Hubert
1 year ago
Hmm, I'm a bit confused by the question. I'll need to review my notes on smart contract testing and deployment to make sure I understand the options properly.
KI
Kirby
1 year ago
This looks like a tricky one. I'll need to think through the smart contract development process carefully to figure out the best approach.
JA
Jacinta
1 year ago
This is a great question that really gets at the heart of smart contract development. I feel pretty confident that running chaincode in development mode is the way to go here, but I'll make sure to review the details before answering.
TA
Tawny
1 year ago
ATDD sounds like the best technique to align the team and the product owner on the expectations. I'll go with that.
LA
Lawana
1 year ago
Okay, I think I've got it. The key is that P really enjoys the work and takes pride in it, which indicates an intrinsic reward. The fact that the organization pays well is just additional context, not the main reward being described. I'm going with A.
RO
Ronny
1 year ago
Running chaincode in development mode? That's the smart(contract) way to do it, if you ask me!
RO
Rodney
2 years ago
Use a Production Network to test and develop Smart Contracts? Now that's just asking for trouble. I'd rather not risk breaking the entire system!
GA
Gail
1 year ago
Use a Production Network to test and develop Smart Contracts? Now that's just asking for trouble. I'd rather not risk breaking the entire system!
LA
Lauran
1 year ago
B) Manually update the Smart Contract code on the network.
NI
Nickole
1 year ago
A) Running chaincode for Smart Contracts in development mode.
MA
Marvel
2 years ago
Deploy the Smart Contract on the network for every update? Um, no thanks. That's way too much work, and I don't have time for all that hassle.
AB
Abraham
1 year ago
A) Running chaincode for Smart Contracts in development mode sounds like a much more efficient option.
KA
Kattie
1 year ago
Deploying the Smart Contract on the network for every update is definitely not the way to go.
LA
Lawrence
1 year ago
B) Manually update the Smart Contract code on the network.
JE
Jenise
1 year ago
A) Running chaincode for Smart Contracts in development mode.
DU
Dudley
2 years ago
Manually updating the Smart Contract code on the network? Yikes, that sounds like a nightmare. I'd rather not have to deal with all that manual labor.
CO
Colette
1 year ago
D) Use a Production Network to test and develop Smart Contracts.
XE
Xenia
1 year ago
A) Running chaincode for Smart Contracts in development mode.
GL
Glendora
1 year ago
B) Manually update the Smart Contract code on the network.
KE
Kenda
1 year ago
A) Running chaincode for Smart Contracts in development mode.
CA
Cammy
2 years ago
Running chaincode for Smart Contracts in development mode? Sounds like the way to go! Less overhead, more flexibility - what's not to love?
XE
Xenia
1 year ago
It definitely makes the development process smoother without the need to redeploy the smart contract every time.
LE
Leota
1 year ago
Yes, running chaincode in development mode allows for quick testing and updates.
TO
Tonja
2 years ago
I prefer option D) Use a Production Network to test and develop Smart Contracts. It provides a more realistic environment for testing.
MO
Mozelle
2 years ago
I agree with Tequila. It allows for iterative testing without the overhead of deploying the Smart Contract for every update.
TE
Tequila
2 years ago
I think option A) Running chaincode for Smart Contracts in development mode would be the best approach.