1. [False] Any file can be considered to be content. Even though a CSV file contains structured data, it can be stored as content in a repository just like any other file.
2. [c] Metadata is stored in a database.
3. [False] The repository represents the storage unit while Content Server serves content and metadata stored in the repository.
4. [b, c] One Content Server instance is dedicated to one repository but more than one Content Server instance can be dedicated to the same repository.
5. [True] DQL can be used to query any database tables registered to be queried via DQL.
6. [a, d] Calendars and chat are not offered by the collaborative edition of the Content Server.
7. [a, c] Workflows can be defined for documents, folders, and virtual documents.
8. [b, c] Accountability features is provided via auditing and tracing.
9. [b, d] IDQL and IAPI are the interactive query utilities for Documentum.
10. [a, b] ACL and permission set is one and the same thing.
1. [False] Any file can be considered to be content. Even though a CSV file contains structured data, it can be stored as content in a repository just like any other file.
2. [c] Metadata is stored in a database.
3. [False] The repository represents the storage unit while Content Server serves content and metadata stored in the repository.
4. [b, c] One Content Server instance is dedicated to one repository but more than one Content Server instance can be dedicated to the same repository.
5. [True] DQL can be used to query any database tables registered to be queried via DQL.
6. [a, d] Calendars and chat are not offered by the collaborative edition of the Content Server.
7. [a, c] Workflows can be defined for documents, folders, and virtual documents.
8. [b, c] Accountability features is provided via auditing and tracing.
9. [b, d] IDQL and IAPI are the interactive query utilities for Documentum.
10. [a, b] ACL and permission set is one and the same thing.
1. [b, d] 1.0, CURRENT
2. [b, c] Export, Checkout
3. [True]
4. [False] A checkout can also be canceled by a superuser.
5. [False] The user can choose to keep the current version on checkin.
6. [a, b, c, d] Any version can be the CURRENT version.
7. [d] A folder cannot be versioned.
8. [a, b, c, d] Checking in with minor version increment can result in 3.5 and major version increment can result in 4.0. However, if 4.0 already exist in the version tree the major increment results in 5.0. If a new branch is being created and one already exists the new version will be 3.4.2.0.
9. [b]
10. [d]
i_chronicle_idis not a property of a rendition.
1. [False] inheritance applies to types and not to objects.
2. [True]
dm_folderdoes not define any single-valued property of its own.3. [False] Security is enforced by the Content Server and this behavior is not dependent upon the mechanism of access (DFC or DQL).
4. [09]The object type tag fordm_documentand its subtypes is09.5. [b] These properties are normally managed by Content Server for its internal purposes and not seen by the users or applications.
6. [c] 4. Since records are shared by different properties, the total number of records is the maximum number of values present for any repeating property.
7. [False]
authorsis a property inherited fromdm_sysobject. dm_documentdoes not have any properties of its own and thus no persistence tables of its own.8. [d] The first two hex digits in
r_object_idrepresent a tag for the object type.9. [True] DQL can be used to query database tables directly, though the tables being queried need to be registered first.
10. [True] A DQL query on a type queries its subtypes as well and
dm_documentis a subtype ofdm_sysobject.
1. [False] Some Documentum layers span multiple tiers.
2. [a, c, d] The layers are Application Layer, Component and Development Layer (Interface Layer), Content Services Layer, and Repository Layer.
3. [c] The Index Server creates full-text indexes based on the contents of documents and these indexes are used for searching.
4. [False] The BOF is supported by DFC and it is at a higher level than DMCL.
5. [b] DFC is made available to the .NET platform using a Primary Interop Assembly.
6. [a] A Content Server projects to connection brokers by announcing its status when it starts up.
7. [c] The Connection broker information is stored in
dmcl.inion the client machine.8. [c] DMCL uses RPC capabilities to perform network communication.
9. [b] The WDK components are the Content Server clients in WDK applications.
10. [d] The WDK customization layer is called
custom, by default.
1. [False] Authentication establishes the identity of a user while authorization gives the user access to certain functionality or resources.
2. [False]
dm_check_passwordis only used on UNIX.3. [d] A user can be created in the repository without the existence of the corresponding external account. The external account is needed for authentication to succeed in these cases.
4. [False] The database owner for the repository database is called the repository owner.
5. [False] Client applications may choose to enforce client capabilities. Webtop and Desktop clients do enforce them.
6. [False] Document creation is not controlled by privileges.
7. [False] Create Cabinet and Create Type are separate privileges and each of these needs to be explicitly granted.
8. [True] The Superuser privilege includes all Sysadmin privileges.
9. [False] System Administrator client capability would be needed only if the client application is being used to create the user-enforced client capabilities.
10. [True]
1. [a, c] Roles and domains are also groups, just used in special ways.
2. [False] Only the configured members of the dynamic group can be added as members for the session.
3. [False] The Content Server neither enforces client capability nor any special treatment for roles.
4. [False] The membership of a sub-role implies membership of the super-role.
5. [False] The Content Server does not enforce the private/public nature of roles, clients do.
6. [False] The automatic public and private assignments based on privileges are defaults. The public/private nature can be changed afterwards.
7. [c]
8. [False]
group_adminandowner_nameare two separate properties and can have different values.9. [False] Each group must be named uniquely within a repository.
10. [True]
1. [False] Extended permissions are unrelated to basic permissions.
2. [False] A permission set and ACL are one and the same.
3. [b, c] The basic permissions are hierarchical and a given permission implies all lower permissions.
4. [False] All except Extended Delete.
5. [False] Custom permission sets are automatically created by the Content Server when permissions for an object are modified.
6. [c] The ACL is inherited only at the time of new object creation. At least one Documentum document indicates that the ACL should be inherited from the new primary folder, if the primary folder is changed. However, it doesn't in version 5.3.
7. [b] There is no change in the primary folder. Further, see the explanation in the answer to question 6.
8. [a, b]
9. [a, b, c, d] As an owner, Jane gets all extended permissions other than Extended Delete, and as a member of world she gets Extended Delete.
10. [b]
1. [b, c] Jane won't see
JohnsDocumentsfolder but can get to the document through search sinceBROWSEpermission lets her see the properties and the object.2. [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_nameproperty which is searched.3. [a, b, c, d] Since full-text indexing is enabled, all searchable properties and content are searched and the matches are case-insensitive.
4. [b]
5. [c]
6. [False] The search stores the criteria only and not the results. The results will depend on the actual objects and their metadata and content.
7. [False] The saved searches are not compatible across applications.
8. [False] Subscription only makes a document available under the Subscriptions node.
9. [False] The shortcut takes the user back into Webtop.
10. [False] Assuming the user is able to get into Webtop, the user still needs appropriate permissions to access the linked object.
1. [b, d] Each custom type can have 0 or 1 supertype. Custom types cannot be supertypes of the built-in types.
2. [a, c]
dm_documentis a built-in object type and cannot be modified.3. [d]
4. [c]
5. [b] Since the
my_invoiceonly has single-valued properties of its own, it will only use one tablemy_invoice_s.6. [False] Even though types cannot be versioned, the changes still need to be committed via checkin.
7. [False] The Content Server does not enforce constraints. In fact, it doesn't use data dictionary for its own functionality.
8. [False] The length of a property is used only if the property is of type String.
9. [True] Multiple conditional lists and one default list can be specified for one property.
10. [a, c] The object type can only be changed to the immediate supertype or a subtype of the current type.
1. [c]
2. [False ] DocApp version is not stored in the archive. The new version depends on the existing version in the new repository.
3. [a, c]
4. [b] DocApp can be archived to the file system but the DocApp only resides in the repository.
5. [a]
6. [b]
7. [b]
8. [c]
9. [d]
10. [False] It can have different users and groups with same permissions and privileges.
1. [False] A workflow template defines a process while a workflow is an instance of the process in execution.
2. [c]
3. [c]
4. [False] They can be selected simultaneously. It is the responsibility of the developer to configure the activity appropriately to prevent this from happening.
5. [True] Aliases help templates to be more portable across repositories and in various business contexts.
6. [a, b, c]
7. [a, b, c] Start Workflow, Start Attachments, Quick Flow
8. [a, b]
9. [False]
10. [True] A user is marked unavailable by specifying a proxy.
1. [False] While workflows and lifecycles provide rich capabilities together, they can be used independently of each other.
2. [b, c] A lifecycle must be installed in a repository for use and it is used by applying to objects.
3. [False] Demoting to a state does not check for entry criteria.
4. [a, b] Either all actions in a lifecycle are implemented in Java or all are implemented in Docbasic.
5. [False] A user can apply the default lifecycle for an object type without knowing the name of that lifecycle.
6. [True] In addition to entry criteria being met, the entry actions must also complete successfully.
7. [c]
8. [a]
9. [a]
10. [a, b, c, d]
1. [False] An alias set contains name-value pairs while a permission set grants permissions to different accessors.
2. [True] Alias references are only present in permission set templates, not in the other types of permission sets.
3. [a, b, d]
4. [c, d] The type name and property name are mismatched in a and b.
5. [True] This is what aliases are for and the
folderSpecargument can contain an alias reference.6. [c, d]
7. [c] One custom permission set is created per object, as the permission set template is assigned to objects.
8. [a, b] Only the alias set attached to the object is examined. If no alias set is attached then no alias sets are examined.
9. [a, b, c]
10. [c]
1. [True]
2. [c]
3. [a, c]
4. [b]
5. [c]
6. [False] If the snapshot is not frozen the component documents can be deleted or checked in as existing versions. Both of these actions can alter the overall contents of the virtual document.
7. [c]
8. [b]
9. [False] A missing object from the virtual document hierarchy results in a broken binding.
10. [False] Virtual document preferences are used by applications such as Webtop.
1. [b, d] Dates are stored as data type
time.2. [c, d]
3. [b, d]
4. [c] A folder cannot be a component of a virtual document. Versions of components are dependent on their binding rules.
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. [a, c] A sequence of states is present in a lifecycle, not a workflow. Performers can be dynamically determined using aliases.
7. [b, c, d] A lifecycle contains states, not activities.
8. [a] Whether an ACL is an ACL template is identified by the
acl_classattribute (1 =template). If an ACL is private (regular) then it cannot be a template, since this is also determined viaacl_class(0 =regular). Only ACL templates contain alias references. ACL's can exist without any relation to ACL templates.9. [a, b] An alias can be a placeholder for user, group, location, or permission set (ACL).
10. [d] Extended privileges pertain to auditing.
11. [b, d] 3.4 normally or 3.3.1.0 if a branch is created.
12. [b, d] The type tag 09 represents
dm_documentand its subtypes.13. [b] A value in a repeating attribute is tested using the
ANYkeyword.14. [a, c]
15. [b] Virtual documents are ideally suited to manage hierarchical content such as that of a book.
16. [a, b, d] A cabinet is a top-level folder and cannot be linked into anything.
17. [d]
18. [c]
19. [b] Without full-text indexing, the
keywordsproperty 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 theobject_nameproperty that is searched.20. [c] The new text needs to be re-indexed before it can be found. A fixed-time delay cannot guarantee re-indexing.
21. [d] A dynamic group membership at run time is altered using custom client code.
22. [a, b, d]
r_object_idis unique within a repository. All versions of an object have samei_chronicle_id.23. [a] By default, a user is authenticated against the Operating System.
24. [d]
REGISTER TABLEregisters a table to become accessible through DQL queries.25. [a, c] Write and Change State are the minimum permissions needed to promote.
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. [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. [a, b]
29. [c]
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. [a, c] Attribute length cannot be reduced. Only non-inherited attributes can be dropped.
32. [a, c] A custom type can be dropped only if no objects and no subtypes of that type exist in the repository.
33. [b] A DocApp is stored as an object of type
dm_applicationin the repository. A DocApp can be archived to the file system as a DocApp archive.34. [b] A workflow can use a simple documents, virtual documents, and folders.
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. [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. [d]
i_chronicle_idis not a property of a rendition.38. [d] The inheritance relationship exists between types, not objects.
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. [a] The first two digits of object ID represent the object type or its supertype, which is one of the built-in types.
41. [a, c, d] This query will consider
dm_sysobjectand its subtypes.dm_useris not a subtype ofdm_sysobject. It doesn't even have an attribute namedobject_name.42. [c]
43. [d] The Client capabilities are optionally enforced by client applications. There is no requirement for client capabilities to be enforced.
44. [d] Roles and domains are also groups. A group must be named uniquely within a repository.
45. [d] Extended Delete is an extended permission and does not imply any other permission, basic or extended.
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. [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. [b, d] Each custom type can have 0 or 1 supertype. Custom types cannot be supertypes of the built-in types.
49. [d] Value assistance is a part of the data dictionary but Content Server does not use the data dictionary for its functionality.
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_doctojohns_doc, even with multiple type changes.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. [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. [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. [d]
55. [b] The default lifecycle for an object type can be applied to its objects without knowing the name of the lifecycle.
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. [a] Valid references are
%supervisorand%janes_alias_set.supervisor.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. [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. [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.
1. [b]
2. [b] The saved search is stored in Saved Searches in the user's default folder. Appropriate permissions are always needed to access objects.
3. [b] Two content servers can serve the same repository. Each Content Server can project to two Connection Brokers. Both of these components are essential for a client to connect to and use a repository. Application Server and Database can also use their high-availability features such as clustering, but they are not specific to Documentum infrastructure and not sufficient to make a Documentum repository highly available.
4. [c] Draft, Validated, and Installed are states of the workflow template not of the workflow.
5. [c] Workflow Manager is used for designing workflow templates. There is no product/feature in Documentum called Workflow Inspector. Task Manager is used for viewing one particular task.
6. [b, c] Write permission doesn't involve extended permissions. Binding rules relate to virtual documents. An ACL template is one that uses alias references. Aliases are resolved using alias sets. An ACL template can refer to an alias named backup. This reference can be resolved for each case using the owner's alias set.
7. [a, b, d] A Superuser automatically gets the owner permissions on all objects in the repository. The object owner always has Read and all extended permissions other than Extended Delete on the object. This gives Jane Read and Change Location. She gets Version permission via membership of
Managers. With the given information, a Write permission cannot be inferred.8. [a, b] Relate implies Browse and Read permissions. These permissions do not allow checking out or modifying the contents.
9. [b, c] The major version is always of the form x.0. Implicit version labels always have an even number of components separated by dots. 5.2.1 is not a valid implicit version label.
10. [a, b] Binding rules indicate which component versions are part of the virtual document, they do not prevent changes to components. Freezing a snapshot does affect what can be done to a component that is a part of the snapshot.
11. [b] Only sysobjects and their subtypes excluding folders and their subtypes can be virtual document components. Further,
dm_cabinetis a subtype ofdm_folder.12. [a, c, d] The attributes are inherited by subtypes from supertypes, so
my_doccannot inheritmy_ref_idfrommy_invoice.13. [a, b, c, d] Attribute names must use lower-case letters and cannot start with
a_. A type name cannot contain a space. A group name can have up to 32 characters.14. [a, c, d] These tasks require Superuser privilege.
15. [b]
16. [c, d] As an owner she already has Change Location permission. Extended Delete does not give her anything more than the Delete permission that she already has. So the problem is likely due to folder security. Since she is attempting to move, both unlinking and linking are involved. Thus, she needs Write permission on both the source and the destination folders.
17. [c] Quick Flow and Send to Distribution List are the same and provide a simple ad hoc workflow mechanism. Since there is sufficient time to design and test the workflow and the needs are custom, a custom workflow template is ideally suited. A lifecycle doesn't model a process — it rather models various stages for a document and transitions among them.
18. [a, b] Checkin affects the current or next version. A chronicle ID cannot be changed — that would mean moving from one version tree to another.
19. [d] The other options relate to content storage.
20. [a] The question is about one repository. Repository connections are handled by Content Server. Better hardware is not the only solution for this problem.
21. [c] From this list, notes are the only feature added by the collaborative edition. Other supported collaborative features are rooms, discussions, and contextual folders. Virtual documents are supported by the Content Server.
22. [c]
dm_documenthas no attributes of its own andauthorsis a repeating property ofdm_sysobject.23. [a, b, c, d]
24. [b]
25. [b] Superuser privilege implies Sysadmin privilege. Sysadmin privilege implies all privileges other than Superuser privilege.
26. [b, c]
27. [b, c] A dynamic group can be used as Members-by-default or Non-members-by-default. The membership can be changed only among the pre-defined members using custom code at run time.
28. [d] Content Server does not attach any meaning to roles. Roles and client capabilities are used by applications.
29. [b] The ACL domain of an object is the owner of the ACL of that object. Even though
dmadminis the commonly used name for the repository owner, the namedmadmindoesn't imply that it is repository owner. An ACL owned by the repository owner (dm_dbo) is available to all users.30. [a, d] Saving a search saves the search criteria. Running the saved search performs the search again and the result depends on the matching objects present at the time of performing the search.
31. [a, b, c, d] All of these are valid options. Subscribing to a document shows it under the Subscriptions node. A shortcut accesses a particular object, with a possible need for authentication. Objects linked to the default folder show up under Home Cabinet. An object ID uniquely identifies an object within a repository.
32. [d] These attributes are going to represent departments. Further, there is no information to indicate the need of any other attributes. So it should not use any type as a supertype and should be created as a NULL type.
33. [a, b, d] DocApps are managed using Documentum Application Builder.
34. [a]
35. [a]
36. [c] As of version 5.3, permission set templates cannot be created using Documentum Administrator.
37. [a, b] Lifecycle criteria are not enforced for the lifecycle owner and for users with Superuser privilege.
38. [a] Entry criteria are not evaluated when demoting an object in its lifecycle.
39. [c]
40. [c, d]
41. [c,d] The major versions are of the form x.0. The new version can be 7.0, if 6.0 is already present in the version tree.
42. [a, b, d]
43. [b, c]
r_version_labelis an exception to the rule that attributes with names prefixed withr_are read-only for users. The Content Server assigns an implicit version label and the CURRENT version label. Users can assign their own symbolic version labels.44. [d] Renditions cannot be edited or versioned.
45. [b, c]
46. [b, d] The type of an object can be changed to its supertype or subtype in one step. So the type of
test.doccan be changed frommy_documenttodm_documentin one step, and then fromdm_documenttomy_reportin another step.47. [a, b] Value assistance cannot be defined for
booleanattributes.48. [a, b, c]
49. [c] A virtual document can be of the type
dm_sysobjector its subtype other thandm_folderand its subtypes.50. [a, b]
51. [a, c]
52. [b] The Content Server recognizes alias references only in specific predefined attributes and in the argument of the
linkandunlinkDFC methods. See the chapter Aliases (Chapter 13) for more details.53. [a] The transition to an exception state is called suspension. Multiple normal states can use one exception state. The lifecycle resumes to the normal state from which it was suspended.
54. [b] John should mark himself unavailable and identify a proxy to work on his tasks. Once he is back, he can mark himself available again.
55. [a, b, c, d] All of these options are possible though some may depend on the configuration in the workflow template.
56. [a, b, c, d] Webtop honors client capability and Content Server enforces privileges, extended privileges, and permissions.
57. [a] Creating a DocApp requires Superuser privilege. There is no such thing as Create DocApp extended permission or extended privilege.
58. [c] The Content Server doesn't look for alias references in
object_name. The keywordLIKEuses the%symbol for pattern matching.59. [b, c, d]
60. [b] The version numbers are implicit labels and are assigned by the Content Server.
© 2007 Packt Publishing Limited All Rights ReservedAuthor (1)
