โ† All PL 400 Flashcard Decks

Plugin Development Flashcards

7 cards from real PL 400 practice questions. Tap to flip, then mark Knew It or Still Learning โ€” missed cards come back until you master them.

Read the first 7 Plugin Development flashcards as text
  1. A plugin must update related records without triggering its own registered step again. What technique prevents an infinite loop?

    Answer: Check context.Depth and exit if greater than 1

    Checking context.Depth > 1 allows the plugin to detect recursive calls and exit early, breaking the loop.

  2. What is the correct way to retrieve the IOrganizationService instance inside a plugin's Execute method?

    Answer: serviceProvider.GetService(typeof(IOrganizationServiceFactory)) then CreateOrganizationService

    You resolve IOrganizationServiceFactory from the IServiceProvider, then call CreateOrganizationService(context.UserId) to get a correctly scoped service.

  3. Which attribute on an entity image registration controls which fields are included in the snapshot?

    Answer: ImageAttributes

    ImageAttributes specifies the comma-separated list of logical field names included in the pre/post image snapshot.

  4. A plug-in developer uses context.SharedVariables to pass data between two plugins in the same pipeline execution. What is the correct data type for values stored there?

    Answer: Only primitive types (int, bool, string, DateTime, Guid)

    SharedVariables is a ParameterCollection that only supports primitive types supported by the Dataverse serialization layer.

  5. When a plugin is registered on the Associate message, which entity is represented in context.InputParameters['Target']?

    Answer: An EntityReference pointing to the target entity

    For the Associate message, Target is an EntityReference for the primary record, and RelatedEntities holds the associated records.

  6. Which Power Platform tool provides a command-line interface to register and update plugin assemblies without using the GUI Plugin Registration Tool?

    Answer: pac plugin push

    The Power Platform CLI command 'pac plugin push' automates plugin assembly registration directly from the terminal.

  7. A developer registers a plugin on the Create message of the Account entity with Filter Attributes set to 'name,accountnumber'. When will the plugin fire?

    Answer: Filter Attributes are ignored on Create; they only apply to Update

    Filter Attributes are only evaluated for Update messages; on Create, the plugin fires for every create regardless of filter settings.