MicrosoftFree

Microsoft 98-361 Software Development Fundamentals Free Practice Test — 30 Questions

This practice bank exercises foundational knowledge across key software development domains tested in the Microsoft 98-361 exam. It covers software development methodologies (Agile, V-Model, Waterfall), project management concepts (triple constraint), coding techniques (abstraction, variable scope, time complexity), web technologies (RESTful APIs, OAuth 2.0, XSS mitigation), cloud service models (IaaS, PaaS, SaaS), testing strategies (unit, integration, system, performance, load), and DevOps practices (version control, blue-green deployment). Ethical considerations like data privacy and encryption key generation are also assessed. By working through these questions, learners reinforce their ability to analyze scenarios, identify best practices, and apply theoretical concepts to practical software development situations.

30
practice questions
20
recall cards
30
explanations
0
sign-ups required
Exam-focused analysis

What this Microsoft 98-361 Software Development Fundamentals practice set measures

This is an analysis of the practice bank, not a claim about the vendor's live exam blueprint. Use it to identify the knowledge, judgment, and recall patterns exercised here, then verify your coverage against the current official exam guide.

Development Methodologies and Project Management

This practice set assesses understanding of software development life cycle models and project management techniques. Questions explore Agile methodologies emphasizing iterative development and continuous feedback, the V-Model's verification and validation phases, and traditional Waterfall's linear approach. Scenario 9 compares Agile vs Traditional, while scenario 8 requires revisiting requirements in V-Model. Scenario 11 tests the project management triangle (time, cost, scope) with budget adjustments. These questions highlight the importance of adaptability, stakeholder engagement, and controlled changes in software projects.

  • Agile prioritizes iterative development and continuous feedback to adapt to changing requirements.
  • The V-Model requires updating earlier phases when new requirements emerge during implementation.
  • Project management involves balancing scope, time, and cost; altering one may necessitate adjustments to others.
  • Daily stand-up meetings enhance team alignment and communication in Agile environments.

Architecture and Cloud Computing

Questions 3, 10, 4, and 17 focus on architectural patterns and cloud service models. RESTful API design with proper HTTP methods and resource URIs is key for web development. Microservices architecture offers independent deployment and scalability compared to monolithic systems. Cloud service models are evaluated for minimizing management overhead: PaaS provides built-in scalability and development tools, while IaaS offers more control but requires more management. Understanding these models aids in selecting appropriate solutions for different workload requirements.

  • RESTful APIs use standard HTTP methods (GET, POST, PUT, DELETE) on unique resource URIs reflecting hierarchy.
  • Microservices enable independent scaling and deployment of services, supporting decentralized team ownership.
  • PaaS abstracts infrastructure management, providing scalable environments for application development and deployment.
  • IaaS offers virtualized computing resources but requires more administrative overhead.

Security and Ethics

Security vulnerabilities and ethical practices are examined through several scenarios. XSS attacks are illustrated by injecting malicious scripts via unsanitized user input; mitigation involves input validation and output encoding. Encryption key strength is enhanced using cryptographically secure random number generators rather than increasing key size alone. Ethical data collection under GDPR requires transparent practices and informed consent. OAuth 2.0 access token expiration principles ensure that expired tokens deny access, maintaining security through re-authentication. These topics emphasize proactive security measures and ethical responsibility.

  • XSS vulnerabilities are mitigated by input validation and output encoding to prevent script execution.
  • Encryption keys should be generated using CSPRNGs to ensure unpredictability and resistance to brute-force.
  • Ethical software development mandates transparent data collection and informed user consent.
  • OAuth 2.0 access tokens have limited validity periods; expired tokens require re-authentication.
  • Proper key management and secure random generation are critical for data protection.

Testing and DevOps Practices

The practice set covers a range of testing types and deployment strategies. Unit, integration, and system testing should be performed in that order to ensure component and system correctness. Performance testing (load testing) evaluates responsiveness under high concurrency. Blue-green deployment allows instant rollback by maintaining two identical environments. Version control systems integrated into IDEs help track changes and manage collaboration. Documentation must be regularly updated to remain relevant. These practices support software quality, reliability, and efficient team collaboration.

  • Testing sequence: Unit → Integration → System testing validates components, interactions, and overall functionality.
  • Load testing simulates multiple concurrent users to assess application performance under stress.
  • Blue-green deployment provides zero-downtime releases and immediate rollback capability.
  • Integrated version control in IDEs facilitates change tracking and conflict resolution among developers.
  • Documentation should be continuously updated and incorporate feedback from stakeholders.
