Add link to Data DevOps article and clarify that data ingestion is not covered by this article

Author: tcare

docs/reference-architectures/ai/mlops-python.md

@@ -61,7 +61,9 @@ The CI pipeline gets triggered every time code is checked in. It publishes an up
 
 - **Unit test.** These tests make sure the code works, has adequate code coverage, and is stable.
 
-- **Data test.** These tests verify that the data samples conform to the expected schema and distribution. Customize this test for other use cases and run it as a separate data sanity pipeline that gets triggered as new data arrives. For example, move the data test task to a data ingestion pipeline so you can test it earlier.
+- **Data test.** These tests verify that the data samples conform to the expected schema and distribution. Customize this test for other use cases and run it as a separate data sanity pipeline that gets triggered as new data arrives. For example, move the data test task to a *data ingestion pipeline* so you can test it earlier.
+
+**Note:** CI/CD concepts for data ingestion pipelines are not covered in this article. For more information on the architecture and best practices for CI/CD of a data ingestion pipeline, see [DevOps for a data ingestion pipeline](https://docs.microsoft.com/en-us/azure/machine-learning/how-to-cicd-data-ingestion).
 
 The following one-time tasks occur when setting up the infrastructure for Azure Machine Learning and the Python SDK: