GARP SCR Exam Prep
Sustainability and Climate Risk (Page 4 )

• A: Person Accounts cannot be merged directly with standard Contact records.
• C: There is no Account Setup option that automatically merges Person Account duplicates.
• D: Matching rules and duplicate rules can help identify or prevent duplicates, but they do not automatically merge Person Accounts. Also, relationship considerations do not change the basic merge capability.

• MAC flooding: Overwhelms a switch’s MAC address table, potentially causing traffic to be broadcast.
• DNS spoofing: Provides false DNS responses to redirect users.
• ARP poisoning: Sends false ARP information to associate an attacker’s MAC address with another device’s IP address.

• Virtual machine disks
• Databases
• Storage accounts
• File systems

• Site-to-site VPN: protects data moving between networks
• HTTPS: protects data moving between a client and website
• Encrypted email: generally protects the message while being transmitted

• At rest = stored data
• In transit = moving data
• In use = data currently being processed by a system

• Disable default accounts: Default or unused accounts may have predictable names or credentials and can be abused by attackers. They should be disabled, removed, or secured with strong credentials where necessary.
• Remove unnecessary services: Every running service can contain vulnerabilities or provide an entry point. Removing services the server does not need reduces exposure.

• Add the server to the asset inventory: Important for asset management, but it does not directly harden the system.
• Document default passwords: Default passwords should be changed or disabled—not recorded for continued use.
• Send logs to the SIEM: Supports monitoring and detection, rather than directly reducing the attack surface.
• Join the corporate domain: A deployment/configuration decision, not inherently a hardening measure.

• A — Reports: Reports are informational and don’t enforce access during an SSO transaction.
• B — Apex trigger and Permission Sets: A trigger could update permissions when a Case changes, but this creates synchronization and timing issues. It also changes Salesforce permissions rather than making a direct, real-time decision for the external system.
• C — Custom SAML JIT Provisioning: JIT provisioning is primarily for creating or updating users at login. It isn’t the appropriate mechanism for dynamically querying business records and deciding whether access should be granted.
• D — Connected App Handler: Designed for custom, programmatic control during connected-app authentication and authorization. Apex can check the user’s current open classified cases and permit or reject the SSO request.

• Have a definite, clear objective (C): Know exactly what you want to communicate. A clear purpose reduces ambiguity and irrelevant information.
• Plan the communication (E): Decide what to say, who needs the information, the appropriate channel and the best timing.
• Seek feedback (F): Check that the receiver understood the message. This could involve asking for confirmation or inviting questions.

• Ask questions (A): Usually associated with the receiver checking or clarifying information, although a sender may use questions in practice.
• Give feedback (B): Feedback is generally the receiver’s response to the sender’s message. The sender’s responsibility here is to seek feedback.
• Consider their contribution (D): This is not a standard sender-focused step in the communication process. The sender should consider the receiver’s needs and perspective, but the wording is less precise than the three recognised actions above.

• Detect risky sign-ins from unfamiliar or unidentified IP addresses
• Evaluate user or sign-in risk
• Automatically require a password change because of a risky sign-in

• User risk policy: Can require a user to securely change their password when the account may be compromised.
• Sign-in risk policy: Can require MFA or block access based on the risk of a particular sign-in.

• Inherent risk: Risk that exists before controls are implemented.
• Avoided risk: Risk eliminated by choosing not to perform the risky activity.
• Operational risk: Risk arising from failures in processes, people, systems, or daily operations.

• Reviewing security objectives to ensure they support business goals.
• Ensuring security requirements are integrated consistently across business units.
• Coordinating security policies, risk management, controls, and awareness activities.

• Executive management: Provides direction, funding, and support, but usually does not manage day-to-day security integration.
• Board of directors: Provides governance and oversight, not operational security coordination.
• Steering committee: Helps coordinate and prioritize initiatives, but the CISO typically owns the overall security program and ensures its integration.

• Online payment fraud
• Account takeover
• Fake account creation
• Suspicious transactions

• C — “when the query finishes”

• D — “when the query began”

• Users logging in more frequently than average
• Logins occurring during non-business hours
• Patterns that may indicate compromised credentials or suspicious access

