Skip Navigation Links
 

Microsoft - AZ-303: Microsoft Azure Architect Technologies

Sample Questions

Question: 239
Measured Skill: Implement solutions for apps (10-15%)

You need to use an Azure logic app to receive a notification when an administrator modifies the settings of a virtual machine in a resource group named RG1.

You create an Azure Logic App.

Which three components should you create next in the Logic Apps Designer?

(To answer, move the appropriate components from the list of components to the answer area and arrange them in the correct order.)

www.cert2brain.com

ASequence: 4, 1, 2
B Sequence: 5, 1, 2
C Sequence: 4, 3, 2
D Sequence: 5, 3, 2

Correct answer: A

Explanation:

To monitor and respond to specific events that happen in Azure resources or third-party resources, you can automate and run tasks as a workflow by creating a logic app that uses minimal code. These resources can publish events to an Azure event grid. In turn, the event grid pushes those events to subscribers that have queues, webhooks, or event hubs as endpoints. As a subscriber, your logic app can wait for those events from the event grid before running automated workflows to perform tasks.

For example, here are some events that publishers can send to subscribers through the Azure Event Grid service:

  • Create, read, update, or delete a resource. For example, you can monitor changes that might incur charges on your Azure subscription and affect your bill.

  • Add or remove a person from an Azure subscription.

  • Your app performs a particular action.

  • A new message appears in a queue.

We have to:

  • Create a logic app that monitors events from an event grid.
  • Add a condition that specifically checks for virtual machine changes.
  • Send email when your virtual machine changes.



Reference: Tutorial: Monitor virtual machine changes by using Azure Event Grid and Logic Apps



Question: 240
Measured Skill: Implement solutions for apps (10-15%)

You have an app named App1 that reads messages from an Azure Service Bus queue. App1 has the following requirements:
  • Messages must be processed in the order in which they are received.
  • No message is to remain in a Service Bus queue named Queue1 for longer than 14 days.
  • Messages that cannot be delivered must be retained until they are reviewed, and then manually deleted.
You need to create Queue1.

Which two settings should you modify for Queue1?

(To answer, select the appropriate settings in the answer area. NOTE: Each correct selection is worth one point.)

www.cert2brain.com

AMessage time to live
B Lock duration
C Enable auto-delete on idle queue
D Enable duplicate detection
E Enable dead lettering on message expiration
F Enable sessions

Correct answer: E, F

Explanation:

Azure Service Bus queues and topic subscriptions provide a secondary subqueue, called a dead-letter queue (DLQ). The dead-letter queue doesn't need to be explicitly created and can't be deleted or managed independent of the main entity.

The purpose of the dead-letter queue is to hold messages that can't be delivered to any receiver, or messages that couldn't be processed. Messages can then be removed from the DLQ and inspected. An application might, with help of an operator, correct issues and resubmit the message, log the fact that there was an error, and take corrective action.

From an API and protocol perspective, the DLQ is mostly similar to any other queue, except that messages can only be submitted via the dead-letter operation of the parent entity. In addition, time-to-live isn't observed, and you can't dead-letter a message from a DLQ. The dead-letter queue fully supports peek-lock delivery and transactional operations.

There's no automatic cleanup of the DLQ. Messages remain in the DLQ until you explicitly retrieve them from the DLQ and complete the dead-letter message.

Microsoft Azure Service Bus sessions enable joint and ordered handling of unbounded sequences of related messages. Sessions can be used in first in, first out (FIFO) and request-response patterns. To realize a FIFO guarantee in Service Bus, use sessions. 

References:

Overview of Service Bus dead-letter queues

Message sessions



Question: 241
Measured Skill: Implement solutions for apps (10-15%)

You are developing a workflow solution using Azure technologies.

What should you implement to meet each requirement?

(To answer, select the appropriate options in the answer area. NOTE: Each correct selection is worth one point.)

www.cert2brain.com

ADebug the solution by using Visual Studio: Durable functions only
Use a collection of ready-made actions: Logic Apps only
Deploy the component by using Visual Studio Team Services: Durable functions only
B Debug the solution by using Visual Studio: Durable functions only
Use a collection of ready-made actions: Durable functions and Logic Apps
Deploy the component by using Visual Studio Team Services: Durable functions and Logic Apps
C Debug the solution by using Visual Studio: Logic Apps only
Use a collection of ready-made actions: Durable functions only
Deploy the component by using Visual Studio Team Services: Logic Apps only
D Debug the solution by using Visual Studio: Logic Apps only
Use a collection of ready-made actions: Durable functions and Logic Apps
Deploy the component by using Visual Studio Team Services: Durable functions only
E Debug the solution by using Visual Studio: Durable functions and Logic Apps
Use a collection of ready-made actions: Durable functions and Logic Apps
Deploy the component by using Visual Studio Team Services: Logic Apps only
F Debug the solution by using Visual Studio: Durable functions and Logic Apps
Use a collection of ready-made actions: Durable functions only
Deploy the component by using Visual Studio Team Services: Logic Apps only

Correct answer: A

Explanation:

Durable Functions is an extension of Azure Functions that lets you write stateful functions in a serverless compute environment. The extension lets you define stateful workflows by writing orchestrator functions and stateful entities by writing entity functions using the Azure Functions programming model. Behind the scenes, the extension manages state, checkpoints, and restarts for you, allowing you to focus on your business logic.

The primary use case for Durable Functions is simplifying complex, stateful coordination requirements in serverless applications.

