Answer:
A. Liquidity management is a balancing act, managers try to find liquidity levels that are neither too high not too low.
Explanation:
Maintaining proper liquidity is an important financial objective of management. Proper liquidity management demands that an entity should be able to meet his short term financial obligation and making sure that liquid assets of the entity are not idle. In order to achieve this, the best way to go is to maintain a level that is neither too high and not too low. Not too high means the entity is not holding too much cash or liquid assets than it currently need to meet its short term financial obligation.
For example, not keeping too much cash in current account but investing them in interest-earning investment assets.
Not too low means the cash or liquid assets held by an entity should not less than the amount needed to meet its short term financial obligation. For example, making sure that the entity has enough cash or readily convertible liquid assets that can be used to pay vendors, rent, interest and meet other short term financial obligation.
Option B is false because keeping too much does not help to maximize short term earnings which is a feature of proper liquidity management. Option C is wrong because there is no guideline to support that deferring coupon payment won`t attract payment and this does not connote proper liquidity management.
Option D is obviously false and does not describe proper liquidity management.
Answer:
Based on selecting a sample of 300 computers The probability questions are follows
1. . What is the probability that no computer needs service within the warranty period?
2 . What is the probability that more than half of the computers that are sampled will need warranty period?
3. What is the expected number of computers fail before the warranty period?
Answer:
The correct answer is c) Common Terminology
Explanation:
NIMS establishes a common terminology to work cooperatively with other organizations in some emergency scenarios, this is used to avoid confusion.
The common terminology usually is implemented in Organizational Functions (named by standard names), Resource Descriptions (named by capabilities) and Incident Facilities (common terms for clarity in an incident)
