MCSD Developing Windows Azure and Web Services v1.0 (70-487)

Page:    1 / 14   
Total 198 questions

Overview -
Trey Research Inc. is a Software-as-a-Service (SaaS) company that provides hosted solutions for business partners around the world. The company is developing a solution that will allow business partners to manage events, including shareholder meetings and trade shows.
You hold meetings with key partners to identify requirements and constraints for the solution. You must minimize costs where possible.
You work with an Azure solutions architect to design the logical structure for the solution. The solution will use the following architecture:



Solution components -
The solution will use Azure Traffic Manager to distribute traffic. The solution will use API Management to provide caching for the Event Service. Partner companies will interact with the solution by using the Event Service API. This API will be implemented as an ASP.NET Core Web API that runs as an Azure Web App. Event data will be stored in Cosmos DB using the Document API.
The solution will be highly available. You define regional Azure outages as periods of 60 seconds or more where the Event Service is not available.
An Azure WebJob named EventJob will be deployed with the Event Service Web App. The WebJob:
Creates new computed events when partner events are created.

Must be active whenever the Event Service is running.
Is updated once a quarter.
Trey Research Inc. has developer teams that work with a variety of operating systems including Windows, Linux, and MacOS.

Event Service -
Individual events must be immutable. Event data can be up to 800 kilobytes (KB) in size. The Event Service must meet the following requirements:
Use REST-based design
Cache data whenever possible.
Support both JSON and XML-based data.
Log customer information whenever data is modified.
Include the X-Customer header in all calls to identify the partner.
Regional access to the Event Service API
Data for partners in Germany and Brazil must be served from Azure datacenters in their respective geographies unless there is a regional Azure outage. All other partners must use the US West Azure datacenter.

Testing -
All testing must interact directly with the Web App backend. Automated testing of the solution is performed using a remote third-party testing solution.

Event data -
You identify the following requirements for the event data store:
Each partner’s event data must be stored in a Collection that is specific to the partner.
Event data must be available if a regional Azure outage occurs.
Event read and write operations for a single partner must always store events in the correct order.

Event API -
Relevant portions of the app files are shown below. Line numbers are included for reference only and include a two-character prefix that denotes the specific file to which they belong.





Event processing -
Relevant portions of the app files are shown below. Line numbers are included for reference only and include a two-character prefix that denotes the specific file to which they belong.


Relevant portions of the app files are shown below. Line numbers are included for reference only and include a two-character prefix that denotes the specific file to which they belong.



Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.
You need to ensure that testing, development, and end user access requirements are met.
Solution: Move the Web App backend to a private VNet.
Does the solution meet the goal?

  • A. Yes
  • B. No


Answer : A

Explanation:
Scenario: All testing must interact directly with the Web App backend. Automated testing of the solution is performed using a remote third-party testing solution.

Overview -
Trey Research Inc. is a Software-as-a-Service (SaaS) company that provides hosted solutions for business partners around the world. The company is developing a solution that will allow business partners to manage events, including shareholder meetings and trade shows.
You hold meetings with key partners to identify requirements and constraints for the solution. You must minimize costs where possible.
You work with an Azure solutions architect to design the logical structure for the solution. The solution will use the following architecture:



Solution components -
The solution will use Azure Traffic Manager to distribute traffic. The solution will use API Management to provide caching for the Event Service. Partner companies will interact with the solution by using the Event Service API. This API will be implemented as an ASP.NET Core Web API that runs as an Azure Web App. Event data will be stored in Cosmos DB using the Document API.
The solution will be highly available. You define regional Azure outages as periods of 60 seconds or more where the Event Service is not available.
An Azure WebJob named EventJob will be deployed with the Event Service Web App. The WebJob:
Creates new computed events when partner events are created.

Must be active whenever the Event Service is running.
Is updated once a quarter.
Trey Research Inc. has developer teams that work with a variety of operating systems including Windows, Linux, and MacOS.

