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

Linux Foundation HFCP Exam - Topic 3 Question 27 Discussion

Posted by Dyan on Jan 23, 2025 at 08:45 PM

What is the advantage of using state-based endorsement policy over a chaincode or collection level endorsement policy?

Suggested Answer: A

In Hyperledger Fabric, a range query with a start and end key is a type of query that searches for all ledger entries whose keys fall within the specified range defined by the startKey and endKey. This is used, for example, to retrieve a subset of assets from the ledger based on their key values, effectively iterating over a specified range .


Get Premium HFCP Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test
30 comments · newest first
LO
Lorrie 11 months ago
C is interesting, but how fine-tuned can it really get?
JA
Jamie 11 months ago
D makes sense, managing multiple keys in one go is efficient.
CH
Charlena 12 months ago
Wait, can you really update policies without changing the chaincode? Sounds too good to be true!
CU
Curt 12 months ago
I disagree, A seems more beneficial for global setups.
TA
Tamera 1 year ago
I think option B is spot on! Simple JSON config is a win.
AR
Artie 1 year ago
I thought the state-based policy was easier to manage because it uses a JSON file, but I’m not confident if that’s the best answer here.
PE
Peggie 1 year ago
I feel like option D might be correct since it mentions multiple keys, but I can't recall if that's the main advantage over the others.
PE
Peggie 1 year ago
I remember practicing a question about endorsement policies, and I think the advantage is that it can be updated without needing to change the chaincode itself.
PE
Pete 1 year ago
I think the state-based endorsement policy allows for more granular control, but I'm not entirely sure how it compares to chaincode policies.
AN
Anika 1 year ago
Ah yes, I remember this from the Fabric documentation. State-based endorsement policy also gives you more flexibility to update the policy without having to redeploy the chaincode. That could be a big time-saver compared to the other options.
ER
Erick 1 year ago
Okay, I think I've got this. The key advantage of state-based endorsement policy is that it allows you to set the policy at a global level, without needing to update the chaincode. That could be really useful for managing endorsement requirements across multiple keys or collections.
AY
Ayesha 1 year ago
Hmm, I'm a bit confused by the wording of this question. I'll need to review my notes on endorsement policies to make sure I understand the distinctions between state-based, chaincode-level, and collection-level policies.
CO
Coletta 1 year ago
This question seems to be asking about the advantages of using state-based endorsement policy over other types of endorsement policies. I'll need to think carefully about the key differences between these approaches.
MI
Michell 1 year ago
Wait, so we're endorsing policies now? I thought we were just supposed to be following them. This is getting too political for me.
MI
Micaela 1 year ago
Option D is interesting, but I'm not sure I need to set the endorsement policy for multiple keys with one chaincode configuration update. Seems a bit overkill for my use case.
NO
Norah 1 year ago
↳ replying to Micaela
User 3: I think having the flexibility to set endorsement policy on a key level without updating the chaincode is really beneficial.
NO
Norah 1 year ago
↳ replying to Micaela
User 2: I agree, but for my use case, I prefer the simplicity of just using a JSON configuration file for endorsement policy.
DA
Danilo 1 year ago
↳ replying to Micaela
User 1: Option D is useful for scenarios where you need to update the endorsement policy for multiple keys at once.
TY
Tyisha 1 year ago
I like the idea of setting the endorsement policy on a global Hyperledger Fabric farm level, as mentioned in option A. That could be a real time-saver.
TA
Tamra 2 years ago
I'm leaning towards option B. The ability to use a simple JSON configuration file instead of complex transactions is really appealing to me.
SA
Samira 1 year ago
↳ replying to Tamra
User 3: Option A seems like a good way to set endorsement policy on a global level.
SY
Sylvie 1 year ago
↳ replying to Tamra
User 2: I think option C is also useful for fine-tuned endorsement policies.
CH
Cherry 1 year ago
↳ replying to Tamra
User 1: I agree, option B does sound convenient.
CO
Coletta 2 years ago
Option C seems like the best choice here. Being able to fine-tune the endorsement policy at the key level without having to update the chaincode is a great advantage.
KE
Kerrie 1 year ago
↳ replying to Coletta
User 3: It makes managing endorsements much easier and more flexible.
LA
Latricia 1 year ago
↳ replying to Coletta
User 2: Yeah, being able to update the endorsement policy at the key level without changing the chaincode is really convenient.
PR
Precious 1 year ago
↳ replying to Coletta
User 1: I agree, option C is definitely the best choice.
AL
Altha 2 years ago
I prefer using state-based endorsement policy because it provides a way to set endorsement policy for multiple keys with just one chaincode configuration update.
CI
Ciara 2 years ago
I agree with Raymon. With state-based endorsement policy, you can update the endorsement policy without having to update the chaincode.
RA
Raymon 2 years ago
I think the advantage of using state-based endorsement policy is that it allows for fine-tuned endorsement policy on key level.
0/2000 characters

Save Cancel