Active recall deck

Practice Microsoft 98-361 Software Development Fundamentals with real flashcards

Read the prompt, commit to an answer, then flip the card. Move through the deck at your own pace and repeat any topic that does not come back quickly.

20 free cards

Card 1 of 20

1 reviewed this session

Static practice bank

Start the 30-question diagnostic

The complete question bank is embedded in this pre-rendered page. There is no database request or second content download when you begin.

Question 1 of 30

In a software development project, a team is using a version control system (VCS) to manage their codebase. They have a main branch called `main` and a feature branch called `feature-xyz`. After completing the feature, the team decides to merge `feature-xyz` into `main`. However, during the merge process, they encounter a conflict in a file called `config.json`. What is the most effective approach for resolving this conflict while ensuring that the integrity of the codebase is maintained and that the changes from both branches are preserved?

1 correct answers

Study workflow

Turn one Microsoft 98-361 Software Development Fundamentals attempt into a study plan

  1. 1

    Review Methodologies

    Study the differences between Agile, V-Model, and Waterfall. Focus on how each handles changing requirements. For Agile, emphasize iterative cycles and daily stand-ups. For V-Model, note the parallel testing phases. This will help answer questions about project flexibility and requirement management.

  2. 2

    Master Cloud Models

    Understand IaaS, PaaS, and SaaS. Know that PaaS provides a development platform with built-in scalability, IaaS gives virtual machines, and SaaS delivers ready-to-use software. Recognize scenarios where minimizing management overhead is crucial; PaaS is often the best fit.

  3. 3

    Practice Security Basics

    Study common web vulnerabilities like XSS. Know that input validation and output encoding are key defenses. Also understand encryption key generation using CSPRNGs. Recognize that increasing key size alone doesn't solve poor randomness. Review OAuth token expiration principles.

  4. 4

    Learn Testing Orders

    Memorize the standard testing sequence: unit, integration, system. Understand that performance testing includes load, stress, and endurance testing. Recognize that load testing is specifically for concurrent user simulation. Review the purpose of each testing phase.

  5. 5

    Apply Deployment Strategies

    Study blue-green deployment and its advantage of instant rollback. Also understand version control systems integrated into IDEs. Know that continuous documentation updates are vital. These DevOps practices ensure smooth releases and maintain codebase integrity.

FAQ

Questions about this exam practice page

Clear boundaries on what the bank covers, how to use it, and where official vendor information still matters.

How does the V-Model differ from Agile in handling requirement changes?+

The V-Model requires revisiting earlier phases to update documentation when new requirements arise, which can be time-consuming. Agile embraces changes through iterative cycles and continuous feedback, allowing faster adaptation. The exam may test your ability to select the appropriate model based on project constraints.

What is the primary benefit of using PaaS over IaaS for application development?+

PaaS eliminates the need to manage underlying infrastructure, offering built-in scalability and development tools. This allows developers to focus on coding rather than server maintenance. The 98-361 exam expects understanding of cloud service models and their appropriate use cases.

What is the correct sequence for functional testing phases in software development?+

The standard order is unit testing (individual components), integration testing (component interactions), and system testing (full application). This sequence ensures each level of functionality is validated before proceeding, a key concept for the 98-361 exam.

How does blue-green deployment minimize risk during software releases?+

It maintains two identical environments (blue and green). Traffic is switched to the new version in one environment, allowing instant rollback to the previous version if issues occur. This reduces downtime and risk, a DevOps practice relevant to the exam.

Why is output encoding important for preventing XSS attacks?+

Output encoding transforms dangerous characters (e.g., < >) into safe entities before rendering in the browser, preventing script execution. Input validation alone may be bypassed; encoding adds a second layer of defense. This is a critical security concept in web development.

Keep studying

Build the next review session

Browse another free bank or use the study strategy guide to turn your misses into spaced review.