Option D is a type of risk transfer, but it doesn't necessarily involve sharing the risk with another party. A code escrow agreement is typically used to protect a software development project by ensuring that the source code is held in trust by a third party.
D. Engaging in a code escrow agreement
In a code escrow agreement, the source code of a software application is deposited with a third-party escrow agent. If the software vendor fails to meet certain obligations, such as maintaining the software or providing support, the source code can be released to the licensee. By engaging in a code escrow agreement, the risk associated with reliance on the software vendor is shared between the vendor and the licensee. If the vendor fails to fulfill its obligations, the licensee has access to the source code, mitigating the risk of dependency on the vendor.
upvoted 2 times
...
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
Sara98
1 month, 2 weeks agoSara98
1 month, 3 weeks agoBaddest
7 months, 3 weeks ago