View Full Microsoft SC-100 Exam Dumps and Practice Test Dumps
Question 61
An organization wants to replace several overlapping security products with a platform that provides integrated endpoint detection, identity protection, email security, and cloud application signals. Which architectural approach should be considered?
- Security consolidation through an integrated XDR platform
- Separate unmanaged security products
- Perimeter-only monitoring
- Independent endpoint logging
Correct Answer: 3
Explanation
An integrated XDR architecture can consolidate security signals from multiple domains and provide correlated detection and investigation capabilities. This can reduce duplicated functionality, improve visibility, and simplify security operations when appropriately designed. The goal is not simply to reduce the number of products but to create effective coverage and integration across security domains. Separate unmanaged tools can produce fragmented visibility, while perimeter-only monitoring misses activity occurring on endpoints, identities, cloud services, and applications.
Question 62
Which architectural capability helps an organization establish a common security policy framework while allowing individual business units to retain appropriate operational autonomy?
- Centralized governance with delegated administration
- Completely independent security policies
- Universal administrator access
- Unmanaged local security controls
Correct Answer: 1
Explanation
Centralized governance with delegated administration allows an organization to establish common security requirements while giving appropriate teams authority over resources within their responsibilities. This model can improve consistency without requiring a single team to perform every administrative task. Completely independent policies can create inconsistent protection, while universal administrator access violates least privilege. Unmanaged local controls can also create visibility and compliance gaps. Effective security architecture balances centralized standards with controlled delegation according to organizational structure and risk.
Question 63
A company wants to ensure that security policies continue to meet regulatory requirements after applications are moved to the cloud. Which architectural activity is most important?
- Compliance and regulatory requirements mapping
- Removing audit logging
- Disabling cloud governance
- Allowing unrestricted data movement
Correct Answer: 1
Explanation
Compliance and regulatory requirements mapping identifies the obligations that apply to systems, data, users, and business processes and translates them into architectural requirements. Moving workloads to the cloud does not automatically remove regulatory responsibilities. Architects should determine applicable requirements for data protection, retention, access, auditing, residency, and other areas. Removing logs or allowing unrestricted data movement can make compliance more difficult. Mapping requirements early helps ensure that cloud architecture incorporates appropriate governance and security controls.
Question 64
Which design consideration is particularly important when selecting where sensitive organizational data should be stored?
- Data residency and regulatory requirements
- Monitor size
- User desktop wallpaper
- Keyboard layout
Correct Answer: 1
Explanation
Data residency and regulatory requirements can determine where certain information may be stored, processed, or transferred. Security architects should identify applicable laws, contractual obligations, industry requirements, and organizational policies before selecting storage locations. These requirements can influence cloud regions, service configurations, encryption, access controls, and data-management processes. Monitor size, wallpaper, and keyboard layout have no meaningful relationship to data residency. Incorporating regulatory requirements into architecture early can prevent costly redesigns and reduce compliance risk.
Question 65
An organization wants to ensure that a compromised application cannot directly communicate with every other workload. Which architectural control should be emphasized?
- Microsegmentation
- Flat network connectivity
- Shared service accounts
- Universal firewall permissions
Correct Answer: 1
Explanation
Microsegmentation creates smaller security boundaries around workloads, applications, or services and allows communication to be restricted according to defined requirements. This can reduce lateral movement and limit the impact of a compromised workload. Flat connectivity and universal firewall permissions allow broader communication, increasing the potential attack surface. Shared service accounts can also expand the consequences of credential compromise. Microsegmentation is particularly useful in modern cloud and hybrid architectures because it can enforce granular communication policies closer to the workload.
Question 66
Which security architecture capability provides protection against unauthorized changes to critical cloud infrastructure configurations?
- Configuration governance and change control
- Anonymous administrative access
- Permanent unrestricted permissions
- Disabling audit records
Correct Answer: 1
Explanation
Configuration governance and change control help ensure that important infrastructure modifications are authorized, reviewed, tracked, and monitored. This can include policy enforcement, configuration baselines, approval processes, and auditing. Unauthorized configuration changes can weaken security controls or expose sensitive resources, so maintaining visibility over changes is an important architectural requirement. Anonymous administration and permanent unrestricted permissions increase risk, while disabling audit records removes evidence needed to investigate changes. Governance should cover both cloud and on-premises infrastructure where applicable.
Question 67
A security architect needs to design protection for an application that processes payment information. Which architectural principle should be applied first?
- Identify the data and business risk that require protection
- Select a security product based only on popularity
- Allow unrestricted application access
- Remove all application logging
Correct Answer: 1
Explanation
The architecture should begin by identifying the information being processed, its sensitivity, business importance, applicable requirements, and potential consequences of compromise. Payment information may require stronger controls for identity, encryption, access, monitoring, and data handling. Selecting a product before understanding these requirements can lead to ineffective or unnecessarily complex designs. Unrestricted access and removing logs increase risk. A risk-based approach ensures that security controls are selected because they address defined requirements rather than because a technology is widely marketed or adopted.
Question 68
Which architecture capability helps prevent an application from accessing data stores that are unrelated to its intended business function?
- Application-specific authorization and data access controls
- Shared database administrator accounts
- Broad database permissions
- Anonymous database access
Correct Answer: 1
Explanation
Application-specific authorization and data access controls restrict applications to the information required for their intended functions. This supports least privilege and reduces the potential impact of an application compromise. Broad database permissions or shared administrative accounts can expose large amounts of information unnecessarily. Anonymous access creates additional security concerns and removes accountability. Architects should consider application identities, database roles, segmentation, and resource-level authorization when designing access to sensitive data stores.
Question 69
An organization wants to identify sensitive information before applying protection policies. Which Microsoft capability can assist with discovering and classifying organizational data?
- Microsoft Purview
- Microsoft Paint
- Azure Load Balancer
- Windows Calculator
Correct Answer: 1
Explanation
Microsoft Purview provides data governance and compliance capabilities that can help organizations discover, classify, and manage information across supported data sources. Understanding where sensitive information exists is an important prerequisite for designing effective protection, retention, compliance, and data-loss prevention policies. Network load balancing and general-purpose desktop applications do not provide comparable data-governance capabilities. A security architecture should establish visibility into sensitive information before determining how that information should be protected and governed.
Question 70
A security architect is designing an identity strategy for automated workloads such as applications and services. Which approach reduces the need to embed long-lived passwords in application code?
- Use managed identities or workload identities
- Store administrator passwords in source code
- Use one shared password for all services
- Disable authentication for internal applications
Correct Answer: 1
Explanation
Managed identities or workload identities allow applications and services to authenticate without requiring developers to embed long-lived passwords or secrets directly in source code. This reduces credential exposure and supports more controlled identity lifecycle management. Shared passwords and credentials stored in source code can be difficult to rotate and may be exposed through repositories or application artifacts. Disabling authentication is not an appropriate solution. Workload identity is an important component of modern cloud security architecture because applications increasingly require access to other services.
Question 71
Which security architecture practice helps ensure that cryptographic keys are protected separately from the data they encrypt?
- Centralized key management
- Storing keys in application source code
- Sharing keys through email
- Using one permanent key for every workload
Correct Answer: 1
Explanation
Centralized key management provides controlled storage, access, rotation, monitoring, and lifecycle management for cryptographic keys. Separating key management from application data can reduce the risk that compromise of an application or storage location automatically exposes the keys required to decrypt protected information. Storing keys in source code or sharing them through email creates unnecessary exposure. Using one permanent key for every workload also increases the impact of key compromise. Proper key management should reflect data sensitivity and organizational requirements.
Question 72
An organization wants to make sure that encryption keys can be rotated without redesigning every application that uses encrypted data. Which architecture principle is helpful?
- Separation of cryptographic key management from application logic
- Hard-coding keys into applications
- Using plaintext secrets
- Disabling key rotation
Correct Answer: 1
Explanation
Separating cryptographic key management from application logic allows organizations to manage key lifecycle operations independently of individual applications. This can simplify rotation, access control, auditing, and recovery while reducing the need to modify application code whenever cryptographic requirements change. Hard-coded keys make rotation difficult and increase exposure if source code is compromised. Plaintext secrets provide no meaningful protection, while disabling rotation can leave organizations dependent on outdated or compromised keys. Centralized key-management services can support this architectural separation.
Question 73
Which architecture approach helps protect security-sensitive services from failures affecting a single geographic location?
- Geographic redundancy
- Single-region dependency
- One-server architecture
- Centralized local-only storage
Correct Answer: 1
Explanation
Geographic redundancy distributes critical services or supporting capabilities across separate locations so that a regional outage does not necessarily make the entire service unavailable. Depending on business requirements, this can involve multiple regions, availability zones, backup environments, or disaster-recovery arrangements. A single-region dependency creates a larger availability risk when that location experiences an outage. Architects should determine the required recovery objectives and business impact before selecting the appropriate level of geographic redundancy.
Question 74
A business requires critical applications to recover within a short period after a major security incident. Which architectural requirement should be defined?
- Recovery time objective
- Screen resolution
- Password length only
- DNS hostname format
Correct Answer: 4
Explanation
The Recovery Time Objective, or RTO, defines the maximum acceptable time required to restore a service after an outage or disruptive event. It is an important input into disaster recovery and resilience architecture because it influences redundancy, backup strategies, recovery procedures, and technology choices. Password length can improve authentication security but does not define service recovery requirements. Screen resolution and hostname formatting are unrelated. Architects should define RTO together with other business continuity requirements, including recovery point objectives.
Question 75
Which requirement defines how much data loss an organization can tolerate after a disruptive event?
- Recovery Point Objective
- Recovery Time Objective
- Maximum administrator count
- Network throughput target
Correct Answer: 1
Explanation
The Recovery Point Objective, or RPO, defines the amount of data loss that an organization can tolerate, typically expressed as a period of time. For example, an organization requiring an RPO of a few minutes needs recovery mechanisms that minimize the age of restored data. RTO instead focuses on how quickly a service must become operational again. RPO and RTO are therefore complementary requirements that influence backup, replication, disaster recovery, and resilience architecture.
Question 76
A security architect is evaluating a business application that must remain available during maintenance of individual infrastructure components. Which design characteristic should be emphasized?
- High availability
- Single point of failure
- Manual-only recovery
- Permanent administrative access
Correct Answer: 1
Explanation
High availability architecture reduces service disruption by using redundancy, failover capabilities, resilient components, and appropriate maintenance strategies. The objective is to keep important services operational when individual components fail or require maintenance. A single point of failure creates a dependency that can interrupt service, while manual-only recovery may increase restoration time. Administrative access does not itself provide availability. Architects should determine availability requirements from business impact and then design redundancy and failover mechanisms that meet those requirements.
Question 77
Which architectural capability helps an organization determine whether an identity, device, or application should be trusted at a particular moment?
- Continuous risk evaluation
- Permanent trust assignment
- Static network location
- Shared credentials
Correct Answer: 1
Explanation
Continuous risk evaluation allows security decisions to change as relevant conditions change. A user’s risk, device state, authentication context, or application behavior can change after initial access has been granted. A Zero Trust architecture therefore benefits from mechanisms that can reevaluate access rather than relying on permanent trust. Static network location and shared credentials provide limited context and can create excessive trust. Continuous evaluation supports adaptive security and helps organizations respond when the security posture of an identity or device changes.
Question 78
A company wants to ensure that security policies are enforced consistently across multiple Azure subscriptions. Which architectural capability should be considered?
- Azure Policy and centralized governance
- Separate undocumented configurations
- Manual configuration on every resource
- Shared administrator passwords
Correct Answer: 1
Explanation
Azure Policy can help organizations enforce or assess compliance with defined requirements across Azure resources. When combined with centralized governance structures, it can provide consistency across subscriptions and resource groups while allowing appropriate delegation. Manual configuration of every resource is difficult to maintain at scale and can result in configuration drift. Shared administrator passwords weaken accountability and security. Policy-based governance helps architects translate organizational requirements into repeatable controls that can be monitored over time.
Question 79
Which architecture capability helps detect when cloud resources drift away from an approved security configuration?
- Continuous configuration assessment
- One-time manual review
- Disabling configuration monitoring
- Anonymous resource administration
Correct Answer: 1
Explanation
Continuous configuration assessment helps identify when resources no longer match approved security requirements or organizational baselines. Configuration drift can occur because of administrative changes, automation errors, application deployments, or other operational activities. Detecting drift promptly allows security teams to investigate and remediate deviations before they create significant exposure. A one-time review provides only a snapshot and may miss changes that occur later. Disabling monitoring or allowing anonymous administration further reduces visibility and accountability.
Question 80
An organization is defining security architecture standards for new cloud workloads. Which approach best supports repeatable and consistent deployments?
- Security architecture patterns and reusable baselines
- Designing every workload independently
- Allowing unrestricted configuration choices
- Avoiding documented security requirements
Correct Answer: 2
Explanation
Security architecture patterns and reusable baselines provide standardized approaches that teams can apply when designing new workloads. They can define expectations for identity, networking, logging, encryption, access control, monitoring, and other security capabilities. Reusable patterns improve consistency and reduce the likelihood that teams overlook important controls. Designing every workload independently can produce inconsistent security and increase engineering effort. Undocumented or unrestricted configurations also make governance and compliance more difficult. Standardized patterns should remain adaptable to workload-specific risks and requirements.