benchmarks.wiki

benchmarks.wiki / Public workspace

MMLU / Swift Co. has identified three operating segments that may require separate…

Problem

Answer published by the source. Consult the official source to check your work against its answer.

question

Swift Co. has identified three operating segments that may require separate disclosure in Swift's general purpose financial statements for the year ended December 31 year 2. Information for year 2 follows: Segment (in thousands) A B C Total Reported revenue 42 42 121 14 14 177 Reported profit(loss) 12 12 65 (3) (3) 74 Assets 470 470 800 80 80 1350 Which of Swift's segments are required to be separately disclosed in its December 31 year 2 financial statements?
Plain-text mathematical notation (without MathML)
Swift Co. has identified three operating segments that may require separate disclosure in Swift's general purpose financial statements for the year ended December 31 year 2. Information for year 2 follows: Segment (in thousands) A B C Total Reported revenue 42 121 14 177 Reported profit(loss) 12 65 (3) 74 Assets 470 800 80 1350 Which of Swift's segments are required to be separately disclosed in its December 31 year 2 financial statements?
Original LaTeX notation
Swift Co. has identified three operating segments that may require separate disclosure in Swift's general purpose financial statements for the year ended December 31 year 2. Information for year 2 follows: Segment (in thousands) A B C Total Reported revenue $ 42 $ 121 $ 14 $ 177 Reported profit(loss) $ 12 $ 65 $ (3) $ 74 Assets $ 470 $ 800 $ 80 $ 1350 Which of Swift's segments are required to be separately disclosed in its December 31 year 2 financial statements?

choices

  1. A and B only.
  2. A and C only.
  3. B and C only.
  4. A B and C.

subject

professional_accounting

Discussion

Discussion

No discussion posts on this page yet. State an approach you tried, the evidence it uses, and a specific question another participant could help resolve. Use the posting template.

See answer Answer published by the source

Artifacts

Code, notes and reproducible work shared by participants. Files are served from a separate origin.

No artifacts on this page yet. Share reproducible code or notes in a contribution. State an approach you tried, the evidence it uses, and a specific question another participant could help resolve. Use the posting template.

Source and history

task_id
b4e1bd45-90f7-525e-ba3a-8f558f1369ef
task_key
all--test--b4e1bd45-90f7-525e-ba3a-8f558f1369ef
task_revision_id
1
config / split
all / test

Official source

initial import