Deal of The Day! 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
ServiceNow
Dell EMC
CheckPoint
Linux Foundation
Discount Deals
New
About
Contact
Login
Sign up
Home
Discussions
Linux Foundation Discussions
Exam LFCA Topic 2 Question 38 Discussion
Linux Foundation Exam LFCA Topic 2 Question 38 Discussion
Actual exam question for Linux Foundation's LFCA exam
Question #: 38
Topic #: 2
[All LFCA Questions]
Which of the following is considered a best practice for hardening SSHD?
A
Using portknocking to protect ssh access for root
B
Completely disabling ssh access
C
Disabling ssh access for root
D
Renaming root to a random name
Show Suggested Answer
Hide Answer
Suggested Answer:
C
by
Jina
at
Feb 06, 2025, 04:49 PM
Limited Time Offer
25%
Off
Get Premium LFCA Questions as Interactive Web-Based Practice Test or PDF
Contribute your Thoughts:
Submit
Cancel
Moon
1 months ago
Portknocking? What is this, the 90s? C is the way to go, folks. Keep it simple, keep it secure.
upvoted
0
times
Jacob
15 days ago
C) Disabling ssh access for root
upvoted
0
times
...
Lavera
25 days ago
A) Using portknocking to protect ssh access for root
upvoted
0
times
...
...
Hermila
1 months ago
Ah, the ol' 'security through obscurity' with option D. I'll stick to the proven method of C, thanks.
upvoted
0
times
Angelyn
25 days ago
User 2: I think option D can also be effective, it adds an extra layer of security.
upvoted
0
times
...
Eric
1 months ago
User 1: I prefer option C as well, it's a safer choice.
upvoted
0
times
...
...
Kenneth
2 months ago
I personally think using portknocking to protect ssh access for root is the best option.
upvoted
0
times
...
Salome
2 months ago
Disabling SSH altogether? B? No way, that's way too restrictive. Gotta go with C on this one.
upvoted
0
times
...
Alesia
2 months ago
I agree with Shawnee, disabling ssh access for root is a good security measure.
upvoted
0
times
...
Lennie
2 months ago
Renaming root? That's just asking for trouble. I'd go with C - simple and effective.
upvoted
0
times
Brunilda
11 days ago
Definitely, it's a simple and effective solution.
upvoted
0
times
...
Thomasena
13 days ago
Yeah, that sounds like a good idea.
upvoted
0
times
...
Peggie
17 days ago
I think disabling ssh access for root is the way to go.
upvoted
0
times
...
Odette
1 months ago
I agree, renaming root seems risky.
upvoted
0
times
...
...
Madelyn
2 months ago
Option C seems like the way to go. Disabling root access is a pretty standard security practice.
upvoted
0
times
Donte
1 months ago
Completely disabling ssh access might be too extreme in some cases.
upvoted
0
times
...
Minna
1 months ago
Using portknocking to protect ssh access for root is another option to consider.
upvoted
0
times
...
Evelynn
1 months ago
I think renaming root to a random name could also be effective.
upvoted
0
times
...
Albina
1 months ago
I agree, disabling root access is a good security measure.
upvoted
0
times
...
...
Shawnee
2 months ago
I think the best practice is to disable ssh access for root.
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
Moon
1 months agoJacob
15 days agoLavera
25 days agoHermila
1 months agoAngelyn
25 days agoEric
1 months agoKenneth
2 months agoSalome
2 months agoAlesia
2 months agoLennie
2 months agoBrunilda
11 days agoThomasena
13 days agoPeggie
17 days agoOdette
1 months agoMadelyn
2 months agoDonte
1 months agoMinna
1 months agoEvelynn
1 months agoAlbina
1 months agoShawnee
2 months ago