- Under Section 108, is Renata personally liable for the unpaid rent?
Answer: Yes, because Renata signed before formation and the lease did not expressly release her or state that she would not be personally liable.
When you see a pre-formation contract question, remember that the default rule is personal liability for the person signing on behalf of a not-yet-formed entity. The only escape is an express agreement to the contrary—knowledge or good faith alone doesn't cut it. Here, Renata signed before formation, and the lease never stated she would not be personally liable nor released her. Even though the landlord knew Juniper Creek was in formation, Section 108(c) requires both knowledge and an express agreement that Renata would not be personally liable. That didn't happen. Also, Juniper Creek's later adoption of the lease made the company liable, but Section 108(b) explicitly says adoption does not release the individual unless the other party expressly releases her. So Renata is personally liable for the unpaid rent.
Now, the wrong answers: "No, because the landlord knew when signing that Juniper Creek had not been formed and that Renata was acting as Managing Member" confuses mere knowledge with the required express release—knowledge alone is insufficient. "No, because Juniper Creek was formed and adopted the lease, making the company the party liable" overlooks that adoption adds liability but does not substitute for the individual's liability. "Yes, but only if the landlord can prove Renata intended to deceive" invents an intent element that the statute does not require; liability is strict unless the express agreement exists.
Your takeaway: For pre-formation contracts, ask two questions—Was there an express agreement to release the individual? Was there an express release after adoption? If either is missing, personal liability sticks.
- What is the maximum amount the Bank may recover from Priya?
Answer: $70,000, because the Bank's $90,000 claim is reduced to $70,000 by the company's remaining assets, and that is less than Priya's unpaid $120,000 contribution.
This question tests the narrow exception to LLC limited liability created by Section 403: a creditor who relies on a member's recorded contribution promise can enforce it directly, but only up to the amount the company's assets could not cover. Start with the statute's formula: the creditor recovers the lesser of (1) its unpaid claim after applying company assets, or (2) the member's unpaid contribution obligation.
The Bank's claim was $90,000, and Larkspur's remaining assets are $20,000, so the Bank's claim remaining unpaid is $70,000. Priya's unpaid contribution obligation is $120,000. The lesser amount is $70,000, so that is the maximum direct recovery.
The choice saying $0 confuses the general rule that LLC debts are the company's debts with the statute's explicit direct-enforcement exception; Section 403(c) exists precisely to allow reliance-based creditor recovery. The choice saying $20,000 wrongly treats company assets as the recovery amount or as a precondition to sue—actually, the assets are subtracted from the creditor's claim, and direct enforcement is allowed without first exhausting company assets. The choice saying $90,000 ignores the statutory offset for company assets; the creditor may not recover the full loan when $20,000 of it is still satisfiable from the company.
On similar questions, immediately identify the statutory cap and apply the "lesser of" calculation before comparing liabilities. Write out the arithmetic: unpaid claim minus company assets, then compare to the unpaid contribution promise.
- Is Deva liable under Section 204?
Answer: Yes, because Deva signed and caused the false certificate to be filed with knowledge of its falsity, and Lender reasonably relied on it.
Whenever you see a statutory cause of action like Section 204, your task is to apply its elements literally, not common-law assumptions about LLC liability. Here the elements are: a false statement in a filed record, signed or caused by the defendant, knowledge or notice of falsity, reasonable reliance, and loss. Deva satisfies each one: she signed the certificate, knew capital was $50,000 not $500,000 and debts existed, and Lender relied on that filed certificate to lend money. So Deva is personally liable.
The wrong answer that Deva signed only in a representative capacity misses the point: Section 204 imposes liability on the human being who signed or caused the filing knowing it was false; it does not require a personal guarantee. The answer claiming managers are never personally liable for LLC debts states the general rule, but this statute is an express exception creating personal liability for fraudulent filings. And the answer asserting strict liability regardless of knowledge is wrong because Section 204 explicitly requires knowledge or notice of falsity; subsection (b) confirms lack of knowledge is a defense.
Your study tip: when a statute is quoted in the question, read it as a checklist. Ask who signed, what they knew, and who relied. If all elements match, the answer is liability even if the defendant acted in a corporate or managerial role; the statute overrides that shield by its own terms.
- Does Section 304 bar Sam's claim against Perla?
Answer: No, because Section 304(c) preserves liability for the manager's own tortious conduct, and Perla's decisions to hire and retain Devon were her own conduct if a jury finds them negligent.
Whenever you see an LLC liability question, the key is to separate vicarious liability from direct personal fault. Section 304 shields members and managers from liability solely because of their status or solely for acts of another person, but it does not make them immune from their own torts.
Here, Sam is not suing Perla just because Devon ran a red light; Sam is suing her for negligently hiring and retaining Devon. The statute's subsection (c) explicitly preserves liability for a manager's own tortious conduct, including a failure to exercise reasonable care in hiring, training, or supervising an employee if the manager personally undertook that responsibility. Perla was personally responsible for hiring and supervision, knew about Devon's record, and hired him anyway. If a jury finds that was negligent, Section 304 does not bar the claim.
The first wrong answer, "Yes, because Devon, not Perla, committed the negligent act," mischaracterizes the claim as vicarious liability. Perla is being sued for her own conduct, not merely for Devon's. The second wrong answer, "Yes, because Perla was acting within the scope of her managerial duties," confuses scope of employment with statutory liability; acting within managerial duties does not erase personal tort liability. The third wrong answer, "No, because a manager is personally liable for every act… that creates a foreseeable risk," overstates the law—foreseeability alone does not create liability without a negligent breach of duty.
Study tip: classify whether the claim targets the owner's own behavior or someone else's. If the plaintiff alleges personal negligence in hiring or supervising, the LLC shield likely will not apply.
- Which issue is most likely to determine whether Nadia is personally liable?
Answer: Whether the loan agreement's definition of 'Borrower' made Nadia an individual co-borrower despite her representative signature
Whenever an LLC member tries to avoid a debt by citing ULLCA's member shield, remember that ULLCA protects members only from LLC obligations arising solely because of membership. It does not immunize them from obligations they voluntarily incur in an individual capacity. Here, the central dispute is contractual: the loan agreement defines "Borrower" as "Bramble LLC and Nadia, individually." That language makes Nadia a co-borrower even if the signature block reads "Bramble LLC, by Nadia, Member." A representative signature creates ambiguity, but the definition of "Borrower" is strong evidence of individual liability. So the most likely determinative issue is whether that definition made Nadia an individual co-borrower despite her representative signature.
"Whether First Bank extended credit in reliance on Nadia's membership" is not enough: reliance on membership alone does not create personal liability; ULLCA's shield still applies unless she separately promised to pay. "Whether Bramble was validly organized and in good standing" is also not decisive: a valid LLC does not prevent a member from being liable based on her own contract. "Whether the loan proceeds were used for Bramble's business rather than Nadia's personal expenses" could matter for alter-ego or veil-piercing theories, but it is not the central issue when the agreement itself defines Nadia as a borrower.
Strategy: on ULLCA questions, distinguish capacity. A signature as "Member" generally protects the member, but look for additional contract language, guarantees, or definitions creating individual obligation. The signature block is not conclusive.
- Under Hargrove, which statement best describes the Bank's claim?
Answer: The Bank may pierce if it proves both a unity of interest and that Marcus used a materially false financial statement to induce credit, so adherence to the separate entity would sanction fraud.
When you see an LLC veil-piercing question, start by isolating the jurisdiction's test. Here, Hargrove imposes two prongs: (1) unity of interest between owner and LLC, and (2) wrongful use such that honoring the separate entity would sanction fraud or injustice. The second prong demands more than insolvency; it requires fraudulent transfers, siphoning, or a materially false financial statement made to induce credit.
The Bank's claim succeeds only if it proves both prongs. Marcus's false balance sheet—claiming $250,000 cash when the LLC had $10,000 and $80,000 in debt—was exactly the kind of materially false representation Hargrove lists as satisfying the second prong. Combined with proof of unity from commingling and ignoring formalities, the Bank may pierce. That is why the answer describing proof of unity plus a false financial statement to induce credit is correct.
The choice saying Marcus's commingling and failure to hold meetings alone eliminated the separate existence is wrong: Hargrove expressly says those facts do not by themselves justify disregard. The choice saying the Bank cannot pierce because it assumed the risk of undercapitalization is also wrong—this is not mere undercapitalization or insolvency; it is fraud in inducing the loan. Finally, the choice saying Marcus acted only as manager and therefore cannot be liable misunderstands the rule: managers are not liable solely by status, but they remain liable for their own fraudulent conduct. The false balance sheet was his wrongful use of the LLC, so personal liability is available.
Study tip: on veil-piercing questions, ask whether the claimant alleges only status, thin capitalization, or informality—insufficient—versus affirmative misconduct like fraud or asset-stripping that makes the entity a shield for injustice.
- Which issue is most likely to determine whether Singh is personally liable?
Answer: Whether Singh knew his statement about flooding was false when he made it
Whenever you see an LLC member asserting the "corporate shield," remember: the LLC protects members from entity debts, not from liability for their own torts. ULLCA (2013) also says membership alone does not make a member an agent of the LLC. Here Singh is sued for fraudulent misrepresentation, so the central question is whether he had the required state of mind for fraud.
The issue most likely to determine personal liability is whether Singh knew his statement about flooding was false when he made it. That goes to scienter, an essential element of fraudulent misrepresentation. If Singh knowingly lied, he committed a tort, and acting on behalf of Vale does not immunize him. Limited liability never shields a wrongdoer from personal responsibility for his own misconduct.
The choice about whether Vale's managers authorized Singh to make representations is not the key: authorization might establish agency or apparent authority, but managers cannot authorize fraud, and authorization does not erase Singh's knowledge or intent.
The choice about whether Singh's membership interest gave him authority to speak for the LLC is also off. Under ULLCA, membership alone does not confer agency authority. Even if he had authority, that would not excuse his own fraudulent statement.
Finally, an as-is clause in the buyer's contract could affect reliance or damages, but it does not address whether Singh knowingly made a false statement—and fraud is not automatically waived by an as-is provision.
Study tip: when a defendant invokes LLC or corporate protection, ask whether the claim rests on the defendant's own tortious conduct. If it does, the shield is no defense.
- Which issue is most likely to determine whether Soto must return the distribution?
Answer: Whether Soto knew that the distribution was improper when he received it
When you see an LLC distribution paired with insolvency, your mind should immediately jump to the ULLCA's rules on improper distributions and the liability of the recipient. The key is that the statute does not punish members for their role in the decision—it punishes them for what they knew when they took the money.
Under ULLCA (2013) § 405, a member who receives a distribution knowing that it violates the Act (for instance, by rendering the LLC unable to pay its debts as they become due) is personally liable to return it. Soto received the $40,000 while knowing Fern was insolvent. He did not vote on the distribution, but that does not matter—the statute focuses exclusively on the recipient's state of mind at the moment of receipt. Therefore, the controlling issue is whether Soto knew the distribution was improper when he accepted it.
The distractor suggesting that Soto, as a non-manager member, owed a fiduciary duty to Fern's creditors is a classic trap—members owe fiduciary duties to the LLC and its members, not to creditors. The idea that the distribution must be proportional to his membership interest is irrelevant because the statute's liability trigger is knowledge, not proportionality. And the fact that the managing members approved the distribution in accordance with the operating agreement does not shield a knowing recipient; internal approval cannot cure a distribution that the recipient knows is improper.
Your takeaway: for improper distribution claims, always ask what did the recipient know and when did they know it? That knowledge, not their title or the voting procedure, is the deciding factor.
- What is the maximum amount Vale may recover from Tara and Neil?
Answer: $100,000 total from Tara and Neil, because the distribution was improper in that amount and Section 406(d) caps aggregate recovery at the amount of the improper distribution.
Whenever you see LLC distribution liability, check two things: whether the distribution was unlawful, and whether any statutory cap limits total recovery. Here, Kestrel's assets ($400,000) were already less than its liabilities ($500,000) before the transfer, so no distribution was lawful; the entire $100,000 paid to Neil was improper. Tara consented as manager, so she is liable under Section 406(a), and Neil received with knowledge, so he is liable under Section 406(b). Vale’s pre-distribution claim lets Vale enforce those liabilities because Kestrel is insolvent and has not sued. But Section 406(d) caps the total recovery from all persons at “the amount of the improper distribution”—$100,000. Therefore, Vale may recover no more than $100,000 total from Tara and Neil, not $100,000 each and not $300,000.
The wrong choices test common traps. "LLC debts are solely the LLC's" ignores the statute's explicit personal liability for improper distributions. "$200,000 total because Tara and Neil are separately liable” double-counts the same improper distribution and ignores the aggregate cap. “$300,000 because Vale's judgment remains unsatisfied" confuses the creditor's judgment against the company with the limited statutory liability for the unlawful distribution; Vale does not become a guarantor of all company debts. On exam day, remember: even when multiple people are liable for an improper distribution, the statute's cap means the creditor's recovery is limited to the unlawful distribution amount, not the full judgment.
- Which additional fact, if true, would most strongly support holding Ellis personally liable for the judgment?
Answer: Ellis regularly paid personal expenses from the LLC account and treated LLC assets as his own
When you see a question about LLC member liability under the ULLCA, start from the default rule: members are not personally liable for LLC obligations merely because they are members. To hold Ellis liable, you need a recognized exception—most commonly a personal guarantee, a direct tort, or corporate-veil-piercing/alter-ego liability. ULLCA also contains an important rule: the failure to observe formalities is not alone a ground for piercing.
Here, the strongest support is that Ellis regularly paid personal expenses from the LLC account and treated LLC assets as his own. That fact shows the LLC was used as an alter ego, blurring the line between member and entity—exactly what veil-piercing asks you to prove.
Why not the others? Ellis failing to hold formal member meetings or keep minutes is a trap: under ULLCA, informality is expressly insufficient to impose personal liability, so this fact actually helps Ellis. Thin capitalization can be a factor in some courts, but by itself it is not the strongest evidence of disregard; it must usually be combined with misuse or undercapitalization at inception plus injustice. And Ellis signing the contract only as Prism's member is the opposite of personal liability—that signature confirms he acted in a representative capacity, so the LLC, not Ellis, is bound.
Strategy: On LLC liability questions, separate "member status" from "misconduct." Look for facts showing the member personally guaranteed, personally committed a tort, or treated the entity as a sham—those justify piercing.
- Which legal issue is most directly raised by Second Bank's claim against Amari?
Answer: Whether a creditor that extended credit in reliance on a member's promised contribution can enforce that promise against the member
When you see a member of an LLC being sued by an outside creditor, separate two questions: Is the member personally liable simply because the LLC defaulted? No. But did the creditor rely on the member's enforceable promise to contribute capital? If so, ULLCA lets the creditor enforce that promise directly. Here, Cobalt obtained the bank's line of credit relying on Amari's operating-agreement commitment to contribute $100,000, and Amari contributed only $10,000. Amari did not need to sign a personal guarantee; under ULLCA, a promised contribution in a signed operating agreement can be enforced by a creditor who extended credit in reliance on it. That is the issue raised: whether the creditor can enforce the contribution promise.
The idea that Amari's promise had to be in a separate signed writing misses the point—the operating agreement itself is the signed record, and no separate guarantee is required. The argument that the bank must first obtain a judgment against Cobalt confuses ordinary entity-debt liability with the statutory right to enforce a member's contribution obligation; ULLCA permits direct enforcement by a relying creditor. Finally, treating the failure only as a breach of fiduciary duty to other members overlooks that the creditor's claim comes from the contribution promise itself, not from fiduciary harm among members. On exam, whenever a promised capital contribution and creditor reliance appear together, think direct enforceability against the member under ULLCA.
