Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25

- Free Preparation Discussions

LPI 102-500 Exam - Topic 11 Question 92 Discussion

Actual exam question for LPI's 102-500 exam

Question #: 92
Topic #: 11

[All 102-500 Questions]

Which of the following steps prevents a user from obtaining an interactive login session?

ARun the command chsh -s /bin/false with the user name.

BSet the UID for the user to 0.

CRemove the user from the group staff.

DAdd the user to /etc/noaccess.

ECreate a .nologin file in the user's home directory.

Show Suggested Answer

Suggested Answer: D

by Simona at Sep 13, 2024, 07:31 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Yolande

9 months ago

Removing from staff doesn't stop login, that's a myth!

upvoted 0 times

...

Maryann

9 months ago

Wait, can you really do that with chsh?

upvoted 0 times

...

Ammie

9 months ago

No way, B just gives root access!

upvoted 0 times

...

Shawn

10 months ago

I think E could work too, but not sure.

upvoted 0 times

...

Ardella

10 months ago

A is the right answer!

upvoted 0 times

...

Julie

10 months ago

I vaguely recall that removing a user from a group doesn't necessarily prevent login, so I don't think option C is the answer.

upvoted 0 times

...

Jennifer

10 months ago

I practiced a similar question, and I feel like setting the UID to 0 is definitely not the right answer. That grants root access, not restricts it.

upvoted 0 times

...

Lindsey

10 months ago

I'm not entirely sure, but I remember something about .nologin files being used to restrict access. Could it be option E?

upvoted 0 times

...

Juan

11 months ago

I think option A might be correct because changing the shell to /bin/false prevents login, right?

upvoted 0 times

...

Kaitlyn

11 months ago

I think I know the answer to this one. Running the chsh command to set the user's shell to /bin/false should prevent them from getting an interactive login session, right? That seems like the most straightforward way to block login access.

upvoted 0 times

...

Crissy

11 months ago

Okay, I've got a strategy for this. I'll eliminate the options that don't directly address login sessions, like setting the UID or removing the user from a group. Then I'll focus on the options that specifically mention login or access restrictions.

upvoted 0 times

...

Soledad

11 months ago

Hmm, I'm a bit unsure about this one. The options seem to cover different ways of restricting user access, but I'm not sure which one specifically prevents an interactive login session. I'll have to think it through step-by-step.

upvoted 0 times

...

Carey

11 months ago

This looks like a tricky Linux security question. I think the key is to find the option that prevents the user from getting an interactive login session. Let me think this through carefully.

upvoted 0 times

...

Jose

11 months ago

I'm uncertain about the details. I know it's not about stealing data like option D suggests, but I'm not clear on the differences between these answers.

upvoted 0 times

...

Roxanne

1 year ago

I think option A with the chsh command is the way to go. Changing the user's shell to /bin/false should do the trick nicely.

upvoted 0 times

Justine

1 year ago

User3: I think creating a .nologin file in the user's home directory is the best option.

upvoted 0 times

...

Annmarie

1 year ago

User2: But wouldn't adding the user to /etc/noaccess also work?

upvoted 0 times

...

Nguyet

1 year ago

User1: I agree, changing the shell to /bin/false will prevent interactive login.

upvoted 0 times

...

...

Tiara

1 year ago

Haha, option B is a classic 'trap' answer. Who would ever want to set a user's UID to 0? That's just asking for trouble!

upvoted 0 times

Lawrence

1 year ago

True, setting the UID to 0 is definitely a bad idea.

upvoted 0 times

...

Terrilyn

1 year ago

E) Create a .nologin file in the user's home directory.

upvoted 0 times

...

Sheron

1 year ago

A) Run the command chsh -s /bin/false with the user name.

upvoted 0 times

...

...

Brice

1 year ago

I'm not sure about the correct answer, but I'm pretty sure setting the UID to 0 (option B) would make the user an administrator, not prevent them from logging in.

upvoted 0 times

Hana

1 year ago

C) Remove the user from the group staff.

upvoted 0 times

...

Paz

1 year ago

E) Create a .nologin file in the user's home directory.

upvoted 0 times

...

Bernardine

1 year ago

A) Run the command chsh -s /bin/false with the user name.

upvoted 0 times

...

...

Dolores

1 year ago

Option E definitely seems like the right choice to prevent a user from logging in interactively. A .nologin file in the home directory is a classic way to disable logins.

upvoted 0 times

Buck

1 year ago

Option E definitely seems like the right choice to prevent a user from logging in interactively. A .nologin file in the home directory is a classic way to disable logins.

upvoted 0 times

...

Leontine

1 year ago

E) Create a .nologin file in the user's home directory.

upvoted 0 times

...

Meaghan

1 year ago

A) Run the command chsh -s /bin/false with the user name.

upvoted 0 times

...

...

Willow

1 year ago

I'm not sure, but I think A) Run the command chsh -s /bin/false with the user name could also prevent interactive login.

upvoted 0 times

...

Jonell

1 year ago

I agree with Karina. Creating a .nologin file would prevent interactive login.

upvoted 0 times

...

Karina

1 year ago

I think the correct answer is E) Create a .nologin file in the user's home directory.

upvoted 0 times

...