Which two statements are true about using the @testSetup annotation in an Apex test class? Choose 2 answers

Records created within a `@testSetup` method can indeed be updated, deleted, or manipulated by individual test methods, as each test method operates on its own independent copy of the setup data.

The `@testSetup` annotation cannot be used in conjunction with the `@IsTest(SeeAllData=true)` annotation because `@testSetup` is designed for creating controlled, isolated test data, which conflicts with `SeeAllData=true`'s purpose of exposing all existing organization data.

Test data created by a `@testSetup` method is inserted into the database only once at the beginning of the entire test class execution, not once for each test method, which optimizes performance by reducing DML operations.

Although a method defined with the `@testSetup` annotation physically executes only once per test class, Salesforce effectively provides each individual test method in that class with a fresh copy of the data created by the `@testSetup` method. This ensures test method isolation, as changes made in one test method do not persist for subsequent test methods.