Event Service -
Individual events must be immutable. Event data can be up to 800 kilobytes (KB) in size. The Event Service must meet the following requirements:
Use REST-based design
Cache data whenever possible.
Support both JSON and XML-based data.
Log customer information whenever data is modified.
Include the X-Customer header in all calls to identify the partner.
Regional access to the Event Service API
Data for partners in Germany and Brazil must be served from Azure datacenters in their respective geographies unless there is a regional Azure outage. All other partners must use the US West Azure datacenter.

Testing -
All testing must interact directly with the Web App backend. Automated testing of the solution is performed using a remote third-party testing solution.

Event data -
You identify the following requirements for the event data store:
Each partner’s event data must be stored in a Collection that is specific to the partner.
Event data must be available if a regional Azure outage occurs.
Event read and write operations for a single partner must always store events in the correct order.

Event API -
Relevant portions of the app files are shown below. Line numbers are included for reference only and include a two-character prefix that denotes the specific file to which they belong.





Event processing -
Relevant portions of the app files are shown below. Line numbers are included for reference only and include a two-character prefix that denotes the specific file to which they belong.


Relevant portions of the app files are shown below. Line numbers are included for reference only and include a two-character prefix that denotes the specific file to which they belong.



Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.
You need to ensure that testing, development, and end user access requirements are met.
Solution: Secure the Web App backend by using Azure Active Directory (Azure AD).
Does the solution meet the goal?

  • A. Yes
  • B. No


Answer : B

Explanation:
Instead, move the Web App backend to a private VNet.
Scenario: All testing must interact directly with the Web App backend. Automated testing of the solution is performed using a remote third-party testing solution.

Overview -
Trey Research Inc. is a Software-as-a-Service (SaaS) company that provides hosted solutions for business partners around the world. The company is developing a solution that will allow business partners to manage events, including shareholder meetings and trade shows.
You hold meetings with key partners to identify requirements and constraints for the solution. You must minimize costs where possible.
You work with an Azure solutions architect to design the logical structure for the solution. The solution will use the following architecture:



Solution components -
The solution will use Azure Traffic Manager to distribute traffic. The solution will use API Management to provide caching for the Event Service. Partner companies will interact with the solution by using the Event Service API. This API will be implemented as an ASP.NET Core Web API that runs as an Azure Web App. Event data will be stored in Cosmos DB using the Document API.
The solution will be highly available. You define regional Azure outages as periods of 60 seconds or more where the Event Service is not available.
An Azure WebJob named EventJob will be deployed with the Event Service Web App. The WebJob:
Creates new computed events when partner events are created.

Must be active whenever the Event Service is running.
Is updated once a quarter.
Trey Research Inc. has developer teams that work with a variety of operating systems including Windows, Linux, and MacOS.

Event Service -
Individual events must be immutable. Event data can be up to 800 kilobytes (KB) in size. The Event Service must meet the following requirements:
Use REST-based design
Cache data whenever possible.
Support both JSON and XML-based data.
Log customer information whenever data is modified.
Include the X-Customer header in all calls to identify the partner.
Regional access to the Event Service API
Data for partners in Germany and Brazil must be served from Azure datacenters in their respective geographies unless there is a regional Azure outage. All other partners must use the US West Azure datacenter.

Testing -
All testing must interact directly with the Web App backend. Automated testing of the solution is performed using a remote third-party testing solution.

Event data -
You identify the following requirements for the event data store:
Each partner’s event data must be stored in a Collection that is specific to the partner.
Event data must be available if a regional Azure outage occurs.
Event read and write operations for a single partner must always store events in the correct order.

Event API -
Relevant portions of the app files are shown below. Line numbers are included for reference only and include a two-character prefix that denotes the specific file to which they belong.





Event processing -
Relevant portions of the app files are shown below. Line numbers are included for reference only and include a two-character prefix that denotes the specific file to which they belong.


Relevant portions of the app files are shown below. Line numbers are included for reference only and include a two-character prefix that denotes the specific file to which they belong.



You need to configure the WebJob.
What should you do?

  • A. Set the type to Triggered. Set the Scale to Single Instance.
  • B. Set the type to Continuous. Set the Scale to Multiple Instance.
  • C. Set the type to Triggered. Set the Scale to Multiple Instance.
  • D. Set the type to Continuous. Set the Scale to Single Instance.


