RCA System Administration and Infrastructure 3 — Questions and Answers
Question 1: Which SQL Server feature should be configured to ensure Relativity remains available if the primary database server fails?
- Log Shipping
- Database Mirroring
- Always On Availability Groups (Correct answer)
- Snapshot Replication
Correct answer: Always On Availability Groups
SQL Server Always On Availability Groups are the recommended high-availability solution for Relativity, providing automatic failover and readable secondaries.
Question 2: An admin notices that Relativity agents are failing with 'Unable to connect to SQL Server' errors. What is the FIRST step to diagnose this?
- Restart all Relativity services on the web server
- Check the Agents tab in the Relativity Admin area for error details
- Verify SQL Server is running and the connection string in Instance Settings is correct (Correct answer)
- Re-install the Relativity Agent Service
Correct answer: Verify SQL Server is running and the connection string in Instance Settings is correct
Verifying SQL Server availability and the connection string in Instance Settings is the first diagnostic step for agent connectivity failures.
Question 3: What is the recommended practice for Relativity log file (LDF) placement on SQL Server?
- Place LDF files on the same volume as MDF files for simplicity
- Place LDF files on a dedicated high-speed sequential-write disk (Correct answer)
- Store LDF files in a SAN shared with other applications
- Compress LDF files to save storage space
Correct answer: Place LDF files on a dedicated high-speed sequential-write disk
LDF files generate sequential write I/O, so placing them on a dedicated high-speed disk prevents contention and optimizes transaction logging performance.
Question 4: In Relativity, what does the 'Invariant' service primarily manage?
- User authentication and SSO
- File storage and native file streaming for the repository (Correct answer)
- SQL query optimization
- Structured analytics model building
Correct answer: File storage and native file streaming for the repository
Invariant is Relativity's file storage service that manages native files, images, and other binary assets stored in the file repository.
Question 5: A Relativity workspace is experiencing slow document loading in the viewer. After confirming SQL performance is normal, what should the admin check next?
- Number of active users logged into the workspace
- Network bandwidth and latency between web servers and file repository (Correct answer)
- The number of fields in the document layout
- Whether the workspace has an active legal hold
Correct answer: Network bandwidth and latency between web servers and file repository
Viewer performance depends heavily on file retrieval from the repository; poor network connectivity between web servers and the file share causes slow document loading.
Question 6: Which Relativity Instance Setting controls the maximum file size that can be uploaded through the web interface?
- MaxUploadSizeInMB (Correct answer)
- WebUploadFileSizeLimit
- UploadLimitMB
- FileUploadMaxSize
Correct answer: MaxUploadSizeInMB
The MaxUploadSizeInMB Instance Setting controls the maximum file size allowed for web-based uploads in Relativity.
Question 7: When configuring a new Relativity worker server, which Windows feature is required to support native document imaging?
- Internet Information Services (IIS)
- Windows Desktop Experience (Correct answer)
- Hyper-V role
- Network Load Balancing
Correct answer: Windows Desktop Experience
Windows Desktop Experience is required on worker servers because imaging software relies on Windows GDI components that are part of this feature.
RCA System Administration and Infrastructure 3
Which SQL Server feature should be configured to ensure Relativity remains available if the primary database server fails?