Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Oracle Exam 1Z0-822 Topic 1 Question 100 Discussion

Actual exam question for Oracle's 1Z0-822 exam
Question #: 100
Topic #: 1
[All 1Z0-822 Questions]

You administer an Oracle Solaris 11 server with multiple zones. You want to configure it so that all nonprivileged users in the global zone see only their own process. What must you do to make the change?

Show Suggested Answer Hide Answer
Suggested Answer: A, D

Contribute your Thoughts:

Bulah
1 months ago
Ah, the old 'modify the LIMITPRIV variable' trick. Classic! I bet that's the one the Oracle folks are hoping we'll all pick. Not this time, my friend. I'm going with option C, the priv= attribute.
upvoted 0 times
Izetta
4 days ago
I see your point, but I still think option A is the best choice. It's a classic for a reason.
upvoted 0 times
...
Lindsay
10 days ago
Well, I'm sticking with option C. The priv= attribute seems like the most direct solution.
upvoted 0 times
...
Shad
12 days ago
I'm not so sure about that. I'm leaning towards option A, modifying the LIMITPRIV variable.
upvoted 0 times
...
Freeman
18 days ago
I think option C is the way to go. It's all about that priv= attribute.
upvoted 0 times
...
...
Anastacia
1 months ago
Joke's on you, I'm going to choose option D just to see the look on the examiner's face. Configuring privileges for the ps command? That's a bold move, Cotton. Let's see if it pays off.
upvoted 0 times
...
Pok
1 months ago
I'm not so sure about that. Modifying the basic privilege set in the policy.conf file seems more straightforward to me. Why complicate things with that priv= attribute stuff?
upvoted 0 times
Felice
4 days ago
I see your point, but I still think modifying the basic privilege set is the simpler option.
upvoted 0 times
...
Alline
14 days ago
But wouldn't it be easier to just configure the priv= attribute in the prof_attr.d/core-os file?
upvoted 0 times
...
Lashawna
21 days ago
I think modifying the basic privilege set in the policy.conf file is the way to go.
upvoted 0 times
...
...
Ronny
2 months ago
Hmm, I think option C is the way to go. Configuring the priv= attribute in the /etc/security/prof_attr.d/core-os file sounds like the right way to limit user visibility in the global zone.
upvoted 0 times
Margot
15 days ago
Let's go with option C then, it sounds like the most appropriate solution.
upvoted 0 times
...
Daniela
25 days ago
I think so too, configuring the priv= attribute in that file should do the trick.
upvoted 0 times
...
Brock
27 days ago
I agree, option C seems like the correct choice.
upvoted 0 times
...
...
Yolando
2 months ago
Hmm, I see your point. But I still think A) makes more sense because it specifically mentions user privileges.
upvoted 0 times
...
Jacob
2 months ago
I disagree, I believe the correct answer is B) Modify the basic privilege set in the /etc/security/policy.conf file.
upvoted 0 times
...
Yolando
3 months ago
I think the answer is A) Modify the LIMITPRIV variable in the /etc/usr/user_attr file.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77