Exam 70-487: Developing Microsoft Azure and Web Services Practice Test
Exam 70-487 practice focuses on developing Microsoft Azure and web services with .NET technologies. The practice bank samples implementation decisions across Entity Framework, ASP.NET Web API, and Windows Communication Foundation (WCF), including data access, request handling, service descriptions, and application startup. These topics connect service code to database behavior, HTTP conventions, and application lifecycle concerns.
Exam overview
About the Exam 70-487: Developing Microsoft Azure and Web Services Exam
The questions exercise practical choices developers make when building data-driven services. Entity Framework scenarios address transaction boundaries, schema evolution through migrations, and generating models and contexts from an existing database. Web API scenarios focus on validating model state, binding route and body values, checking request media types, applying shared request logic through message handlers, and enforcing role-based access. WCF material includes using service metadata to create client proxies. Together, these concepts require distinguishing responsibilities at the data, transport, and application-pipeline layers—for example, choosing a transaction for atomic database changes rather than relying on schema migration, or using a message handler for cross-cutting request behavior rather than controller-specific logic. The practice bank reflects these implementation scenarios; it should not be read as a statement of official exam coverage.
Sample Practice Questions
Review a selection from this exam's published US Practice Tests practice bank.
A service uses Entity Framework and needs to ensure that several database changes either all succeed or are all rolled back. What database concept should it use?
Show answer
Correct answer: AA transaction groups database operations into a unit that can commit together or roll back on failure, supporting atomicity. The other choices do not provide this all-or-nothing behavior.
A team wants Entity Framework to generate and apply database schema changes as its model evolves while preserving existing data where possible. Which feature is designed for this workflow?
Show answer
Correct answer: ACode First Migrations tracks model changes and provides migration operations that can update the database schema over time. The other options address logging, query shaping, or validation rather than schema evolution.
An ASP.NET Web API application needs to validate incoming model data and return the validation errors when the model is invalid. Which controller approach is appropriate?
Show answer
Correct answer: AASP.NET Web API model binding and validation populate ModelState. Checking ModelState.IsValid lets the controller reject invalid input and report validation errors rather than processing it.
An Entity Framework application uses a database-first workflow and needs to create entity classes and a context from an existing database schema. Which tool workflow is appropriate?
Show answer
Correct answer: ADatabase-first development can reverse engineer an existing database to create an Entity Framework model and corresponding classes. Migrations primarily support evolving a database from a code model, while the other options are unrelated.
An ASP.NET application needs to run initialization code once when the application domain starts. Which application lifecycle method is intended for this purpose in Global.asax?
Show answer
Correct answer: AApplication_Start runs when the ASP.NET application starts in its application domain, making it a suitable place for application-wide initialization such as registering routes or filters.
An ASP.NET Web API application needs to apply common logic to incoming requests before they reach controllers, such as adding a correlation identifier. Which component is designed for this pipeline-level work?
Show answer
Correct answer: BA delegating handler participates in the HTTP message pipeline and can inspect or modify requests and responses across routes. Action filters are associated with controller actions, while formatters handle representation conversion.
A developer wants to build a WCF client proxy from a service's published description. Which metadata format is commonly used to describe the service contract and endpoints?
Show answer
Correct answer: AWSDL describes web service operations, messages, and bindings, allowing tools to generate client proxies. CSS, XSLT, and YAML are not the standard WCF service-description format used for this purpose.
How to use this practice test
The free practice session draws up to 20 random questions from the available 70-487 bank. Submit answers to see results after the session, then use missed items to pinpoint concepts to revisit, such as Entity Framework transactions or Web API parameter binding. The bank contains 50 published questions.
Preparation tips
- Compare Entity Framework transactions with migrations: transactions protect a group of database operations, while migrations track and apply schema changes.
- Practice distinguishing database-first scaffolding from code-first schema workflows, including the roles of entity classes and the context.
- Trace a Web API request from routing and parameter binding through model validation; note when route values, body data, and Content-Type are involved.
- Review where to place cross-cutting request behavior in a message handler, and how role-based authorization differs from authentication.
- Work through WCF metadata and proxy generation so you can connect a service description to a client-side contract and endpoint.