Which of the following workspace types also have a contract request? Note: There are 2 correct answers to this question

• A.Amendment
• B.Procurement (Missed)
• C.Internal
• D.Sales (Missed)

Comment: *

Name: *

Email: *

Verification: *

In the standard deployment description for contracts, what is the maximum number of custom contract header fields your customer ...

• A.Up to 10 customs fields
• B.Up to 15 customs fields
• C.Up to 5 customs fields
• D.Up to 3 customs fields

Comment: *

Name: *

Email: *

Verification: *

You need to create contract workspaces using the legacy load process. Which CSV file must the customer populate?

• A.Contracts.csv
• B.ContractTeam.csv
• C.ContractDocuments.csv
• D.ContractLoad.csv

Comment: *

Name: *

Email: *

Verification: *

During deployment, you use the customer's test realm to build the initial configuration. How do you use the test realm after deployment?

• A.Validate user master data in the test realm
• B.Apply changes to templates in the test realm first and then export/import the templates to the production realm
• C.Publish a template in the test realm to automatically update the production realm template
• D.Perform all updates in the production realm

Comment: *

Name: *

Email: *

Verification: *

Which of the following are the guidelines for the Hierarchical Type header field and the legacy contract upload? Note: There are 3 correct answers to this question

• A.Place master agreements before sub-agreements (Missed)
• B.Parent agreements must be loaded before the sub-agreement (Missed)
• C.Hierarchical Type is an optional field on the legacy upload
• D.A sub-agreement must be loaded in a separate zip file with no master agreements (Missed)
• E.You can add a sub-agreement to a sub-agreement

Comment: *

Name: *

Email: *

Verification: *