API API-571 Exam Prep
Corrosion and Materials Professional (Page 38 )

• Documented and evaluated
• Assessed for security, cost, and operational impact
• Reviewed and approved by the appropriate personnel
• Tested before implementation
• Tracked with version history and rollback procedures

• Risk management process: May help assess the issues, but it does not authorize and manage design changes.
• Product design process: Applies primarily while creating a new design.
• Design review process: Normally evaluates a design before release; this design is already released.

• 16GB RAM: A 64-bit OS is needed to use more than roughly 4GB effectively, but RAM capacity does not prove the CPU supports 64-bit operation.
• 500GB HDD: Storage capacity has no bearing on OS architecture.
• 1Gbps Ethernet: Network speed is unrelated to CPU architecture.

• Each Case must follow defined support steps.
• Each step must be completed within a specified time limit.

• Case Escalation Rules: Escalate Cases based mainly on age or criteria; they do not model a complete sequence of service steps.
• Process Builder with Scheduled Actions: Can automate time-based actions but is not the standard framework for Case service-level commitments.
• Omni-Channel Routing: Routes work to agents based on capacity and priority; it does not track Case lifecycle deadlines.

• Maximum response and resolution times
• Expected uptime or availability
• Performance requirements
• Escalation procedures
• Consequences for failing to meet requirements

• SOW: Defines a project’s scope, tasks, deliverables, and schedule.
• MOA: Documents specific responsibilities agreed upon by two parties.
• MOU: Records a general understanding or intent to cooperate.

• Crowd-sourced evaluation: Requires recruiting and managing many evaluators.
• Human-worker evaluation: Provides human judgment but requires coordination, labeling instructions, and quality control.
• RLHF: Is a training and alignment process, not simply a low-overhead model comparison method.
• Automatic model evaluation: Quickly evaluates outputs using predefined toxicity or quality metrics with minimal manual effort.

• Active remediation actions role in Microsoft Defender for Endpoint

• Security Reader role in Azure AD/Entra ID

• Security Administrator is broader than necessary because it grants extensive security-management permissions, violating least privilege.
• Compliance Data Administrator is intended for compliance data management, not Defender for Endpoint remediation approvals.

• Create and manage approved IT services as products
• Control which users can deploy those products
• Apply governance, permissions, and constraints
• Use and manage infrastructure-as-code templates, such as AWS CloudFormation templates

• AWS Resource Explorer: Helps find and browse AWS resources; it does not govern IaC deployments.
• AWS Organizations: Manages accounts, consolidated billing, and organization-wide policies.
• AWS Systems Manager: Provides operational management, such as patching, automation, and parameter storage, but it is not primarily used to catalog and govern IaC-based service deployments.

• How quickly the vendor must respond to incidents or requests
• Availability or uptime requirements
• Resolution time targets
• Performance expectations and penalties for failing to meet them

• SOW (Statement of Work): Describes the work, deliverables, scope, and schedule.
• MOA (Memorandum of Agreement): Documents an agreement in which parties commit to specific responsibilities.
• MOU (Memorandum of Understanding): Records a general intention to cooperate; it may not be legally binding.

• Base table — the table containing common inherited fields
• Parent table — the table directly extended by the child
• Other tables in the hierarchy

• A — Capacity: The system must handle all current records and anticipated future records. A system that cannot cope with volume will quickly become ineffective.
• C — Accuracy: Academic records are critical, so the new system must be at least as accurate as the existing system and comparable systems. Poor accuracy could cause serious administrative and reputational problems.
• D — Integration: Linking with the university’s financial systems supports consistency and avoids duplicate data entry, especially for registration, deregistration and fee-related transactions.

• B — Parallel running: This is a useful implementation and risk-control technique, but it is not an essential feature of the system itself. It may also be expensive and time-consuming.
• E — Internet access for all information: This creates significant confidentiality and security risks. External access might be needed for selected services, but unrestricted access to all information is not essential and would be inappropriate for student records.

• C series: CPU-optimized instances; not designed primarily for LLM training.
• G series: GPU instances generally optimized for graphics and some machine learning workloads, but not specifically large-scale model training efficiency.
• P series: Powerful GPU instances for ML training, but typically consume more energy than Trainium-based instances for suitable training workloads.

