050-SEPROGRC-01 · Question #44
If one person working in an Archer instance launches a services-intensive process (such as a very large data feed), what impact might other users working in the same instance see?
The correct answer is D. The other users might experience noticeable lag until the process completes. In a shared RSA Archer instance, resource-intensive processes like large data feeds consume server resources and can degrade performance for all concurrent users.
Question
If one person working in an Archer instance launches a services-intensive process (such as a very large data feed), what impact might other users working in the same instance see?
Options
- AKeyword searching will not work.
- BRecords cannot be edited until the process completes.
- CThe other users will be automatically logged out of the system.
- DThe other users might experience noticeable lag until the process completes.
How the community answered
(33 responses)- A3% (1)
- B9% (3)
- C15% (5)
- D73% (24)
Why each option
In a shared RSA Archer instance, resource-intensive processes like large data feeds consume server resources and can degrade performance for all concurrent users.
Keyword searching is a separate indexed function and is not categorically disabled by a running data feed process.
Record editing is not locked or blocked system-wide due to a background process running; users retain the ability to edit records.
Archer does not automatically log out other users when a resource-intensive process is launched; sessions remain active.
Archer runs on shared server infrastructure, so a services-intensive process such as a large data feed consumes CPU, memory, and database resources that all users in the same instance depend on. This resource contention causes degraded response times, resulting in noticeable lag for other active users. The lag persists until the intensive process completes and server resources are freed.
Concept tested: Archer instance resource contention and performance impact
Topics
Community Discussion
No community discussion yet for this question.