Microsoft Project Question Bank

website·Indexed 30 days ago

https://microsoft-project-wg8b.vercel.app/

A technical question bank for exam preparation and study, featuring Q&A, multiple-choice questions, and scenario-based exercises covering Azure Synapse Analytics, Azure SQL, .NET Core, DevOps project metrics, and resource configurations.

Tokens
14.1K
Snippets
27
Records
211
Agent score
67%

What's inside Microsoft Project Question Bank

  1. Collect detailed process data for Windows Server VMs

    To monitor baseline metrics and collect detailed data about processes running within the guest operating system of Azure virtual machines running Windows Server, deploy both the Azure Log Analytics agent and the Dependency agent.
  2. Optimize Azure Data Lake Storage Gen2 folder structures for security and performance

    To support fast queries and simplified folder security across services like Azure Databricks and Synapse serverless SQL pools, organize folders by subject area and date. This allows for security boundaries at the subject level and efficient partition pruning by date.
    /{SubjectArea}/{DataSource}/{YYYY}/{MM}/{DD}/{FileData}_{YYYY}_{MM}_{DD}.csv
  3. Handle truncation errors in Azure Data Factory data flows

    To proactively avoid truncation errors when inserting data from a CSV into an Azure Synapse Analytics dedicated SQL pool and ensure problematic rows are captured, use the following pattern:

    1. Add a Conditional Split transformation to separate rows that will cause truncation errors based on column length checks.
    2. Add a Sink transformation to write those specific error rows to a file in Azure Blob storage.
  4. Bypass branch policies in Azure DevOps

    To allow a specific user to merge changes to a branch (e.g., the master branch) even when a branch policy (such as a successful build requirement) is not met, modify the access control for that user within the Security settings of the branch.
  5. Overwrite partitions in Azure Synapse Analytics dedicated SQL pool

    To overwrite the content of a partition in a fact table (e.g., dbo.Sales) with content from a staging table (stg.Sales) that has matching definitions while minimizing load times, use the partition switch operation (Switch the partition from the target table to the staging table).
  6. Stream Azure SQL Database Query Store statistics to Log Analytics

    To send Query Store runtime statistics from an Azure SQL database to Azure Log Analytics for monitoring, configure the diagnostic settings of the database resource.
    1. Navigate to the Azure SQL database resource.
    2. Select 'Diagnostics settings'.
    3. Select 'Turn on diagnostics' (or 'Edit setting').
    4. Select 'Add diagnostic setting'.
    5. Provide a setting name.
    6. Select 'Send to Log Analytics' as the destination resource.
    7. Check the box for 'QueryStoreRuntimeStatistics' under database diagnostics log telemetry.
    8. (Optional) Check 'Basic metrics' for one-minute-based monitoring.
    9. Select Save.
  7. Collect crash reports and user feedback for mobile apps in Azure DevOps

    To collect crash reports for issue analysis, distribute beta releases to testers, and receive user feedback for Android and iOS apps managed via Azure DevOps, use the Microsoft Test & Feedback extension.
  8. Optimize Azure Synapse dedicated SQL pool storage for query performance

    When storing data in Azure Blob Storage to be read by an Azure Synapse Analytics dedicated SQL pool, use the Parquet file format to meet the following requirements:

    • Enable the pool to skip unnecessary columns and rows in a query (predicate pushdown/columnar storage).
    • Automatically create column statistics.
    • Minimize the overall size of files.
  9. Trigger photo processing for Azure Blob Storage uploads

    When designing a process to produce mobile-friendly versions of images uploaded to a General-purpose V2 Azure Storage Blob account with a requirement to start processing in less than one minute:

    • Converting the account to a BlockBlobStorage account does not inherently solve the triggering requirement.
    • Triggering processing directly from Blob storage events is a common pattern, though specific implementation details (like Event Grid) are required to meet strict latency goals.