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-6201-ARCHERASC01 Topic 1 Question 78 Discussion

Actual exam question for RSA's 050-6201-ARCHERASC01 exam
Question #: 78
Topic #: 1
[All 050-6201-ARCHERASC01 Questions]

Why is it important that users be able to interact with fields that are being evaluated by a rule within Events?

Show Suggested Answer Hide Answer
Suggested Answer: D

Contribute your Thoughts:

Sang
9 days ago
A) Only fields that all users can see can be evaluated within a rule. That seems overly restrictive, how would you ever get anything done?
upvoted 0 times
...
William
14 days ago
But what if only administrators can configure events?
upvoted 0 times
...
Kristin
14 days ago
B) This is a non-issue, as only administrators are able to configure events. Haha, if that were the case, it would make things a lot simpler for the developers!
upvoted 0 times
...
Carmela
15 days ago
D) If a user cannot interact with all fields, he cannot save the record, and therefore, cannot trigger calculations. This seems like the most comprehensive answer that covers the broader implications.
upvoted 0 times
Tegan
4 days ago
C) If a user cannot interact with an evaluated field, he cannot trigger the action included in an event.
upvoted 0 times
...
...
Justine
17 days ago
C) If a user cannot interact with an evaluated field, he cannot trigger the action included in an event. This makes sense, as the user needs to be able to interact with the fields in order to set off the event.
upvoted 0 times
...
Maryann
17 days ago
I agree, if users can't interact with evaluated fields, they can't trigger actions.
upvoted 0 times
...
Johnna
20 days ago
I think it's important because users need to trigger actions in events.
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