Secure, monitor, and optimize data storage and data processing →mediumMultiple ChoiceObjective-mapped

DP-203 Practice Question: Secure, monitor, and optimize data storage and data processing

Exhibit

Refer to the exhibit.
{
  "name": "CopyDataPipeline",
  "properties": {
    "activities": [
      {
        "name": "CopyFromBlobToSQL",
        "type": "Copy",
        "inputs": [{"referenceName": "BlobInput", "type": "DatasetReference"}],
        "outputs": [{"referenceName": "SQLOutput", "type": "DatasetReference"}],
        "typeProperties": {
          "source": {
            "type": "BlobSource"
          },
          "sink": {
            "type": "SqlSink",
            "sqlWriterStoredProcedureName": "usp_InsertData",
            "sqlWriterTableType": "dbo.InsertType",
            "storedProcedureParameters": {
              "Param1": {
                "value": "value1"
              }
            }
          }
        }
      }
    ]
  }
}

You are reviewing an Azure Data Factory pipeline JSON that copies data from Azure Blob Storage to Azure SQL Database using a stored procedure. The pipeline fails with a 'Parameter supplied for object is not valid' error. What is the most likely cause?

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

The stored procedure parameters are not mapped to source columns.

The error 'Parameter supplied for object is not valid' in a copy activity using a stored procedure typically indicates that the stored procedure is expecting parameters that are not being provided correctly. The most common cause is that the source columns in the copy activity are not mapped to the stored procedure parameters. Option C is correct because the pipeline JSON likely lacks the necessary parameter mapping from source columns to stored procedure input parameters. Option A is incorrect because BlobSource is valid for Azure Blob Storage. Option B is incorrect because the error is about parameter supply, not the existence of a table type. Option D is incorrect because the error relates to parameter mapping, not dataset references.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✗
The source type 'BlobSource' is not compatible with Azure Blob Storage.
Why it's wrong here
BlobSource is a valid source type for Azure Blob Storage in Data Factory, so this is not the cause.
✗
The SQL table type 'dbo.InsertType' does not exist.
Why it's wrong here
The error is about parameters being supplied incorrectly, not about the existence of a SQL table type.
✓
The stored procedure parameters are not mapped to source columns.
Why this is correct
When using a stored procedure as a sink, source columns must be explicitly mapped to the stored procedure parameters. If this mapping is missing or incorrect, the 'Parameter supplied for object is not valid' error occurs.
✗
The dataset references are incorrect.
Why it's wrong here
While incorrect dataset references can cause issues, the specific error message points to a parameter issue, not dataset names.

Quick reference

Azure Blob Storage Tier Comparison

Tier	Storage Cost	Retrieval Cost	Latency	Use Case
Hot	Highest	Lowest	Immediate	Active data, frequent reads
Cool	Lower	Higher	Immediate	Data accessed < once / month
Cold	Lower still	Higher	Immediate	Data accessed < once / quarter
Archive	Lowest	Highest + rehydration delay	Hours	Long-term compliance retention

Go deeper

DP-203 Practice Question: Secure, monitor, and optimize data storage and data processing

Exhibit

Why each option matters

Option-by-option breakdown

Azure Blob Storage Tier Comparison

Related to this question