Practice Test 1

1. 1. [b, d] Dates are stored as data type time.

2. 2. [c, d]

3. 3. [b, d]

4. 4. [c] A folder cannot be a component of a virtual document. Versions of components are dependent on their binding rules.

5. 5. [a, b] The Index server is used for full-text indexing and is not even required to be present in a deployment. Webtop is one WDK application and other WDK applications can be used independently.

6. 6. [a, c] A sequence of states is present in a lifecycle, not a workflow. Performers can be dynamically determined using aliases.

7. 7. [b, c, d] A lifecycle contains states, not activities.

8. 8. [a] Whether an ACL is an ACL template is identified by the acl_class attribute (1 = template). If an ACL is private (regular) then it cannot be a template, since this is also determined via acl_class (0 = regular). Only ACL templates contain alias references. ACL's can exist without any relation to ACL templates.

9. 9. [a, b] An alias can be a placeholder for user, group, location, or permission set (ACL).

10. 10. [d] Extended privileges pertain to auditing.

11. 11. [b, d] 3.4 normally or 3.3.1.0 if a branch is created.

12. 12. [b, d] The type tag 09 represents dm_document and its subtypes.

13. 13. [b] A value in a repeating attribute is tested using the ANY keyword.

14. 14. [a, c]

15. 15. [b] Virtual documents are ideally suited to manage hierarchical content such as that of a book.

16. 16. [a, b, d] A cabinet is a top-level folder and cannot be linked into anything.

17. 17. [d]

18. 18. [c]

19. 19. [b] Without full-text indexing, the keywords property is not used in a simple search, the search is case-sensitive, and content is not searched. The name of the document is present in the object_name property that is searched.

20. 20. [c] The new text needs to be re-indexed before it can be found. A fixed-time delay cannot guarantee re-indexing.

21. 21. [d] A dynamic group membership at run time is altered using custom client code.

22. 22. [a, b, d] r_object_id is unique within a repository. All versions of an object have same i_chronicle_id.

23. 23. [a] By default, a user is authenticated against the Operating System.

24. 24. [d] REGISTER TABLE registers a table to become accessible through DQL queries.

25. 25. [a, c] Write and Change State are the minimum permissions needed to promote.

26. 26. [a, d] Read permission is required for copying. Change Location is needed for moving from the primary folder. If folder security is enabled, Browse is needed on the source folder and Write on the destination folder for copying a file.

27. 27. [b] Subscribing to documents and locations makes them accessible under the Subscriptions node. This information is saved in the repository and is available from all clients (browsers on multiple computers).

28. 28. [a, b]

29. 29. [c]

30. 30. [c] A workflow template cannot be instantiated unless it is in the installed state. Stopped workflows and the active state of the workflow template owner don't affect the availability of the template for creating new workflows. There is no set limit on the number of simultaneous workflows.

31. 31. [a, c] Attribute length cannot be reduced. Only non-inherited attributes can be dropped.

32. 32. [a, c] A custom type can be dropped only if no objects and no subtypes of that type exist in the repository.

33. 33. [b] A DocApp is stored as an object of type dm_application in the repository. A DocApp can be archived to the file system as a DocApp archive.

34. 34. [b] A workflow can use a simple documents, virtual documents, and folders.

35. 35. [b] A document can be checked in as the same version. A new document gets version 1.0. Canceling a checkout does not alter the content of the existing version. A new branch changes the version.

36. 36. [a, c, d] The actual version depends on the existing version tree and whether a minor or major increment is chosen on checkin. A minor increment can result in 2.6. A second branch can lead to 2.5.2.0. A major increment can lead to 5.0. The following figures illustrate the scenario:

    
    
    

37. 37. [d] i_chronicle_id is not a property of a rendition.

38. 38. [d] The inheritance relationship exists between types, not objects.

39. 39. [a, c, d] The Content Server always honors the configured security. If she does not have appropriate permissions on an object she either needs to use a user ID that does have permissions or alter permissions to grant her appropriate access rights.

40. 40. [a] The first two digits of object ID represent the object type or its supertype, which is one of the built-in types.

41. 41. [a, c, d] This query will consider dm_sysobject and its subtypes. dm_user is not a subtype of dm_sysobject. It doesn't even have an attribute named object_name.

42. 42. [c]

43. 43. [d] The Client capabilities are optionally enforced by client applications. There is no requirement for client capabilities to be enforced.

44. 44. [d] Roles and domains are also groups. A group must be named uniquely within a repository.

45. 45. [d] Extended Delete is an extended permission and does not imply any other permission, basic or extended.

46. 46. [a, c] A Superuser is a special user and has at least the same effective permissions as the object owner on each object. Each object owner effectively has at least Read permission and all extended permissions other than Extended Delete. The word "effectively" here means that the Content Server will use these effective permissions if the explicitly granted permissions are more restrictive than these. The Change Permission extended permission allows John to grant himself Delete permission explicitly.

47. 47. [c] The object inherits the permission set of folder A since the default ACL mode is folder. Linking the object to folder B does not change its primary folder. Further, the permission set is only inherited when the new object is created.

48. 48. [b, d] Each custom type can have 0 or 1 supertype. Custom types cannot be supertypes of the built-in types.

49. 49. [d] Value assistance is a part of the data dictionary but Content Server does not use the data dictionary for its functionality.

50. 50. [d] The type of an object can only be changed to the supertype or a subtype of the current type. Since both of these types have NULL supertype, it is not possible to change the object type from janes_doc to johns_doc, even with multiple type changes.

51. 51. [c, d] Removing a document from the DocApp does not remove it from the repository. Also a document no longer in the DocApp is not included in an archive, unless another folder/cabinet includes it and the installation options require the objects to be included as well.

52. 52. [a] The root document and all the components need to be added explicitly. However, renditions are automatically added when a document is added to the DocApp.

53. 53. [c] The best way is to add the cabinet and include the folder structure and objects via the install option. This way, there is minimum onus on the developer and the full folder structure and linked objects are included when an archive is created.

54. 54. [d]

55. 55. [b] The default lifecycle for an object type can be applied to its objects without knowing the name of the lifecycle.

56. 56. [a, b] An alias can also represent a location or a permission set. The Content Server recognizes and resolves alias references in certain attributes and a method argument.

57. 57. [a] Valid references are %supervisor and %janes_alias_set.supervisor.

58. 58. [a, b, c] A snapshot is stored as an object of type dm_assembly, which is not a sysobject. Only sysobjects other than cabinets and folders (and their subtypes) can be components in virtual documents.

59. 59. [b] Only taking a snapshot is insufficient since the component objects and the root object can be altered even in the current version. Snapshots can be frozen, not virtual documents.

60. 60. [d] The answer depends on other factors. If A1 and A2 are sequential within the workflow then the order of execution is determined by the sequence. Priority is used by the workflow agent when multiple tasks corresponding to automatic activities (potentially from different workflows) are ready to be executed at the same time.