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

- Free Preparation Discussions

LPI 102-500 Exam - Topic 5 Question 70 Discussion

Posted by Lettie on Nov 21, 2023 at 06:39 PM

How is the file format of /etc/crontab different from a normal crontab file? (Select TWO correct answers)

Suggested Answer: D

Get Premium 102-500 Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test
43 comments · newest first
YO
Yolande 11 months ago
I thought both formats were pretty similar, but I guess not!
AN
Angella 11 months ago
A normal crontab file must be installed with the crontab command, right?
VI
Virgina 11 months ago
Wait, does the /etc/crontab really allow a year field?
KA
Karan 11 months ago
Totally agree, that's a big difference!
LA
Lauran 11 months ago
The /etc/crontab file has a user field for commands.
ST
Stefania 12 months ago
I’m pretty confident that the /etc/crontab file includes a user field, but I’m not sure about the year field being a feature.
SH
Shizue 12 months ago
I feel like the environment variable substitution is something that applies to normal crontab files, but I might be mixing it up with something else.
RE
Reyes 12 months ago
I remember that a normal crontab file is created with the crontab command, but I can't recall if that's the only difference.
GA
Garry 1 year ago
I think the /etc/crontab file has a user field, but I'm not entirely sure if it specifies a year field too.
WI
Wilford 1 year ago
I'm a bit confused about the environment variable substitution part. I'll need to double-check the details on that.
TR
Tresa 1 year ago
I think the key difference is that the /etc/crontab file can specify a user field, while a normal crontab doesn't have that. I'm pretty confident about that one.
CE
Celeste 1 year ago
Okay, let's see. I know the /etc/crontab file is system-wide, while a normal crontab is user-specific. But I'm not sure about the other differences.
IZ
Izetta 1 year ago
Hmm, this looks like a tricky one. I'll need to think carefully about the differences between the /etc/crontab file and a normal crontab file.
WH
Whitney 1 year ago
Ah, I remember now - the /etc/crontab file can't use environment variable substitution, but a normal crontab can. That's an important distinction.
OC
Octavio 1 year ago
Okay, I've got a strategy for this. Based on my experience, the best way to add a sensitive environment-specific configuration value is to use the Cloud CLI for Commerce. That way, I can set the value securely without having to directly edit any configuration files.
VI
Vivan 1 year ago
Hmm, I'm a little unsure about this one. The options seem similar, but I think I can eliminate a couple based on my understanding of architecture frameworks.
RY
Ryann 1 year ago
If I recall correctly, the program should output something like 10 11 repeatedly, but it might depend on how many iterations there are.
KA
Kattie 1 year ago
I'm not entirely sure, but "A" for management sounds familiar. I remember discussions about management's role in achieving objectives.
DY
Dyan 1 year ago
I'm going with B and D. After all, the /etc/crontab file is like the boss's version of a crontab, so it's got a user field that the regular crontab doesn't have.
DA
Daren 1 year ago
↳ replying to Dyan
Yeah, it's easy to overlook that one. But it's definitely a key difference.
JE
Jeannine 1 year ago
↳ replying to Dyan
I always forget about the year field in /etc/crontab.
TA
Tamesha 1 year ago
↳ replying to Dyan
Yeah, that's true. It's like the super crontab file.
DU
Dulce 1 year ago
↳ replying to Dyan
I think you're right, the /etc/crontab file does have a user field for commands.
KA
Kattie 1 year ago
This question is a real head-scratcher! I bet the developers who wrote this exam question were having a field day coming up with these tricky options.
MI
Millie 1 year ago
↳ replying to Kattie
I know, these options really make you think!
EM
Emerson 1 year ago
↳ replying to Kattie
D) The /etc/crontab file has a user field for commands.
LA
Larae 1 year ago
↳ replying to Kattie
A) The /etc/crontab file can specify a year field.
GL
Glory 1 year ago
I'm pretty sure the answer is B and D. The /etc/crontab file has a user field, but a normal crontab file is installed with the crontab command. That's the difference, right?
BU
Bulah 1 year ago
B and C are the correct answers. A normal crontab file needs to be installed using the crontab command, and it supports environment variable substitution, unlike the /etc/crontab file.
KA
Kaycee 1 year ago
↳ replying to Bulah
Oh, I see. Thanks for clarifying that!
LE
Lenora 1 year ago
↳ replying to Bulah
C) A normal crontab file allows for environment variable substitution.
ME
Meghan 1 year ago
↳ replying to Bulah
B) A normal crontab file must be installed with the crontab command.
GE
Germaine 1 year ago
↳ replying to Bulah
The /etc/crontab file has a user field for commands.
MA
Marjory 1 year ago
↳ replying to Bulah
The /etc/crontab file can specify a year field.
VI
Viola 1 year ago
↳ replying to Bulah
B and C are the correct answers.
JE
Jesusita 2 years ago
I agree with both of you. The /etc/crontab file is different from a normal crontab file in those aspects.
AL
Alison 2 years ago
A and D seem like the correct answers. The /etc/crontab file has a user field to specify the user that the command should run as, and it can also specify a year field, which a normal crontab file cannot do.
BR
Brinda 1 year ago
↳ replying to Alison
B) A normal crontab file must be installed with the crontab command.
LO
Lonny 1 year ago
↳ replying to Alison
Yes, that's correct. The /etc/crontab file is different from a normal crontab file in those ways.
AS
Ashlee 1 year ago
↳ replying to Alison
D) The /etc/crontab file has a user field for commands.
ST
Stevie 1 year ago
↳ replying to Alison
A) The /etc/crontab file can specify a year field.
AR
Arlene 2 years ago
I believe the /etc/crontab file has a user field for commands.
MA
Mari 2 years ago
I think the /etc/crontab file can specify a year field.
0/2000 characters

Save Cancel