LPI Exam 300-300 Topic 5 Question 15 Discussion

Actual exam question for LPI's 300-300 exam

Question #: 15
Topic #: 5

[All 300-300 Questions]

How is Samba instructed to read its entire configuration from the registry?

ABy starting all Samba processes with the option --regconf.

BBy putting config backend = registry in the [global] section of smb.conf.

CBy starting the regd service in addition to the other Samba services.

DBy replacing private.tdb with a plain text registry file holding the server's configuration.

EBy creating a symbolic link from smb.conf to the .reg file holding the configuration.

Show Suggested Answer

Suggested Answer: B

Configuration Backend: Samba can be configured to read its settings from various backends, including the Windows registry.

Setting the Backend:

Adding config backend = registry in the [global] section of smb.conf instructs Samba to use the registry for its configuration.

Implementation Steps:

Open the smb.conf file.

Add the line config backend = registry under the [global] section.

Restart the Samba services to apply the changes.

Samba Wiki - Configuration

by Gearldine at Sep 15, 2024, 05:29 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Wendell

2 months ago

Haha, I bet the developers were having a field day with these options. 'Let's see how many weird ways we can configure Samba!'

upvoted 0 times

...

Martha

2 months ago

E? Really? A symlink to a .reg file? That sounds like a hack, not a proper solution.

upvoted 0 times

Mariann

1 months ago

E? Really? A symlink to a .reg file? That sounds like a hack, not a proper solution.

upvoted 0 times

...

Martina

2 months ago

B) By putting config backend = registry in the [global] section of smb.conf.

upvoted 0 times

...

Alaine

2 months ago

A) By starting all Samba processes with the option --regconf.

upvoted 0 times

...

Eun

2 months ago

I'm not sure, but I think option A) By starting all Samba processes with the option --regconf could also work. What do you guys think?

upvoted 0 times

...

Wei

2 months ago

D is the way to go! Replacing that binary database with a plain text registry file is the way to go for easy configuration.

upvoted 0 times

Felicidad

1 months ago

True, but creating a symbolic link from smb.conf to the .reg file could also work well.

upvoted 0 times

...

Sheron

1 months ago

I think putting config backend = registry in the [global] section of smb.conf is the most straightforward.

upvoted 0 times

...

Goldie

2 months ago

But wouldn't starting all Samba processes with the option --regconf be easier?

upvoted 0 times

...

Matthew

2 months ago

I agree, using a plain text registry file makes configuration much simpler.

upvoted 0 times

...

Lashon

3 months ago

I agree with Pearlie, that seems like the most logical way to instruct Samba to read its configuration from the registry.

upvoted 0 times

...

Latonia

3 months ago

Option B makes the most sense to me. Samba should have a configuration backend setting to use the registry instead of the default config file.

upvoted 0 times

Louisa

2 months ago

Definitely, using the registry as the configuration backend can be more efficient for managing Samba settings.

upvoted 0 times

...

Solange

2 months ago

That makes sense, it's important to specify the configuration backend for Samba to use the registry.

upvoted 0 times

...

Queen

2 months ago

Yes, putting config backend = registry in the [global] section of smb.conf is the way to go.

upvoted 0 times

...

Elbert

2 months ago

I think option B is the correct way to instruct Samba to read its configuration from the registry.

upvoted 0 times

...

Pearlie

3 months ago

That's correct, it tells Samba to read its configuration from the registry.

upvoted 0 times

...

Twana

3 months ago

I agree, setting config backend = registry in the [global] section seems like the right way to go.

upvoted 0 times

...

Pearlie

3 months ago

I think the answer is B) By putting config backend = registry in the [global] section of smb.conf.

upvoted 0 times

...