• Login History: Shows individual login attempts and basic details, but does not provide behavioral analysis or averages.
• Login Inspector: Used to troubleshoot or inspect a specific login attempt, rather than analyze organization-wide patterns.
• Login Report: May provide reportable login information, but it is not the specialized tool for forensic behavioral analysis.

• Personally identifiable information (PII) detection

• Prompt Shields

• Self-harm content filtering addresses self-harm-related content.
• Violence content filtering addresses violent content.
• Neither protects customer PII or detects document-based prompt injection.

• 2000::/3 — Global unicast, used for publicly routable IPv6 addresses.
• FC00::/7 — Unique local, used for private internal addressing.
• FE80::/10 — Link-local, used only on the local network segment and not routed between subnets.

• Works across SaaS and internal applications: TOTP is widely supported by authentication systems and can be integrated into many applications.
• Device manufacturer agnostic: A hardware token or authenticator application can generate the code without depending on a specific computer or phone manufacturer.
• Offline capability: The code is generated locally using a shared secret and the current time; an internet connection or cellular service is not required.

• Username and password: May work offline but provides weaker authentication and does not meet the intended improvement in security.
• Biometrics: Can depend on device hardware, operating-system support, and enrollment mechanisms.
• SMS verification: Requires cellular connectivity and is vulnerable to threats such as SIM swapping.

• The application failing to start or becoming unhealthy
• An incorrect probe path, port, or protocol
• The application needing more startup time
• Dependency or configuration failures
• A liveness probe being too aggressive

bash 
kubectl describe pod <pod-name> 
kubectl logs <pod-name> --previous

• Scale to more replicas: may hide the issue but does not diagnose it.
• Decrease initialDelaySeconds: makes probes run earlier and could worsen startup failures.
• Drain and reboot the node: node metrics are normal, so rebooting is not justified as the first step.

• A — Add a Path for Stage: A Path lets users update the Opportunity’s Stage directly from the record page, without opening the full edit form. It can also display guidance and key fields.
• B — Use a Kanban list view: Users can move Opportunities between stages by dragging records between columns, which is ideal when Stage is the only field they normally change.

• Who performed the action
• What action occurred
• When it occurred
• Where it originated
• Whether it succeeded or failed

• Investigating suspicious activity: Important, but investigation depends on having adequate audit data first.
• Storage allocation: Necessary for retention, but storage does not help if the records lack meaningful details.
• Actions after audit failure: Part of operational planning, not the primary assessment of the application’s audit capability.

• Due Date
• Order Date
• Delivery Date

DAX 
Order Date = 'Due Date' 
Delivery Date = 'Due Date'

• Due Date[Date] ? Sales[Due Date]
• Order Date[Date] ? Sales[Order Date]
• Delivery Date[Date] ? Sales[Delivery Date]

• Manage multiple organizations from one hierarchy.
• Enterprise-wide policies, including repository visibility, forking, and GitHub Copilot policies.
• Centralized identity and access management, such as SAML SSO, SCIM provisioning, and—where applicable—Enterprise Managed Users.
• Centralized billing and licensing, including organization and Copilot seat management.
• Enterprise audit log, which aggregates activity across organizations.
• Security and compliance oversight, such as organization security visibility and enterprise-wide controls.
• Enterprise support and account management features, depending on the plan.

• Organization: manages its own repositories, teams, members, and local policies.
• Enterprise: governs multiple organizations and can enforce policies across them.

• ARP poisoning: Redirects or intercepts local network traffic; monitoring would typically show suspicious ARP changes or man-in-the-middle behavior.
• Jamming: Interferes with wireless or radio signals. It would affect connectivity, not usually show a server-specific overload.
• Kerberoasting: Attempts to obtain and crack Kerberos service-account hashes; it does not normally cause a system outage.

• Microsoft Teams: Connects to Teams-related data, but it isn’t the primary connector for the Power Apps data tables.
• Personal Analytics: Provides personal productivity insights, not application data.
• SQL Server database: Only applies if the app explicitly uses SQL Server as its data source.
• Dataflows: Used for preparing and centralizing data, not as the normal direct connection to a Power Apps app.

• Resources that do not need internet access should remain on private network segments.
• Internet-facing access should be restricted to systems that require it.
• Access should be explicitly allowed rather than broadly exposed.

