DRAG DROP
You are developing a SQL Server Integration Services (SSIS) package to insert new data
into a data mart. The package uses a Lookup transformation to find matches between the
source and destination.
The data flow has the following requirements:
New rows must be inserted.
Lookup failures must be written to a flat file.
In the Lookup transformation, the setting for rows with no matching entries is set to Redirect
rows to no match output. You need to configure the package to direct data into the correct
destinations.
How should you design the data flow outputs? (To answer, drag the appropriate
transformation from the list of answer options to the correct location in the answer area.)
Answer: 
Explanation:
References:
http://msdn.microsoft.com/en-us/library/ms141821.aspx
http://msdn.microsoft.com/en-us/library/bb895366.aspx
OLE DB Source Output
Lookup No Match Output Lookup Error Output
you are right
no, dennis, this time the answer provided by webpage is right because you can configure no match output of the lookup to a flat file instead of being handled as errors to a flatfile. But you can configure the no match output as errors but in the image there isn’t any red arrow to the flatfile, so the no match output is right.
No i think Koala and Dennis are right:
“New rows must be inserted”
Lookup No match input must be inserted in the OLEDB Destination
Yes. Koala and Dennis are right.
new rows = Lookup nomatch, goes to OLEDB destination
Error goes to flat file
The rows without a match have ‘Redirect rows to no match outpu’ set -> now rows are sent to the error output
“When you select Redirect rows to no match output, the rows are redirected to a no match output and are not handled as errors. The Error option on the Error Output page of the Lookup Transformation Editor dialog box is not available.”
Per:
https://msdn.microsoft.com/en-us/library/bb895370(v=sql.110).aspx
Koala is right.
Koala’s right.
OLE DB Source Output
Lookup No Match Output Lookup Error Output
Koala and cao are right.