Exam 70-357: Developing Mobile Apps Practice Test
Exam 70-357: Developing Mobile Apps covers software development decisions for mobile applications, from responsive interfaces to local data and network-dependent behavior. The available practice material touches on Xamarin.Forms interactions, offline caching, push notifications, storage choices, accessibility, and app security. These scenarios connect implementation choices to practical needs such as keeping forms usable across orientations and protecting user-generated content.
Exam overview
About the Exam 70-357: Developing Mobile Apps Exam
Mobile development work requires coordinating the user interface with device capabilities and remote services. Practice scenarios address binding a Xamarin.Forms control to application logic, adapting layouts when orientation changes, and supporting larger accessibility text without making controls unreachable. Other examples involve choosing storage for reproducible files, refreshing cached server data after connectivity returns, and handling concurrent edits when a server rejects a locally updated record. Security and reliability decisions include safely rendering user input, evaluating third-party image-decoding libraries for production, and selecting a notification mechanism for delivery when an app is inactive. A business-rule calculation, such as a cart discount, can be tested independently of the device interface and network with a unit test. These tasks reflect the practical judgment involved in building mobile apps that remain usable, secure, and consistent across changing device and connectivity conditions.
Sample Practice Questions
Review a selection from this exam's published US Practice Tests practice bank.
A mobile app caches a server response to support offline use. What should it do when connectivity returns and cached data may be stale?
Show answer
Correct answer: BOffline caching requires a strategy for reconciling local and server state, such as refreshing data or resolving conflicts according to the app's rules. Cached data should not be assumed to remain current indefinitely.
A mobile app stores a locally generated file that can be recreated by downloading it again. The device is running low on storage. Where is this file most appropriately kept?
Show answer
Correct answer: ARegenerable data is a good fit for cache storage, which the platform or app can clear when space is needed. Important user-created data should instead be stored in a more durable location with appropriate backup and retention behavior.
A mobile app uses a third-party library to decode images. What is a good practice when selecting the library for a production app?
Show answer
Correct answer: BDependency selection should consider legal, compatibility, maintenance, and security factors. Popularity alone does not guarantee that a package is safe, supported, or suitable for the app's requirements.
A mobile app displays a user-generated comment that may contain markup-like characters. Which approach best avoids interpreting that content as executable or unintended markup?
Show answer
Correct answer: ARendering untrusted content through a text API treats it as data instead of markup. Building UI markup from raw user input risks unintended interpretation and injection-like behavior.
A mobile app supports portrait and landscape orientations. A screen contains a form whose controls must remain reachable in both orientations. Which implementation choice is most appropriate?
Show answer
Correct answer: AA scrollable, adaptable layout keeps controls accessible when the available vertical space changes. Fixed coordinates and assumptions about a single orientation are brittle across rotation and device sizes.
A mobile app should receive a notification even when it is not actively open. Which mechanism is generally intended for this use?
Show answer
Correct answer: APlatform push notification services can deliver notifications to an app that is not currently active, subject to user settings and platform delivery policies. A continuously running foreground loop is not a reliable or battery-friendly substitute.
In a Xamarin.Forms app, a developer wants a visual control to invoke logic when the user taps it. Which approach best separates the UI interaction from the page’s code-behind?
Show answer
Correct answer: ACommand binding lets a view model expose an ICommand that the UI can invoke, supporting separation of presentation and interaction logic. Styles and resource dictionaries describe reusable UI configuration, not event-handling behavior.
How to use this practice test
The free practice bank contains 50 questions; each session presents up to 20 selected at random. Complete a session to see your results, then use missed or uncertain items to identify which implementation decisions need closer review.
Preparation tips
- Trace how an app should reconcile cached data after connectivity returns, and distinguish stale reads from server-side conflicts caused by concurrent edits.
- Compare local storage choices for durable user data versus files that can be regenerated, including the impact of low device storage.
- For Xamarin.Forms interface scenarios, consider command or binding patterns, orientation-responsive layouts, and whether controls remain usable with larger accessibility text.
- Review mobile security choices for untrusted user-generated text and third-party libraries, including safe rendering and production maintenance considerations.
- Separate business-rule tests from UI and network dependencies; identify when a unit test can verify calculations such as a cart discount.