Answer : A

Explanation:
Scenario: An Azure WebJob named EventJob will be deployed with the Event Service Web App. The WebJob:
-> Creates new computed events when partner events are created.
-> Must be active whenever the Event Service is running.
Triggered WebJobs Starts only when triggered manually or on a schedule. Runs on a single instance that Azure selects for load balancing.
References:
https://docs.microsoft.com/en-us/azure/app-service/webjobs-create

Overview -
Trey Research Inc. is a Software-as-a-Service (SaaS) company that provides hosted solutions for business partners around the world. The company is developing a solution that will allow business partners to manage events, including shareholder meetings and trade shows.
You hold meetings with key partners to identify requirements and constraints for the solution. You must minimize costs where possible.
You work with an Azure solutions architect to design the logical structure for the solution. The solution will use the following architecture:



Solution components -
The solution will use Azure Traffic Manager to distribute traffic. The solution will use API Management to provide caching for the Event Service. Partner companies will interact with the solution by using the Event Service API. This API will be implemented as an ASP.NET Core Web API that runs as an Azure Web App. Event data will be stored in Cosmos DB using the Document API.
The solution will be highly available. You define regional Azure outages as periods of 60 seconds or more where the Event Service is not available.
An Azure WebJob named EventJob will be deployed with the Event Service Web App. The WebJob:
Creates new computed events when partner events are created.

Must be active whenever the Event Service is running.
Is updated once a quarter.
Trey Research Inc. has developer teams that work with a variety of operating systems including Windows, Linux, and MacOS.

Event Service -
Individual events must be immutable. Event data can be up to 800 kilobytes (KB) in size. The Event Service must meet the following requirements:
Use REST-based design
Cache data whenever possible.
Support both JSON and XML-based data.
Log customer information whenever data is modified.
Include the X-Customer header in all calls to identify the partner.
Regional access to the Event Service API
Data for partners in Germany and Brazil must be served from Azure datacenters in their respective geographies unless there is a regional Azure outage. All other partners must use the US West Azure datacenter.

Testing -
All testing must interact directly with the Web App backend. Automated testing of the solution is performed using a remote third-party testing solution.

Event data -
You identify the following requirements for the event data store:
Each partner’s event data must be stored in a Collection that is specific to the partner.
Event data must be available if a regional Azure outage occurs.
Event read and write operations for a single partner must always store events in the correct order.

Event API -
Relevant portions of the app files are shown below. Line numbers are included for reference only and include a two-character prefix that denotes the specific file to which they belong.





Event processing -
Relevant portions of the app files are shown below. Line numbers are included for reference only and include a two-character prefix that denotes the specific file to which they belong.


Relevant portions of the app files are shown below. Line numbers are included for reference only and include a two-character prefix that denotes the specific file to which they belong.




DRAG DROP -
You need to implement event storage isolation and consistency.
Which settings should you use? To answer, drag the appropriate values to the correct operations. Each value may be used once, more than once, or not at all.
You may need to drag the split bar between panes or scroll to view content.
Each correct selection is worth one point.
NOTE:
Select and Place:



Answer :

Explanation:
Scenario: Individual events must be immutable. Event data will be stored in Cosmos DB using the Document API.

Box 1: Strong -
Strong: Strong consistency offers a linearizability guarantee. The reads are guaranteed to return the most recent committed version of an item. A client never sees an uncommitted or partial write. Users are always guaranteed to read the latest committed write.

Box 2: Strong -
Strong: Strong consistency offers a linearizability guarantee. The reads are guaranteed to return the most recent committed version of an item. A client never sees an uncommitted or partial write. Users are always guaranteed to read the latest committed write.

