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

RSA Exam 050-11-CARSANWLN01 Topic 2 Question 86 Discussion

Actual exam question for RSA's 050-11-CARSANWLN01 exam
Question #: 86
Topic #: 2
[All 050-11-CARSANWLN01 Questions]

To prevent a Meta key from being indexed on a core service, you can

Show Suggested Answer Hide Answer
Suggested Answer: A

Contribute your Thoughts:

Jody
2 days ago
Haha, Option D is just ridiculous. Setting the 'valueMax' to '000000'? That's not going to do anything to prevent indexing!
upvoted 0 times
...
Fernanda
6 days ago
I'm leaning towards Option C. Removing the Meta key from the Manage Default Meta Keys interface seems like the most straightforward approach.
upvoted 0 times
...
Roselle
11 days ago
But wouldn't removing the Meta key from the Manage Default Meta Keys interface prevent it from being indexed?
upvoted 0 times
...
Edgar
13 days ago
I disagree, I believe the correct answer is A) disable the parser for the Meta key in the device configuration.
upvoted 0 times
...
Vincenza
16 days ago
Option B looks like the correct way to prevent a Meta key from being indexed. Adding the indexNone value to the key in the custom index file should do the trick.
upvoted 0 times
Ashton
3 days ago
I think option B is the way to go.
upvoted 0 times
...
...
Roselle
17 days ago
I think the answer is C) remove the Meta key from the Manage Default Meta Keys interface.
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