C1000-010 · Question #14
GoodCreditLoans is a financial company that wants to create an automated loan approval application. They currently have an application that uses hard-coded logic and manual checks to assess loan…
The correct answer is D. SalesReport E. MarketingContact. There appears to be an error in the listed correct answer. Based on the business rules provided, the actual correct answer should be A (Loan) and C (Applicant), not D and E. Why A and C are correct: Both harvested rules reference exactly two data points - "the amount of the…
Question
GoodCreditLoans is a financial company that wants to create an automated loan approval application. They currently have an application that uses hard-coded logic and manual checks to assess loan applications, generate payment reminders, send marketing emails to potential clients, and create monthly sales reports. The existing application uses these entities: MarketingContact. Equipment. Loan, Reminder. Applicant. SalesReport Here are some example rules harvested during rule discovery for the new automated loan approval application:
if the amount of the loan is less than $10,000,000.00 then the loan is rejected If the amount of the loan is equal to or more than $10,000,000.00 and the applicant's monthly salary is greater than $175,000.00 then the loan is accepted What two entities are needed to write the loan approval business rules?
Options
- ALoan
- BReminder
- CApplicant
- DSalesReport
- EMarketingContact
How the community answered
(52 responses)- A6% (3)
- B25% (13)
- C12% (6)
- D58% (30)
Explanation
There appears to be an error in the listed correct answer. Based on the business rules provided, the actual correct answer should be A (Loan) and C (Applicant), not D and E.
Why A and C are correct: Both harvested rules reference exactly two data points - "the amount of the loan" and "the applicant's monthly salary." These attributes belong to the Loan entity and the Applicant entity respectively, making them the only two entities needed to evaluate and execute the loan approval rules.
Why the others are wrong:
- B (Reminder) handles payment notifications after a loan is already processed - it plays no role in the approval decision itself.
- D (SalesReport) is an output/reporting entity generated monthly; it has no attributes relevant to evaluating loan eligibility.
- E (MarketingContact) is used for outbound marketing campaigns and has no connection to loan amounts or salary checks.
Memory tip: Follow the data trail in the rules. Each condition ("loan amount < X", "salary > Y") maps directly to an entity field - whatever entities own those fields are the ones you need. If an entity's attributes don't appear in the rule conditions, it's not required.
Note to you: Please double-check the source of this question. The stated correct answer (D, E) contradicts the rules given. This may be a typo or transcription error - A and C is almost certainly the intended answer.
Topics
Community Discussion
No community discussion yet for this question.