Box 3: Consistent -
Azure Cosmos DB supports two indexing modes:
Consistent: If a container's indexing policy is set to Consistent, the index is updated synchronously as you create, update or delete items. This means that the consistency of your read queries will be the consistency configured for the account.
None: If a container's indexing policy is set to None, indexing is effectively disabled on that container. This is commonly used when a container is used as a pure key-value store without the need for secondary indexes. It can also help speeding up bulk insert operations.
References:
https://docs.microsoft.com/en-us/azure/cosmos-db/index-policy

Overview -
Trey Research Inc. is a Software-as-a-Service (SaaS) company that provides hosted solutions for business partners around the world. The company is developing a solution that will allow business partners to manage events, including shareholder meetings and trade shows.
You hold meetings with key partners to identify requirements and constraints for the solution. You must minimize costs where possible.
You work with an Azure solutions architect to design the logical structure for the solution. The solution will use the following architecture:



Solution components -
The solution will use Azure Traffic Manager to distribute traffic. The solution will use API Management to provide caching for the Event Service. Partner companies will interact with the solution by using the Event Service API. This API will be implemented as an ASP.NET Core Web API that runs as an Azure Web App. Event data will be stored in Cosmos DB using the Document API.
The solution will be highly available. You define regional Azure outages as periods of 60 seconds or more where the Event Service is not available.
An Azure WebJob named EventJob will be deployed with the Event Service Web App. The WebJob:
Creates new computed events when partner events are created.

Must be active whenever the Event Service is running.
Is updated once a quarter.
Trey Research Inc. has developer teams that work with a variety of operating systems including Windows, Linux, and MacOS.

Event Service -
Individual events must be immutable. Event data can be up to 800 kilobytes (KB) in size. The Event Service must meet the following requirements:
Use REST-based design
Cache data whenever possible.
Support both JSON and XML-based data.
Log customer information whenever data is modified.
Include the X-Customer header in all calls to identify the partner.
Regional access to the Event Service API
Data for partners in Germany and Brazil must be served from Azure datacenters in their respective geographies unless there is a regional Azure outage. All other partners must use the US West Azure datacenter.

Testing -
All testing must interact directly with the Web App backend. Automated testing of the solution is performed using a remote third-party testing solution.

Event data -
You identify the following requirements for the event data store:
Each partner’s event data must be stored in a Collection that is specific to the partner.
Event data must be available if a regional Azure outage occurs.
Event read and write operations for a single partner must always store events in the correct order.

Event API -
Relevant portions of the app files are shown below. Line numbers are included for reference only and include a two-character prefix that denotes the specific file to which they belong.





Event processing -
Relevant portions of the app files are shown below. Line numbers are included for reference only and include a two-character prefix that denotes the specific file to which they belong.


Relevant portions of the app files are shown below. Line numbers are included for reference only and include a two-character prefix that denotes the specific file to which they belong.




DRAG DROP -
You need to configure settings to identify regional outages.
Which values should you use? To answer, drag the appropriate values to the correct settings. Each value may be used once, more than once, or mot at all. You may need to drag the split bar between panes or scroll to view content.
Each correct selection is worth one point.
NOTE:
Select and Place:



Answer :

Explanation:

Box 1, Probing interval: 10 -
Probing Interval. This value specifies how often an endpoint is checked for its health from a Traffic Manager probing agent. You can specify two values here: 30 seconds (normal probing) and 10 seconds (fast probing). If no values are provided, the profile sets to a default value of 30 seconds.
Box 2: Tolerated Number of Failures: 3
Tolerated Number of Failures. This value specifies how many failures a Traffic Manager probing agent tolerates before marking that endpoint as unhealthy. Its value can range between 0 and 9. A value of 0 means a single monitoring failure can cause that endpoint to be marked as unhealthy. If no value is specified, it uses the default value of 3.
Scenario: Regional access to the Event Service API
Data for partners in Germany and Brazil must be served from Azure datacenters in their respective geographies unless there is a regional Azure outage. All other partners must use the US West Azure datacenter.
The solution will be highly available. You define regional Azure outages as periods of 60 seconds or more where the Event Service is not available.
References:
https://docs.microsoft.com/en-us/azure/traffic-manager/traffic-manager-monitoring

