Linux Foundation HFCP Exam - Topic 1 Question 9 Discussion

Actual exam question for Linux Foundation's HFCP exam

Question #: 9
Topic #: 1

[All HFCP Questions]

When building a test network, how many nodes are adequate for an Ordering Service?

AThere is no set number of nodes required for an Ordering Service.

BThree ordering nodes are needed for a test Ordering Service.

COne ordering nodes is sufficient for an Ordering Service.

DOrdering Service nodes are optional in a test network.

Show Suggested Answer

Suggested Answer: D

In Hyperledger Fabric, to enable CouchDB as the state database, the stateDatabase configuration option in the core.yaml file must be changed from goleveldb to CouchDB. This change directs the peer to use CouchDB instead of the default LevelDB for storing the world state, which can then be queried using rich queries and provides additional features like indexing.

by Matt at May 22, 2024, 02:12 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Vallie

4 months ago

I heard three is the sweet spot for reliability.

upvoted 0 times

...

Jamal

4 months ago

Definitely no set number, it depends on your needs.

upvoted 0 times

...

Lizette

4 months ago

Wait, are ordering nodes really optional? That seems risky!

upvoted 0 times

...

Paul

4 months ago

I disagree, one node can work for testing purposes.

upvoted 0 times

...

Han

5 months ago

I think three nodes are a good standard for redundancy.

upvoted 0 times

...

Ronnie

5 months ago

I vaguely recall that ordering nodes are important, but I’m not sure if they’re optional in a test network. That seems a bit confusing.

upvoted 0 times

...

Markus

5 months ago

I think I came across a similar question where they emphasized having at least three nodes for reliability in an Ordering Service.

upvoted 0 times

...

Truman

5 months ago

I’m a bit unsure, but I feel like one node could work for testing purposes, right? It seems like it could be enough for a simple setup.

upvoted 0 times

...

Mozell

5 months ago

I remember reading that there's no strict rule for the number of nodes, but I think three might be a good practice for redundancy.

upvoted 0 times

...

Dean

5 months ago

Based on my understanding, there is no set number of ordering nodes required for a test network. The Ordering Service is responsible for ordering transactions, so the number of nodes you need will depend on factors like the expected transaction volume and your availability requirements.

upvoted 0 times

...

Malcolm

5 months ago

The question mentions a "test network", so I'm guessing the number of ordering nodes required might be different than for a production network. I'll try to think through the tradeoffs between redundancy, performance, and cost for a test setup.

upvoted 0 times

...

Anna

5 months ago

I'm not sure about the exact number of nodes required for an Ordering Service in a test network. I'll need to review the documentation on Hyperledger Fabric to make sure I understand the requirements.

upvoted 0 times

...

Taryn

6 months ago

I think option A is the correct answer. The question specifically asks about a "test network", and in a test environment, the number of ordering nodes can be flexible based on your needs and constraints. I'll make a note to explain my reasoning in case I need to justify my answer.

upvoted 0 times

...

Theola

6 months ago

Hmm, the key here is that the Potential Name object needs to have a master-detail relationship with the Product Development object. So we'll need to find a way to either assign the missing relationships or remove the records without them.

upvoted 0 times

...

Hubert

6 months ago

I've got a good feeling about this one. The key is to focus on the XML structure and how the "bold" tag should be handled. I think I know the right approach to get the correct answer.

upvoted 0 times

...