• A: A single administrator with access to core functions may violate least privilege if that access is broader than necessary.
• B: Inspecting traffic supports monitoring and defense, but does not itself limit privileges.
• C: Updating routing configurations supports availability and connectivity, not least privilege.

• Sending calls to available agents quickly
• Balancing interactions across agents
• Preventing calls from being handled manually one at a time

• Workforce Management: Forecasts demand and schedules enough staff; it supports wait-time reduction but does not directly distribute calls.
• Skill-based Routing: Routes calls based on agent skills and may improve the customer experience, but the question is asking about the core feature that distributes calls efficiently.
• IVR: Lets callers navigate menus and self-service options; it does not primarily assign calls to agents.

• 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.

• Normalize casing in the data source—for example, convert all values to uppercase or lowercase.
• Add an index key to provide a unique, stable identifier for each row or value.

• nomes de pessoas;
• organizações;
• locais;
• datas;
• números de processos;
• leis ou contratos.

• NER = identifica informações específicas e classificáveis.
• Sumarização = reduz um documento e apresenta seus pontos principais.

• Azure Machine Learning is the overall Azure service.
• Machine Learning designer is the visual, drag-and-drop interface within Azure Machine Learning.
• Microsoft may refer to the broader product as Azure Machine Learning studio, while “Designer” remains the specific visual workflow tool.

• Azure Logic Apps: Workflow and integration automation.
• Azure Batch: Large-scale parallel or batch compute.
• Azure Cosmos DB: Globally distributed NoSQL database.

• Prevent connections to malware command-and-control servers
• Identify infected systems making those DNS requests
• Collect information for incident response

• A: Attackers do not normally use sinkholes to map a company’s domain structure.
• B: Redirecting employees from legitimate sites to attacker-owned sites describes malicious DNS manipulation, not a defensive sinkhole.
• D: Attracting attackers away from real resources is more closely associated with a honeypot or deception system.

• Authentication: Verifies a user’s identity, such as username and password.
• Authorization: Determines what the authenticated user is allowed to access.
• Accounting: Records connection and usage details, such as login time or session duration.

• CIA: Confidentiality, integrity, and availability are broad security objectives, not a specific RADIUS function.
• ACL: An access control list contains permit/deny rules on systems or network devices. RADIUS can support access decisions but is not itself an ACL.
• PEM: Privacy-Enhanced Mail is also associated with certificate and key encoding formats; it is unrelated to RADIUS’s primary purpose.

• 25 — Traditional SMTP server-to-server delivery; often restricted for client submission and not inherently encrypted.
• 110 — POP3 for retrieving email; unencrypted by default.
• 143 — IMAP for retrieving and synchronizing email; unencrypted by default.
• 587 — Authenticated SMTP submission, commonly secured with STARTTLS.

• Planning — identify the need, objectives, resources and feasibility.
• Analysis — determine user requirements and examine the existing system.
• Design — specify how the new system will work.
• Implementation — build, test, install and introduce the system.
• Maintenance/evaluation — monitor and improve the system after implementation.

• Server provisioning
• Operating systems and runtime infrastructure
• Scaling
• Much of the maintenance and patching

• Thin clients reduce endpoint hardware requirements but do not specifically streamline code deployment.
• Private cloud provides dedicated cloud infrastructure but usually requires more management and expense.
• Virtual machines improve resource utilization, but administrators still manage the VMs, operating systems, and deployments.

• 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.

• Idioma: “Responda em português.”
• Tamanho: “Responda em até três frases.”
• Formato: “Use uma lista com três recomendações.”
• Objetivo: “Recomende produtos com base nas necessidades do cliente.”

• Mudar o tamanho do LLM: pode alterar capacidade e custo, mas não garante idioma ou respostas curtas.
• Aumentar a temperatura: aumenta a criatividade e a aleatoriedade; não controla diretamente o tamanho ou idioma.
• Aumentar o Top K: permite considerar mais tokens prováveis, aumentando a variedade; também não é o mecanismo principal para controlar idioma ou comprimento.

• An Anypoint VPC provides private network connectivity for CloudHub applications.
• An IPsec VPN tunnel or AWS Direct Connect connects that VPC to the customer’s on-premises network without exposing the database to the public internet.
• The VPC and on-premises firewalls must allow the required traffic, routes, and ports.