Overview -
Trey Research Inc. is a Software-as-a-Service (SaaS) company that provides hosted solutions for business partners around the world. The company is developing a solution that will allow business partners to manage events, including shareholder meetings and trade shows.
You hold meetings with key partners to identify requirements and constraints for the solution. You must minimize costs where possible.
You work with an Azure solutions architect to design the logical structure for the solution. The solution will use the following architecture:



Solution components -
The solution will use Azure Traffic Manager to distribute traffic. The solution will use API Management to provide caching for the Event Service. Partner companies will interact with the solution by using the Event Service API. This API will be implemented as an ASP.NET Core Web API that runs as an Azure Web App. Event data will be stored in Cosmos DB using the Document API.
The solution will be highly available. You define regional Azure outages as periods of 60 seconds or more where the Event Service is not available.
An Azure WebJob named EventJob will be deployed with the Event Service Web App. The WebJob:
Creates new computed events when partner events are created.

Must be active whenever the Event Service is running.
Is updated once a quarter.
Trey Research Inc. has developer teams that work with a variety of operating systems including Windows, Linux, and MacOS.

Event Service -
Individual events must be immutable. Event data can be up to 800 kilobytes (KB) in size. The Event Service must meet the following requirements:
Use REST-based design
Cache data whenever possible.
Support both JSON and XML-based data.
Log customer information whenever data is modified.
Include the X-Customer header in all calls to identify the partner.
Regional access to the Event Service API
Data for partners in Germany and Brazil must be served from Azure datacenters in their respective geographies unless there is a regional Azure outage. All other partners must use the US West Azure datacenter.

Testing -
All testing must interact directly with the Web App backend. Automated testing of the solution is performed using a remote third-party testing solution.

Event data -
You identify the following requirements for the event data store:
Each partner’s event data must be stored in a Collection that is specific to the partner.
Event data must be available if a regional Azure outage occurs.
Event read and write operations for a single partner must always store events in the correct order.

Event API -
Relevant portions of the app files are shown below. Line numbers are included for reference only and include a two-character prefix that denotes the specific file to which they belong.





Event processing -
Relevant portions of the app files are shown below. Line numbers are included for reference only and include a two-character prefix that denotes the specific file to which they belong.


Relevant portions of the app files are shown below. Line numbers are included for reference only and include a two-character prefix that denotes the specific file to which they belong.



You need to ensure that computed events are processed correctly.
What should you do?

  • A. Move the WebJob to a different App Service plan.
  • B. Select a deployment slot for the WebJob.
  • C. Disable WebJobs during deployments.
  • D. Create an additional upgrade domain.


Answer : B

Explanation:
Scenario: An Azure WebJob named EventJob will be deployed with the Event Service Web App. The WebJob:
-> Creates new computed events when partner events are created.
-> Must be active whenever the Event Service is running.
-> Is updated once a quarter.
References:
https://stackify.com/azure-deployment-slots/

You are developing a library to support multiple ASP.NET MVC web applications on a shared server. The library provides implementations of security algorithms.
If a problem with any of the security algorithms is discovered, a new version of the library must be created and deployed. Application downtime during the update must be minimized.
You need to ensure that the new version of the library will be used by all applications as soon as possible.
What should you do?

  • A. Build the web applications and include the security assembly as an embedded resource. When an update is needed, copy the new assembly to the bin directory for the application.
  • B. Sign all assemblies in each application with the same key used to sign the security assembly. When an update is needed, create a new key pair and re-sign all assemblies.
  • C. Build the security assembly as a netmodule in a shared location. Use the assembly linker to merge the netmodule into the assemblies for the application. When an update is needed, update the netmodule in the shared location.
  • D. Install the security assembly in the Global Assembly Cache (GAC). When an update is needed, update the assembly in the GAC.


Answer : D

You are developing an application in Visual Studio 2012 to display student information. The application contains the following Entity Framework model.