Durable Functions currently supports the following languages:

  • C#: both precompiled class libraries and C# script.
  • JavaScript: supported only for version 2.x of the Azure Functions runtime. Requires version 1.7.0 of the Durable Functions extension, or a later version.
  • Python: requires version 2.3.1 of the Durable Functions extension, or a later version.
  • F#: precompiled class libraries and F# script. F# script is only supported for version 1.x of the Azure Functions runtime.
  • PowerShell: support for Durable Functions is currently in public preview. Supported only for version 3.x of the Azure Functions runtime and PowerShell 7. Requires version 2.2.2 of the Durable Functions extension, or a later version. Only the following patterns are currently supported: Function chaining, Fan-out/fan-in, Async HTTP APIs.

Azure Logic Apps is a cloud service that helps you schedule, automate, and orchestrate tasks, business processes, and workflows when you need to integrate apps, data, systems, and services across enterprises or organizations. Logic Apps simplifies how you design and build scalable solutions for app integration, data integration, system integration, enterprise application integration (EAI), and business-to-business (B2B) communication, whether in the cloud, on premises, or both.

For example, here are just a few workloads you can automate with logic apps:

  • Process and route orders across on-premises systems and cloud services.

  • Send email notifications with Office 365 when events happen in various systems, apps, and services.

  • Move uploaded files from an SFTP or FTP server to Azure Storage.

  • Monitor tweets for a specific subject, analyze the sentiment, and create alerts or tasks for items that need review.

To build enterprise integration solutions with Azure Logic Apps, you can choose from a growing gallery with hundreds of ready-to-use connectors, which include services such as Azure Service Bus, Azure Functions, Azure Storage, SQL Server, Office 365, Dynamics, Salesforce, BizTalk, SAP, Oracle DB, file shares, and more. Connectors provide triggers, actions, or both for creating logic apps that securely access and process data in real time.

References:

What are Durable Functions?

What is Azure Logic Apps?



Question: 242
Measured Skill: Implement management and security solutions (25-30%)

You are a DevOp for your company. You have an Azure subscription.

You are planning data security for Azure resources.

You need to ensure that the data meets the following requirements:
  • Data in Azure SQL databases that is at rest, in transit, and in use must be encrypted.
  • The confidentiality of code on virtual machines must be protected while the code is being processed.
Which feature should you use for each requirement?

(To answer, select the appropriate options in the answer area. NOTE: Each correct selection is worth one point.)

www.cert2brain.com

ASQL databases: Advanced data security
Virtual machine code: Azure Container Service
B SQL databases: Always Encrypted
Virtual machine code: Azure Batch
C SQL databases: Always Encrypted
Virtual machine code: Azure Confidential Compute
D SQL databases: Elastic Pools
Virtual machine code: Azure Disk Encryption
E SQL databases: Transparent Data Encryption (TDE)
Virtual machine code: Azure Confidential Compute
F SQL databases: Transparent Data Encryption (TDE)
Virtual machine code: Azure Disk Encryption

Correct answer: C

Explanation:

Transparent data encryption (TDE) and Always Encrypted are two different encryption technologies offered by SQL Server and Azure SQL Database. While TDE encrypted data is decrypted in Azure SQL database prior to send the data to a client, Always Encrypted encrypted data is decrypted by the client application.

Confidential computing is an industry term defined by the Confidential Computing Consortium (CCC) - a foundation dedicated to defining and accelerating the adoption of confidential computing. The CCC defines confidential computing as: The protection of data in use by performing computations in a hardware-based Trusted Execution Environment (TEE).

A TEE is an environment that enforces execution of only authorized code. Any data in the TEE can't be read or tampered with by any code outside that environment.

Azure confidential computing allows you to leverage confidential computing capabilities in a virtualized environment. You can now use tools, software, and cloud infrastructure to build on top of secure hardware.

Prevent unauthorized access: Run sensitive data in the cloud. Trust that Azure provides the best data protection possible, with little to no change from what gets done today.

Regulatory compliance: Migrate to the cloud and keep full control of data to satisfy government regulations for protecting personal information and secure organizational IP.

Secure and untrusted collaboration: Tackle industry-wide work-scale problems by combing data across organizations, even competitors, to unlock broad data analytics and deeper insights.

Isolated processing: Offer a new wave of products that remove liability on private data with blind processing. User data cannot even be retrieved by the service provider.

Note: Azure provides a special VM size for confidential computing.

References:

Transparent data encryption or always encrypted?

Confidential computing on Azure



Question: 243
Measured Skill: Implement solutions for apps (10-15%)

You are developing an Azure Function that will be triggered using a webhook from an external application. The Azure Function will receive JSON data in the body of the request.

Calling applications send an account ID as part of the URL. The number at the end of the URL is an integer. The format for the URL resembles the following: /api/account/1

The Azure Function must accept all incoming requests without requiring keys or token.

You need to complete the attributes for the Azure Function.

How should you complete the code?

(To answer, select the appropriate options in the answer area. NOTE: Each correct selection is worth one point.)

www.cert2brain.com

AP1: QueueTrigger
P2: FileTrigger
P3: Function
P4: /api/account/1
P5: [FromBody] string accountId
B P1: FunctionName
P2: HttpTrigger
P3: Anonymous
P4: /account/
P5: int accountId
C P1: HttpTrigger
P2: BlobTrigger
P3: User
P4: account/{accountId:int}
P5: string accountId
D P1: RouteAttribute
P2: QueueTrigger
P3: Anonymous
P4: ProcessItem/{accountId:int}
P5: int account

Correct answer: B

Explanation:

The HTTP trigger lets you invoke a function with an HTTP request. You can use an HTTP trigger to build serverless APIs and respond to webhooks.

The following article describes most of the settings and values used to implement Azure Functions HTTP trigger.

Azure Functions HTTP trigger



 
Tags: exam, examcollection, exam simulation, exam questions, questions & answers, training course, study guide, vce, braindumps, practice test
 
 

© Copyright 2014 - 2021 by cert2brain.com