File Info
| Exam | Managing and Maintaining IBM Lotus Notes and Domino 8.5 Environments |
| Number | C2040-926 |
| File Name | IBM.C2040-926.ActualTests.2019-04-15.43q.tqb |
| Size | 146 KB |
| Posted | Apr 15, 2019 |
| Download | IBM.C2040-926.ActualTests.2019-04-15.43q.tqb |
How to open VCEX & EXAM Files?
Files with VCEX & EXAM extensions can be opened by ProfExam Simulator.
Coupon: MASTEREXAM
With discount: 20%
Demo Questions
Question 1
Joe has configured the fault analyzer task to run on the server. He finds that the task is running as intended but the collection database has grown extremely large.
What can Joe do to reduce the size of the collection database?
- Make a backup copy of the collection database before deleting it and then recreate the collection database.
- Set maximum collection size for the collection database.
- Change “Remove diagnostic files after a specified number of days” to Yes
- Turn off diagnostic collection for clients only.
Correct answer: C
Question 2
Charlie is preparing an upgrade of the Notes clients and is testing the Smart Upgrade Tracking feature. When he tries to manually initiate a Smart Upgrade he
receives the error "File Does Not Exist".
What could be the cause of this error?
- The Smart Upgrade Tracking database is not named “Smart Upgrade Tracking”
- A Desktop Policy is not configured
- The id file is missing from the person document
- The Smart Upgrade Tracking database name is incorrect in the Desktop Policy
Correct answer: D
Explanation:
Question 3
Linda has configured a Smart Upgrade kit document to be used in conjunction with a desktop policy for tracking purposes. Her test user tries to run Smart Upgrade manually and reports they are getting a "no updates available dialog box and cannot complete the upgrade”. If Linda disables the policy, it works fine.
What should Linda check in the Smart Upgrade Kit document?
- The Destination version field in the Smart Upgrade kit document matches the Deploy version in the Desktop Settings document
- The upgrade deadline in the desktop policy document has expired
- A kit description is specified
- The desktop policy name is defined properly in the kit document
Correct answer: A
