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
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Linux Foundation HFCP Exam - Topic 3 Question 27 Discussion

What is the advantage of using state-based endorsement policy over a chaincode or collection level endorsement policy?
A) It provides a way to set endorsement policy on a global Hyperledger Fabric farm level with one configuration
B) It can be used without complex configuration transactions, only a JSON configuration file is needed.
C) It provides fine-tuned endorsement policy on key level, update is possible without chaincode update
D) It provides a way to set endorsement policy for multiply keys with one chaincode configuration update.

Linux Foundation HFCP Exam - Topic 3 Question 27 Discussion

Actual exam question for Linux Foundation's HFCP exam
Question #: 27
Topic #: 3
[All HFCP Questions]

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

Show Suggested Answer Hide Answer
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 .


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

Limited Time Offer

25%

Off

Get Premium HFCP Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Lorrie
10 months ago
C is interesting, but how fine-tuned can it really get?
upvoted 0 times
...
Jamie
10 months ago
D makes sense, managing multiple keys in one go is efficient.
upvoted 0 times
...
Charlena
10 months ago
Wait, can you really update policies without changing the chaincode? Sounds too good to be true!
upvoted 0 times
...
Curt
10 months ago
I disagree, A seems more beneficial for global setups.
upvoted 0 times
...
Tamera
11 months ago
I think option B is spot on! Simple JSON config is a win.
upvoted 0 times
...
Artie
11 months 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.
upvoted 0 times
...
Peggie
11 months 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.
upvoted 0 times
...
Peggie
11 months 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.
upvoted 0 times
...
Pete
11 months 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.
upvoted 0 times
...
Anika
11 months 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.
upvoted 0 times
...
Erick
11 months 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.
upvoted 0 times
...
Ayesha
11 months 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.
upvoted 0 times
...
Coletta
12 months 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.
upvoted 0 times
...
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.
upvoted 0 times
...
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.
upvoted 0 times
Norah
1 year ago
User 3: I think having the flexibility to set endorsement policy on a key level without updating the chaincode is really beneficial.
upvoted 0 times
...
Norah
1 year ago
User 2: I agree, but for my use case, I prefer the simplicity of just using a JSON configuration file for endorsement policy.
upvoted 0 times
...
Danilo
1 year ago
User 1: Option D is useful for scenarios where you need to update the endorsement policy for multiple keys at once.
upvoted 0 times
...
...
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.
upvoted 0 times
...
Tamra
1 year 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.
upvoted 0 times
Samira
1 year ago
User 3: Option A seems like a good way to set endorsement policy on a global level.
upvoted 0 times
...
Sylvie
1 year ago
User 2: I think option C is also useful for fine-tuned endorsement policies.
upvoted 0 times
...
Cherry
1 year ago
User 1: I agree, option B does sound convenient.
upvoted 0 times
...
...
Coletta
1 year 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.
upvoted 0 times
Kerrie
1 year ago
User 3: It makes managing endorsements much easier and more flexible.
upvoted 0 times
...
Latricia
1 year ago
User 2: Yeah, being able to update the endorsement policy at the key level without changing the chaincode is really convenient.
upvoted 0 times
...
Precious
1 year ago
User 1: I agree, option C is definitely the best choice.
upvoted 0 times
...
...
Altha
1 year 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.
upvoted 0 times
...
Ciara
1 year ago
I agree with Raymon. With state-based endorsement policy, you can update the endorsement policy without having to update the chaincode.
upvoted 0 times
...
Raymon
1 year ago
I think the advantage of using state-based endorsement policy is that it allows for fine-tuned endorsement policy on key level.
upvoted 0 times
...

Save Cancel