Which one of the following statements is true about adding positions to the local database?
-
Adding positions is only allowed by a primary team member.
-
Adding positions is only allowed when the project is locked
-
Adding positions is only allowed when connected to server
-
Adding positions is only allowed when the local database is locked
In database systems that support local caching, adding positions typically requires an active server connection to ensure data consistency and synchronization. When disconnected, the local database is often read-only to prevent conflicts. Options A, B, and D are incorrect because team member roles, project locks, and database locks do not control this fundamental connectivity requirement.
Adding new positions to the local (mobile/remote) database requires a live connection back to the central server because position records need server-side validation and ID assignment before they can be created locally. This is why the operation is gated on being connected to the server rather than on locking the project, locking the local database, or being a 'primary team member' (which isn't a real constraint here).