New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25%
- Ends In
00:00:00
Coupon code:
SAVE25
X
Welcome to Pass4Success
Login
|
Sign up
-
Free
Preparation Discussions
Mail Us
support@pass4success.com
Location
US
MENU
Home
Popular vendors
Salesforce
Microsoft
Nutanix
Amazon
Google
CompTIA
SAP
VMware
Fortinet
PeopleCert
Eccouncil
HP
Palo Alto Networks
Adobe
ISC2
ServiceNow
Dell EMC
CheckPoint
Linux Foundation
Discount Deals
New
About
Contact
Login
Sign up
Home
Discussions
LPI Discussions
102-500 Exam - Topic 11 Question 57 Discussion
LPI 102-500 Exam - Topic 11 Question 57 Discussion
Actual exam question for LPI's 102-500 exam
Question #: 57
Topic #: 11
[All 102-500 Questions]
How can a specific user be prevented from scheduling tasks with a i.?
A
By adding the specific user to the /etc/ at,allow file.
B
By adding the specific user to the [deny] section in the /etc./atd.conf file.
C
By adding the specific user to the nojoba group.
D
By adding the specific user to the /etc/at.deny file.
E
By executing the atd --deny [user] command.
Show Suggested Answer
Hide Answer
Suggested Answer:
A, D
by
Felix
at
Jan 05, 2023, 10:54 PM
Limited Time Offer
25%
Off
Get Premium 102-500 Questions as Interactive Web-Based Practice Test or PDF
Contribute your Thoughts:
0
/2000 characters
Submit
Cancel
Luis
4 months ago
Adding to /etc/at.deny is the way to go!
upvoted
0
times
...
Ashlee
4 months ago
I thought the nojoba group was for something else?
upvoted
0
times
...
Noble
4 months ago
Wait, isn't the /etc/at.allow file for allowing users?
upvoted
0
times
...
Margarett
4 months ago
Definitely agree with that!
upvoted
0
times
...
Arminda
4 months ago
You can block users by adding them to /etc/at.deny.
upvoted
0
times
...
Ona
5 months ago
I thought the atd.conf file had something to do with denying users, but I can't remember if it's the [deny] section or not.
upvoted
0
times
...
Bettyann
5 months ago
I practiced a similar question, and I feel like the nojoba group might be related, but I don't think that's the right answer here.
upvoted
0
times
...
Loise
5 months ago
I remember something about the /etc/at.allow file, but I can't recall if that's for allowing or denying users.
upvoted
0
times
...
Rene
5 months ago
I think it might be option D, adding the user to the /etc/at.deny file, but I'm not completely sure.
upvoted
0
times
...
Cyril
5 months ago
Hmm, I'm not totally sure about this. I'll have to review the WSDL documentation again to make sure I understand the use cases for each.
upvoted
0
times
...
Desirae
5 months ago
I'm a bit confused by this question. I'm not sure which option would be the most appropriate. Maybe I should review the course materials again to refresh my understanding of the different presentation strategies.
upvoted
0
times
...
Vi
5 months ago
I think it was definitely packet B from a similar question we did last week, but I'm not completely sure.
upvoted
0
times
...
Donette
9 months ago
As a seasoned sysadmin, I can tell you the answer is D. /etc/at.deny is the way to go. Simple and effective.
upvoted
0
times
...
Leila
9 months ago
Haha, I bet the answer is E. Execute the atd --deny [user] command. That's gotta be the most dramatic way to prevent a user from scheduling tasks!
upvoted
0
times
...
Rodrigo
9 months ago
This is a tricky one. I'm going to go with C, adding the user to the nojoba group. Can't be too careful with task scheduling, you know?
upvoted
0
times
Felicitas
8 months ago
User4: I agree with User3, I think B is the correct answer.
upvoted
0
times
...
Corazon
9 months ago
User3: I think B is the right choice, by adding the specific user to the [deny] section in the /etc/atd.conf file.
upvoted
0
times
...
Ressie
9 months ago
User2: I'm not sure about that. I believe it's A, by adding the specific user to the /etc/at.allow file.
upvoted
0
times
...
Mireya
9 months ago
User1: I think the correct answer is D, adding the specific user to the /etc/at.deny file.
upvoted
0
times
...
...
Pansy
10 months ago
Hmm, I'm not sure. Maybe B, adding the user to the [deny] section in the /etc./atd.conf file? Seems like a logical place to restrict access.
upvoted
0
times
Genevieve
8 months ago
A seems like a good choice. Adding the user to the /etc/at.allow file would restrict their access.
upvoted
0
times
...
Veronika
8 months ago
I believe D is the way to go. Adding the user to the /etc/at.deny file should prevent scheduling tasks.
upvoted
0
times
...
Sherell
8 months ago
User3: I agree with User1, B seems like the logical answer.
upvoted
0
times
...
Merri
9 months ago
User2: I'm not sure, maybe D is the right choice.
upvoted
0
times
...
Desiree
9 months ago
User1: I think B is the correct option.
upvoted
0
times
...
Leah
9 months ago
I think B is the correct option. It makes sense to deny access in the atd.conf file.
upvoted
0
times
...
...
Ahmed
10 months ago
I think the correct answer is D, adding the specific user to the /etc/at.deny file. Seems straightforward and makes the most sense.
upvoted
0
times
Franklyn
8 months ago
D) By adding the specific user to the /etc/at.deny file.
upvoted
0
times
...
Linsey
8 months ago
C) By adding the specific user to the nojoba group.
upvoted
0
times
...
Johna
8 months ago
B) By adding the specific user to the [deny] section in the /etc./atd.conf file.
upvoted
0
times
...
Yong
8 months ago
A) By adding the specific user to the /etc/ at,allow file.
upvoted
0
times
...
Aleta
8 months ago
D) By adding the specific user to the /etc/at.deny file.
upvoted
0
times
...
Narcisa
9 months ago
C) By adding the specific user to the nojoba group.
upvoted
0
times
...
Desirae
9 months ago
B) By adding the specific user to the [deny] section in the /etc/atd.conf file.
upvoted
0
times
...
Tawna
10 months ago
A) By adding the specific user to the /etc/at.allow file.
upvoted
0
times
...
...
Shanda
10 months ago
I'm not sure, but I think C) By adding the specific user to the nojoba group could also work.
upvoted
0
times
...
Benedict
11 months ago
I disagree, I believe the correct answer is B) By adding the specific user to the [deny] section in the /etc./atd.conf file.
upvoted
0
times
...
Jani
11 months ago
I think the answer is D) By adding the specific user to the /etc/at.deny file.
upvoted
0
times
...
Log in to Pass4Success
×
Sign in:
Forgot my password
Log in
Report Comment
×
Is the comment made by
USERNAME
spam or abusive?
Commenting
×
In order to participate in the comments you need to be logged-in.
You can
sign-up
or
login
Save
Cancel
Luis
4 months agoAshlee
4 months agoNoble
4 months agoMargarett
4 months agoArminda
4 months agoOna
5 months agoBettyann
5 months agoLoise
5 months agoRene
5 months agoCyril
5 months agoDesirae
5 months agoVi
5 months agoDonette
9 months agoLeila
9 months agoRodrigo
9 months agoFelicitas
8 months agoCorazon
9 months agoRessie
9 months agoMireya
9 months agoPansy
10 months agoGenevieve
8 months agoVeronika
8 months agoSherell
8 months agoMerri
9 months agoDesiree
9 months agoLeah
9 months agoAhmed
10 months agoFranklyn
8 months agoLinsey
8 months agoJohna
8 months agoYong
8 months agoAleta
8 months agoNarcisa
9 months agoDesirae
9 months agoTawna
10 months agoShanda
10 months agoBenedict
11 months agoJani
11 months ago