• Accept: Acknowledge the risk and take no additional action.
• Transfer: Shift the risk or financial impact to another party, such as through insurance or a contract.
• Mitigate: Reduce the likelihood or impact using controls, such as firewalls, training, or backups.
• Avoid: Eliminate the activity that creates the risk.

• A valid input returns the expected result
• An invalid input raises an error
• Boundary values are handled correctly

• B: Copilot may help generate tests, but it does not automatically write all necessary tests.
• C: Writing the implementation does not verify that it works correctly.
• D: Copilot can suggest test commands or test code, but the developer or development environment must execute and validate the tests.

• Microsoft Purview portal: Create and manage sensitivity labels and configure support for sensitivity labels used with Office files in SharePoint and OneDrive.
• SharePoint admin center: Primarily manages SharePoint settings. Older guidance and PowerShell procedures used SharePoint tenant configuration, which can make this question confusing.
• IRM: Concerns Information Rights Management and is a separate protection mechanism; it should not be used to identify the portal for configuring Microsoft Purview sensitivity labels.

• B. Versioned configuration files — Infrastructure is defined in machine-readable files and tracked in version control, allowing repeatable provisioning and change history.
• D. Docker files — Assuming “Doctor files” is a typo for Dockerfiles, a Dockerfile declaratively defines how to build a container image and is commonly considered infrastructure/configuration as code.

• A. Cloned virtual machine images — These are prebuilt infrastructure artifacts, but cloning an image is not itself a code-based infrastructure definition.
• C. Change management database records — A CMDB records information about infrastructure; it does not define or provision that infrastructure.

• A. Periodically rotate responsibilities: May reduce some risks, but it does not directly detect unauthorized changes.
• B. Review segregation-of-duties conflicts: Identifies incompatible access combinations, not whether a specific data change was unauthorized.
• C. Log changes in an outside application: Logs provide evidence, but someone must review and analyze them. Logging alone does not detect misuse.
• D. Independent review: Directly detects unauthorized changes and reduces the risk that the person making the change can conceal it.

• Matching hashes: The software likely has not changed.
• Different hashes: The software was modified or corrupted.

• Encryption: Protects confidentiality by making data unreadable; it does not primarily detect changes.
• Baselines: Define an approved system or configuration state, but they are not the specific integrity mechanism here.
• Tokenization: Replaces sensitive data with substitute values.

• Amazon EC2 instances — ???????? ?? ?? ??????? CPU, memory ??? instance size ???????? ???????
• AWS Lambda functions — memory configuration ?????????? ???????
• Amazon EBS volumes — volume type ?? size optimize ???? ???????
• ??????? ECS workloads — resource configuration ? cost optimization-?? ???????

• Memory ? compute usage ?????????? ???? custom code ????? ???? development ? maintenance ??????
• Cost allocation tags ???? ????? ??? ?????? ???? ??????? ???; inefficient resource ??????? ?? recommendation ???? ???
• CloudTrail resource ???? ?? API activity ??????, resource utilization ????

• Leaf switches provide access ports for servers, users, and other devices.
• Spine switches provide the backbone between leaf switches.
• Every leaf switch connects to every spine switch, creating a predictable, full-mesh fabric between the two layers.
• Leaf switches do not connect directly to other leaf switches, and spine switches do not connect directly to other spine switches.

• A: Adding both a spine and leaf is unnecessary for simply adding access ports.
• B: It focuses on uplink speed, not the scalable topology.
• D: A single spine connection creates a bottleneck and a single point of failure.

• Code suggestions: Inline completions as you write code, such as lines, functions, or blocks.
• Chat: An interactive interface for asking questions, explaining code, generating code, and helping with debugging.

• Knowledge Base: Not listed as a standard Copilot Individual IDE feature in this context.
• Pull Request Diff Analysis: More closely associated with GitHub-based code review or pull-request features, not the core Individual IDE extension capabilities.

• The requirement is to obtain an assessment of the Azure environment’s design.
• The proposed solution is the Premier support plan.
• Premier can provide this type of guidance, but it is a higher-tier, more expensive option.
• The question specifically says to keep costs to a minimum. A lower tier—typically Professional Direct in the support-plan model used by this question—provides architectural/design guidance.

• Namespace: The namespace associated with the code where the checkpoint was set.
• Time: When the checkpoint was captured or executed.

• Exception: Exceptions are viewed through debug logs or execution results, not as the primary Checkpoints tab information.
• Debug Statement: System.debug() output belongs in the Logs tab. A checkpoint captures program state, such as variables and their values, at a specific point in execution.