• Static IP addresses only identify the application’s outbound traffic; they do not create a private network path to the database.
• A Dedicated Load Balancer does not replace the required network connection to the on-premises environment. It is also unnecessary merely to reach individual databases.
• Moving sensitive databases to a DMZ is not the intended architecture and could reduce their protection.

• The current and previous versions
• Which clauses were changed
• When each revision occurred
• Potentially, who made the changes

• Version validation: Verifies a version’s accuracy or integrity but does not primarily track revisions.
• Version changes: Not the standard name for a formal document-management process.
• Version updates: Describes updating a document, not the complete process of managing and tracking its revisions.

• Admin access to the deployment pipeline (B) – lets the developers use the pipeline and deploy content.
• Contributor access to the Development and Test workspaces (E) – required to deploy items into those workspaces.
• Viewer access to the Production workspace (D) – lets them view Production content without allowing deployment or modification.

• Contributor access to Production (F), because that could allow changes or deployment there.
• Viewer access to Development/Test (C), because Viewer is insufficient for deployment.
• Build permission to Production semantic models (A), because building reports on a semantic model is not required merely to view Production items.

• Planning and designing products and services
• Developing and delivering them
• Managing risks, suppliers, and resources
• Measuring performance
• Continually improving value delivery

• Value stream steps describe activities used to create and deliver value; they do not themselves provide the broader capabilities.
• Vision and operating model provide direction and structure, but they are not the practical management capabilities that enable the work.
• Value chain is the operating model showing how activities combine to create value; it is enabled by practices and resources.

• Laws and regulations
• Litigation holds
• Industry or contractual obligations
• Tax, financial, health, or privacy requirements

• Business strategy and direction: May influence retention, but cannot override legal requirements.
• Storage capacity and longevity: Practical considerations, not the primary driver.
• Business ease and value analysis: May support decisions after compliance obligations are identified.

• A: Daily involvement is unnecessary and may not solve the availability problem.
• C: Clarifying all requirements at the start conflicts with agile’s iterative refinement.
• D: Simply reviewing based on availability leaves the problem unresolved and allows rework to continue.

Question 3: AWS Storage Gateway File Gateway

• A: S3 bucket per user — S3 is object storage, not a traditional shared file system; mounting it requires extra tools and is less efficient.
• B: File Gateway — Provides a local file share using standard file protocols while storing files in Amazon S3. This preserves convenient local access and extends storage capacity.
• C: WorkSpaces and WorkDocs — Designed for virtual desktops and document collaboration, not large shared file storage.
• D: EC2 with EBS — EBS is attached to one EC2 instance and is not designed for direct multi-user file sharing.

1. Create a custom Sensitive Information Type (SIT) in the Microsoft Purview portal.
2. Use a regular expression to match the 32-character alphanumeric account number.
3. Reference that SIT in the DLP policy protecting SharePoint Online.

• Format-based data ? custom SIT with RegEx
• Built-in sensitive data ? Microsoft-provided SIT
• Document classification/protection ? sensitivity labels
• Security investigation queries ? Advanced Hunting, not DLP detection

• Accept: Acknowledge the risk and choose not to take additional action.
• Transfer: Shift the risk or its financial impact to another party, such as through insurance or outsourcing.
• Mitigate: Reduce the likelihood or impact of the risk, such as by implementing security controls.
• Avoid: Eliminate 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.

• User preferences change, so the model must learn from recent data.
• Keeping the existing data helps preserve knowledge of older patterns and provides a broader training distribution.
• Training only on new data can cause catastrophic forgetting and may overfit if the new dataset is small.
• The new data should not automatically be used as the test set, because it is needed for training and the model must still be evaluated on separate, representative data.

• Ease of exploitation
• Required privileges
• User interaction
• Impact on confidentiality, integrity, and availability

• CVE: Identifies and names a specific publicly known vulnerability; it does not measure severity.
• OSINT: Refers to intelligence gathered from publicly available sources.
• SOAR: Automates and coordinates security operations, such as alert response and playbooks.

• s3:GetObject for the relevant objects
• s3:ListBucket if listing is required
• Appropriate bucket and object resource permissions

• B: Making the bucket public is insecure and unnecessary.
• C: Prompt engineering cannot override AWS IAM or encryption permissions.
• D: Data sensitivity does not determine whether the role can access it.