The application contains a WCF data service named DirectoryService.svc.
You need to create a query expression to display all of the grades for students whose first name is "John"
How should you build the expression?

  • A. http://localhost:54946/DirectoryService.svc/Students?$filter=FirstName eq 'John' &$expand=Grades
  • B. http://localhost:54946/DirectoryService.svc/Students?$filter=FirstName eq 'John'/Grades
  • C. http://localhost:54946/DirectoryService.svc/Students?$filter=FirstName = 'John' &$expand=Grades
  • D. http://localhost:54946/DirectoryService.svc/Grades/Students?$filter=FirstName eq 'John' A


Answer : Explanation

DRAG DROP -
You are developing a WCF Data Services service in Visual Studio to display movie information from a SQL Server database that changes every 24 hours. The service is defined in the following class.


The application contains the following Entity Framework model.

The service must only return data for movies that are currently in theaters.
You need to add a method to the MovieService class to filter the data.
How should you build the method? (To answer, drag the appropriate code segments to the correct location or locations in the answer area. Each code segment may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.)
Select and Place:



Answer :

Explanation:
Query interceptor methods, which are called when processing an HTTP GET request, must return a lambda expression that determines whether an instance of the interceptor's entity set should be returned by the query results. This expression is used by the data service to further refine the requested operation. The following is an example definition of a query interceptor.
// Define a query interceptor for the Orders entity set.
[QueryInterceptor("Orders")]
public Expression<Func<Order, bool>> OnQueryOrders()
References:
https://docs.microsoft.com/en-us/dotnet/framework/data/wcf/interceptors-wcf-data-services

You are developing an ASP.NET MVC application that reads and writes data from a SQL Server database.
You need to prevent the application from reading data that is locked by other transactions. You also need to prevent exclusive range locks.
Which isolation level should you use?

  • A. ReadCommitted
  • B. Serializable
  • C. Repeatable
  • D. ReadUncommitted


Answer : A

DRAG DROP -
You are developing a Windows Azure based web application that provides users the ability to rent training videos. The application is deployed to hosted services in Asia and Europe.
The web application must meet the following requirements:
-> Video files are large and must be able to be streamed.
-> Streaming videos requires low latency network connections.
-> Rental data contains structured information about the user and the video.
-> Rental permissions are checked every five seconds during video playback.
You need to recommend a storage architecture for the application.
What should you do? (To answer, drag the appropriate technologies to the correct location or locations in the answer area. Each technology may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.)
Select and Place:




Answer :

DRAG DROP -
You are developing a self-hosted WCF service that returns stock market information.
The service must be discoverable by any client application. You need to build the service host.
How should you build the host? (To answer, drag the appropriate code segments to the correct location or locations in the answer area. Each code segment may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.)
Select and Place:




Answer :

You are developing a WCF service that compares several data sources. The service takes a long time to complete.
The service must meet the following requirements:
-> The client must be able to continue processing while the service is running.
-> The service must initiate communication with the client application when processing is complete.
You need to choose a message pattern to meet the requirements.
Which message pattern should you choose?

  • A. One Way
  • B. Streaming
  • C. Duplex
  • D. Request/Reply


Answer : C

DRAG DROP -
You are developing a WCF service.
You need to implement transport security by using NTLM authentication and NetTcpBindings.
You have the following markup:


Which configuration values should you include in Target 1, Target 2, and Target 3 to complete the markup? (To answer, drag the appropriate configuration values to the correct location or locations in the answer area. Each configuration value may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.)
Select and Place:



Answer :

You are developing a WCF service.
A new service instance must be created for each client session.
You need to choose an instancing mode.
Which instance mode should you use?

  • A. PerCall
  • B. Single
  • C. Multiple
  • D. PerSession
  • E. PerRequest D


Answer : Explanation

Explanation:
PerSession: A new InstanceContext (and therefore service object) is created for each new client session and maintained for the lifetime of that session (this requires a binding that supports sessions).

Incorrect: Answers -
A: PerCall: A new InstanceContext (and therefore service object) is created for each client request.
B: Single: A single InstanceContext (and therefore service object) handles all client requests for the lifetime of the application.
References:
https://msdn.microsoft.com/en-us/library/ms731193(v=vs.110)

Page:    1 / 14   
Total 198 questions