• Reviewing and validating generated code
• Checking security, licensing, and quality concerns
• Testing the implementation
• Making the final design and coding decisions

• A: Copilot is not a complete replacement for developers.
• C: Human input, review, and oversight are still required.
• D: Copilot Chat supports many tasks beyond debugging, including explanation, generation, refactoring, and testing assistance.

• Azure Resource Manager (ARM) templates
• Or, in newer Azure terminology, Bicep files

1. insert con; ? 1
2. Database.setSavepoint(); ? 2
3. update con; ? 3
4. Database.rollback(sp_admin); ? 4

Statement 1 — Correct

Statement 2 — Correct

• Accept: Acknowledging the risk and choosing not to take additional action.
• Transfer: Shifting the risk or financial consequences to another party, such as an insurer.
• Mitigate: Reducing the likelihood or impact through controls, such as patching or access restrictions.
• Avoid: Eliminating the activity that creates the risk.

• LastName: Required.
• FirstName: Optional.
• AccountId: Optional; a Contact may be associated with an Account later or remain private, depending on organization settings.
• Name: A compound display field made from first and last name; it isn’t entered as a separate field.

• C — Some risks cannot be eliminated.

• D — Accepting residual risk does not imply recklessness.

• E — Most companies in this industry will say something similar.

• Training or coaching
• Mentoring
• Additional support or resources
• Targeted performance improvement plans

• A: Recognition may be appropriate, but awards do not address identified gaps.
• C: Rotating schedules does not necessarily improve the specific competencies that are missing.
• D: Assessment results should be handled sensitively, but keeping them entirely private prevents useful feedback and development discussions.

• Default network device credentials: More associated with external attackers or poor device configuration.
• Spear phishing emails: Commonly used to compromise users, but less characteristic of an insider who already has access.
• Typosquatting and impersonation: Primarily social-engineering techniques aimed at deceiving users.
• Unidentified removable devices: Provide a direct way to transfer data outside the organization and may bypass network monitoring.

• A — Too infrequent: Formal strategies are often reviewed only every three to five years. This can make the organisation slow to respond to rapid changes in technology, competitors, regulation or customer needs.

• C — Relies on predicting the future: The approach assumes senior managers can make reasonably reliable forecasts and assumptions. In uncertain environments, these assumptions may quickly become invalid.

• E — Can restrict radical innovation: Formal planning tends to favour existing information, established objectives and incremental improvements. This may discourage experimental or highly innovative strategies that emerge from lower levels of the organisation.

• B concerns the difficulty of achieving competitive advantage through core competences when competing with focused specialists. It is not specifically a drawback of the formal top-down planning process.
• D is an activity organisations should undertake—continuous monitoring—not a drawback of the approach itself.

• Accept: Acknowledging the risk without taking additional action.
• Transfer: Shifting responsibility or financial impact to another party, such as through insurance or outsourcing.
• Mitigate: Reducing the likelihood or impact of the risk through controls.
• Avoid: Eliminating the activity or condition that creates the risk.

• Career enhancement — A mentor can provide guidance, advice, networking support and help the mentee identify career opportunities.
• Support with new challenges — A mentor can help the mentee think through unfamiliar situations and develop confidence and practical solutions.
• Personal development — Mentoring can improve skills such as communication, leadership, decision-making and self-awareness.

• Solving all problems — The mentor supports and guides the mentee but should not take responsibility for solving every problem.
• Discipline would be dispensed if they make a mistake — Mentoring does not remove normal accountability or workplace consequences. Mistakes should instead become learning opportunities.

• The JSON files contain one billion items, so this is a big-data workload.
• PySpark uses Apache Spark’s distributed, parallel processing, allowing the data to be processed across multiple compute nodes.
• It can read and transform data directly from OneLake, helping minimize unnecessary data movement or duplication.
• A Fabric notebook can also support exploration and visualization, as well as Spark-based analytics and anomaly-detection workflows.

• Pandas is primarily in-memory and generally suited to smaller datasets. One billion records would be impractical on a typical single machine.
• A Power BI report with core visuals is appropriate for visualization and sharing, but it is not the best tool for large-scale transformation, parallel processing, or anomaly detection. It would normally consume prepared data rather than perform the entire workload.

• C — Before update
• D — Before insert

