Which statement about the combination of fatal and non-fatal errors during duplication is accurate?

Which statement about the combination of fatal and non-fatal errors during duplication is accurate?

• A. All errors must be fixed before duplication.
• B. Non-fatal errors must be fixed; fatal errors can be skipped.
• C. Non-fatal errors can be skipped regardless of impact.
• D. Fatal errors must be fixed; non-fatal errors can be skipped if they do not impact the final build.

Answer: (D)

The main idea here is how to handle errors by severity during duplication. Fatal errors block the process because they indicate a problem that would make the duplicated artifact unusable or incomplete, so they must be fixed before proceeding. Non-fatal errors are less serious—they’re like warnings or minor issues that don’t necessarily prevent a usable result. If those issues don’t affect the final build, you can skip them to complete the duplication. This approach ensures you don’t waste time fixing things that won’t impact the delivered product, while still requiring fixes for problems that would broke the output. So, fatal errors must be fixed; non-fatal errors can be skipped if they do not impact the final build.

The main idea here is how to handle errors by severity during duplication. Fatal errors block the process because they indicate a problem that would make the duplicated artifact unusable or incomplete, so they must be fixed before proceeding. Non-fatal errors are less serious—they’re like warnings or minor issues that don’t necessarily prevent a usable result. If those issues don’t affect the final build, you can skip them to complete the duplication. This approach ensures you don’t waste time fixing things that won’t impact the delivered product, while still requiring fixes for problems that would broke the output. So, fatal errors must be fixed; non-fatal errors can be skipped if they do not impact the final build.