Linux Foundation Exam HFCP Topic 3 Question 15 Discussion

Actual exam question for Linux Foundation's HFCP exam

Question #: 15
Topic #: 3

[All HFCP Questions]

What are the standard possibilities to configure parameters of a component (peer, orderer) in Hyperledger Fabric?

ALocal Linux config files and kubernetes configuration in etcd.

BGlobal configuration database for storing all relevant parameters.

CYaml config files, environment variables, flags on CLI commands.

DIndividual configuration database for each organization.

Show Suggested Answer

Suggested Answer: C

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 .

by Nidia at Aug 08, 2024, 08:10 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Rickie

3 months ago

I think option C makes the most sense, as it allows for flexibility and ease of configuration using Yaml files, environment variables, and CLI commands.

upvoted 0 times

...

Sabina

3 months ago

I believe option A is also a valid way to configure parameters, using local Linux config files and kubernetes configuration in etcd.

upvoted 0 times

...

Marcos

3 months ago

I agree with Yvonne, those options seem to be the most common ways to configure parameters in Hyperledger Fabric.

upvoted 0 times

...

Yvonne

3 months ago

I think the standard possibilities are Yaml config files, environment variables, flags on CLI commands.

upvoted 0 times

...

Gail

3 months ago

Ah, the age-old debate: local config or global database? Personally, I'm a fan of the Swiss Army knife approach in C. More tools, more fun!

upvoted 0 times

...

Melvin

3 months ago

Individual config databases for each org? Sounds like a recipe for chaos. I'm with Twana on this one - keep it simple with C.

upvoted 0 times

Tesha

2 months ago

Definitely, having individual config databases for each organization could get messy.

upvoted 0 times

...

Polly

2 months ago

Yeah, I agree. Using yaml config files and environment variables is much simpler.

upvoted 0 times

...

Willetta

3 months ago

I prefer individual configuration databases for each organization, it provides more control and customization.

upvoted 0 times

...

Ranee

4 months ago

I believe using a global configuration database could also be a good option for storing all relevant parameters.

upvoted 0 times

...

Angelo

4 months ago

I agree with Vinnie, those options make sense for configuring parameters.

upvoted 0 times

...

Christene

4 months ago

Kubernetes config in etcd, eh? Sounds like a lot of overhead just to set some parameters. I'll stick with the simpler approach in C.

upvoted 0 times

...

Twana

4 months ago

Global config database? Nah, that's too centralized. Gotta go with the options that let us manage our own stuff.

upvoted 0 times

Alyce

3 months ago

A) Local Linux config files and kubernetes configuration in etcd.

upvoted 0 times

...

Alyssa

4 months ago

C) Yaml config files, environment variables, flags on CLI commands.

upvoted 0 times

...

Vinnie

4 months ago

I think the standard possibilities are Yaml config files, environment variables, flags on CLI commands.

upvoted 0 times

...

Ariel

4 months ago

Hmm, looks like C is the way to go. Yaml configs, environment vars, and CLI flags - that's the flexibility we need!

upvoted 0 times

Mendy

3 months ago

CLI flags are handy for quick adjustments.

upvoted 0 times

...

Mattie

3 months ago

Environment variables and CLI flags give us more control over configuration.

upvoted 0 times

...

Lillian

3 months ago

Yaml configs make it easy to manage parameters.

upvoted 0 times

...

Alfreda

3 months ago

Environment variables are great for customizing configurations.

upvoted 0 times

...

Alaine

4 months ago

Yaml configs make it easy to manage settings.

upvoted 0 times

...

Ronnie

4 months ago

I agree, C seems like the most flexible option.

upvoted 0 times

...

Carol

4 months ago

I agree, C seems like the most flexible option.

upvoted 0 times

...