apex 
trigger AccountTrigger on Account (before insert, before update) { 
    for (Account acct : Trigger.new) { 
        acct.Description = 'Updated automatically'; 
    } 
}

• In after insert and after update, Trigger.new records are read-only.
• Use after triggers when you need the record’s final database Id or want to create/update related records.
• Attempting to change a field directly in an after trigger causes a read-only error.

• Keep earlier prompt versions.
• Identify the last version that produced acceptable output.
• Restore it as a baseline.
• Make small, controlled changes—ideally one significant change at a time.
• Test the output after each change.

• A: Discards useful information about what worked.
• B: Large simultaneous changes make it difficult to identify the cause of problems.
• D: Accepts output that does not meet the requirements.

• NIDS: Monitors network traffic for suspicious activity and network-based attacks targeting the application or its supporting services.
• HIPS: Protects an individual host by monitoring processes, files, and system activity. It can help secure the web server, but it is not focused specifically on the application’s network attack surface.
• SIEM: Aggregates and correlates logs; it does not directly prevent attacks.
• Honeypot: A decoy system, not the primary protection for a production web application.
• Certificate revocation list: Deals with certificate trust, not application exploitation.

• A. IDS attack signatures: Primarily detects suspicious network activity, not necessarily malware embedded in uploaded files.
• C. Load balancer: Improves availability and distributes traffic; it does not inspect documents for malware.
• D. WAF: Protects web applications from attacks such as SQL injection and command injection, but its primary role is not scanning uploaded PDFs for malware.

• Input validation: Prevents malicious or malformed input within an application; it does not authenticate a software package.
• Secure cookies: Protect web-session cookies; they do not protect downloadable software.
• Fuzzing: Tests software by supplying unexpected input to find vulnerabilities; it does not verify software integrity.

• Check whether the data is accurate, complete, and properly prepared.
• Confirm that the pattern is not caused by an outlier, data-quality problem, or modeling issue.
• If the data is valid, treat the result as a potentially valuable new business insight.

• A: A data scientist may help, but expert validation and data-quality checking come first.
• C: Filtering out inconvenient data risks hiding a valid insight.
• D: Einstein’s result should not be accepted without verification simply because it produced the finding.

• A: Allow SAN certificates — SANs are used to identify valid hostnames in a certificate. They do not bypass trust validation.
• C: Open the secure LDAP port — A blocked port would normally cause a timeout or connection-refused error, not certificate errors.
• D: Increase the TLS version on the RA — The issue concerns certificate trust, not the organization’s registration authority.

1. Product + ProductSubCategory: Inner join

1. Result + ProductCategory: Left outer join

yaml 
clusterIP: None

• CronJob: Runs Jobs on a schedule and normally does not need stable networking.
• Deployment: Manages interchangeable, stateless replicas and usually uses a regular Service.
• DaemonSet: Runs a Pod on selected nodes but does not inherently require stable Pod identities.

• IRR assumes that interim cash flows can be reinvested at the project’s own IRR. This may be unrealistic, especially when the IRR is very high.
• MIRR assumes reinvestment at a specified rate, usually the company’s cost of capital or another realistic reinvestment rate.

• B: MIRR does not specifically favour projects with long payback periods.
• C: MIRR and IRR can rank competing projects differently.
• D: MIRR is not always higher than IRR; it may be higher or lower depending on the cash flows and reinvestment rate.

• Espionage: Stealing information for intelligence or competitive purposes.
• Data exfiltration: Unauthorized removal or transfer of data.
• Nation-state attack: An attack sponsored or conducted by a government.
• Shadow IT: Technology or access methods used outside approved IT processes.

• Microsoft Foundry is an enterprise platform for developers, data scientists, and IT teams.
• It supports the full AI application lifecycle: selecting models, connecting enterprise data, developing, evaluating, deploying, monitoring, and scaling solutions.
• It can include visual tools and low-code experiences, but it is not primarily designed to enable business users to build complete generative AI solutions independently.

• B: You still need to select and configure an appropriate model.
• C: Business users may participate through visual tools, but they are not the primary target audience.
• D: Foundry includes low-code tools, but it is not fundamentally a low-code-only platform.

• contoso.onmicrosoft.com
• contoso1.onmicrosoft.com

• onmicrosoft.com domains: Maximum of five per tenant.
• Custom domains: Domains that your organization owns and verifies in Microsoft 365.