Answer to Question 1
TRUE
Answer to Question 2
A use case is defined by one primary actor, one useful goal, and one system. In other words, if a use case has more than one strong candidate for primary actor, or aims at more than one (complete) useful goal, or models the behavior of more than one system or subsystem, it must be broken into more than one use case.
There are, however, other reasons for dividing use cases or joining them wholly or partially: A use case may become too complex to understand and manage, or the discovery of common functionality among multiple use cases may require that reusable use cases be created. The mechanisms of extend and include are then used to relate separated or recombined use cases back together.
A use case may be divided vertically by consolidating parallel steps within a use case into another use case, or horizontally by taking out a set of steps. Refactoring is a special case of horizontal division in which a set of steps common to multiple use cases are extracted and joined.