hardMultiple ChoiceObjective-mapped

PL-900 Practice Question: Is configuring a custom connector in Power…

Exhibit

Refer to the exhibit.

{
  "type": "Microsoft.PowerApps/apis",
  "apiVersion": "2020-10-01",
  "properties": {
    "displayName": "Salesforce Connector",
    "backendService": {
      "serviceUrl": "https://login.salesforce.com",
      "endpoint": "https://instance.salesforce.com/services/data/v52.0"
    },
    "connectionParameters": {
      "token": {
        "type": "oauthSetting",
        "oAuthSettings": {
          "flow": "accessCode",
          "clientId": "3MVG9lKcPoNINVB",
          "scopes": ["api", "refresh_token"]
        }
      }
    }
  }
}

An organization is configuring a custom connector in Power Automate to connect to Salesforce. The exhibit shows a snippet of the connector definition. However, when attempting to test the connection, the authentication fails. What is the most likely cause?

⚠ Common exam trap

Candidates often assume 'accessCode' is a valid OAuth flow type because it appears in some third-party documentation or older samples, but the PL-900 exam expects the exact OAuth 2.0 standard term 'authorizationCode' as used in Power Automate custom connector definitions.

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 OAuth flow type is incorrectly set to 'accessCode' instead of 'authorizationCode'.

The OAuth 2.0 flow type 'accessCode' is not a valid OAuth 2.0 grant type. The correct value for the authorization code grant type is 'authorizationCode'. Power Automate custom connectors require this exact string to properly initiate the OAuth 2.0 authorization code flow with Salesforce. Using 'accessCode' causes the authentication handshake to fail because the connector cannot map the flow to a supported OAuth grant.

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 OAuth flow type is incorrectly set to 'accessCode' instead of 'authorizationCode'.
Why this is correct
The correct OAuth flow for authorization code is 'authorizationCode'.
✗
The scopes array is missing the 'id' scope.
Why it's wrong here
The scopes listed are sufficient for OAuth.
✗
The apiVersion is not supported by Power Automate.
Why it's wrong here
2020-10-01 is a valid API version for custom connectors.
✗
The serviceUrl should point to the Salesforce instance, not login.salesforce.com.
Why it's wrong here
login.salesforce.com is the correct URL for the OAuth authorization endpoint.

Go deeper

PL-900 Practice Question: Is configuring a custom connector in Power…

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question