CIMA CIMAPRA19-P03-1 Exam Prep
P3 Risk Management (Online) (Page 12 )

• desktopwidth:i:1280
• desktopheight:i:1024

• Connection information: Controls connection-related settings, not the desktop resolution.
• Scaling plan: Controls when session hosts start, stop, or scale based on demand.
• Session behaviour: Controls behavior such as disconnect or logoff handling.
• Display settings: Specifically controls RDP display properties, making it the appropriate choice.

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

• The requirement is an assessment of the Azure environment’s design, which requires a support plan offering proactive architectural guidance.
• Premier support would provide this capability, but it is a high-cost option.
• Since the requirement says to minimize expenses, Premier is not the best recommendation.
• A lower-cost plan with the required advisory/design-review capability—historically Professional Direct in Azure’s support-plan model—would be more appropriate.

• A. Adjust resolution: Incorrect because an incompatible resolution usually causes no display, distortion, or an unsupported-mode message—not intermittent flickering.
• B. Swap the HDMI cable: Correct. Replacing the common, easily tested component is the appropriate troubleshooting step.
• C. Replace the projector: Incorrect because the issue also occurs with a monitor.
• D. Configure refresh rate: A mismatched refresh rate can cause visual problems, but the repeated flicker across displays points more strongly to the cable.

• Company documents
• Databases
• Knowledge bases
• Current web or business data

• A: Describes diversity and inclusive design, not grounding.
• B: Describes explainability or model interpretability.
• D: Describes documenting a model’s capabilities and limitations.

• Sets a high initial price for a new product.
• Targets customers willing to pay more, often called early adopters.
• Gradually reduces the price to attract more price-sensitive customers as the product becomes less novel and competition increases.

• Penetration pricing: starts with a low price to gain market share quickly.
• Premium pricing: maintains a high price to communicate superior quality or status; it does not necessarily involve later price reductions.
• Loss leader pricing: sells one product at a very low price, sometimes below cost, to attract customers who may buy other products.

• File policy in Microsoft Defender for Cloud Apps: Can detect activity involving files, but it is not designed specifically to investigate risk from departing or deleted users.
• Access review policy in Microsoft Entra: Reviews whether users should retain access to resources; it does not detect historical document downloads.
• Alert policy in Microsoft Defender for Office 365: Primarily handles alerts for email and collaboration threats, not insider-risk investigations involving departed users.

• MTTC: Time required to contain or limit the incident’s impact — best match.
• MTTR: Time required to remediate or recover from the incident; this may include eradication, restoration, and cleanup, which goes beyond merely stopping spread.
• MTTD: How long it takes to discover the incident.
• MTBF: Average time between failures, generally a reliability metric.

• The application stores data on Amazon EBS volumes, so the encryption should be applied directly to those volumes.
• EBS encryption uses AWS-managed cryptographic operations and is designed to provide encryption at rest with minimal performance impact.
• The volumes are created during initial deployment, so they can be configured as encrypted when provisioned.

• B: Moving data to an encrypted S3 bucket changes the storage design and does not encrypt the EBS data the application uses.
• C: A custom encryption algorithm adds application overhead and is unnecessary.
• D: Ephemeral disks are temporary storage and can lose data when instances stop or terminate. Encrypting only the AMI’s root volume does not protect data stored elsewhere.

• Least privilege: Limits users to only the access necessary for their job.
• Background checks: Help identify potentially risky individuals before employment.
• Separation of duties: Ensures that one person cannot complete a sensitive process alone, reducing fraud and abuse.

• Future costs — Only costs occurring in the future can be affected by the investment decision. Past costs are sunk and irrelevant.
• Incremental costs — These are additional costs caused by choosing the investment. They are relevant because they differ between alternatives.
• Cash flows — Capital investment decisions are based on future cash inflows and outflows, usually discounted to present value.

• Committed costs have already been agreed or incurred and generally cannot be changed by the decision.
• Unavoidable costs will arise regardless of which option is selected, so they do not affect the choice.

• Frequency/likelihood = how often or how likely the risk is to occur.
• Severity/impact = how damaging or costly the consequences would be.

• A minor equipment fault occurring frequently may have high frequency but low severity.
• A major cyberattack occurring rarely may have low frequency but high severity.
• A risk that happens often and causes substantial losses has high frequency and high severity.

• Customize Opportunity Contact Role
• Add the Opportunity Contact Role related list to the Opportunity page layout

• Install unauthorized or unsupported software
• Access features blocked by the manufacturer or operating system
• Customize system behavior beyond normal settings

• SAS (Serial Attached SCSI):

• SSD (solid-state drive):

• A — Improved management of storage space: Correct.

• B — Improved supplier relationships: Correct.

• C — Improved pricing decisions: Correct.

• D — Non-product-specific costs must be apportioned: Incorrect.

• E — Profitability of each customer group: Incorrect.

• Microservices: An application design approach that divides software into small services; it does not specifically reduce the number of operating systems.
• Containerization: Uses isolated containers that share the host OS kernel—best match.
• Virtualization: Creates separate virtual machines, and each typically requires its own guest OS, so it does not minimize OS instances as effectively.
• Infrastructure as code: Automates deployment and management of infrastructure; it does not describe the architecture being used.

• Physical: Protects facilities or equipment, such as locks and security cameras.
• Technical: Uses technology, such as firewalls, encryption, or access controls.
• Operational: Covers day-to-day actions and processes, such as training, backups, or incident response.
• Managerial: Includes policies, standards, risk assessments, and procedures.

• Error correction (ECC): Improves data reliability but does not maximize bandwidth.
• RAM voltage: Increasing voltage may affect stability or speed, but it is not the primary method for increasing module bandwidth.
• Physical module size: Refers to the capacity or form factor of the RAM, not its data-transfer bandwidth.

1. Create a temporary Onboarding OU.
2. Move the new account into it.
3. Move the restrictive SCPs from the organization root to the Production OU.
4. Allow the account to update AWS Config.
5. Move the account into Production after onboarding.

• An SCP attached at the organization root applies to every account and OU beneath it.
• An SCP attached to the Production OU applies only to accounts in that OU.
• Therefore, moving the restrictive SCP from the root to Production temporarily exempts the onboarding account without weakening the policies for existing production accounts.
• Once onboarding is complete, moving the account into Production subjects it to the normal restrictions.

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

• Domain controllers, because the requirement specifically excludes them. However, note that both member servers and domain controllers run Windows Server, so OS targeting alone cannot distinguish them unless the targeting option allows selecting the relevant server role/version. In the usual exam interpretation, target the applicable server OS category.
• Client computers, because they run a client Windows operating system.

• Domain: Targets membership in a domain, not the computer’s operating-system type.
• Security Group: Would require creating and maintaining a group containing all member servers, increasing administrative effort.
• Environment Variable: Not designed to reliably identify member servers.

• B: Developer Edition has limited user, storage, and data-volume capacity, making realistic community testing difficult.
• C: A Developer Edition org cannot contain sandboxes, so it cannot provide separate environments for development, integration, and UAT.
• E: A standalone Developer Edition org is not part of the production org’s deployment path, so change sets cannot be used to deploy from it directly to that production org. The team would need Metadata API, Salesforce CLI, or another deployment method.

• Custom domains: Supported by Basic and higher tiers.
• Dedicated compute: Basic and Standard use dedicated virtual machine instances; Free and Shared use shared infrastructure.
• Load balancing between instances: Standard provides scaling across multiple instances with load balancing.
• Storage: Standard provides more storage than Basic.
• Cost: Standard is the least expensive option that satisfies all the stated requirements.

• Free/Shared: Use shared compute and have limited features; they don’t meet the dedicated-compute requirement.
• Basic: Provides dedicated compute and custom domains, but does not provide the required Standard-level multi-instance capabilities in the exam’s feature comparison.

• B — The most significant risks are held by SQ.

• C — SQ should recognise the cars as inventory.

• F — SQ recognises revenue when LM sells a car to a third party.

• A: LM does not hold the most significant risks.
• D: LM does not recognise the cars as inventory.
• E: SQ should not recognise revenue when cars are merely delivered to LM.

• Marketing users: Dynamic Forms can show all fields.
• Support users: Field visibility rules can display only the Support preference fields on the record page.
• Reporting: Both profiles can still report on all fields because Dynamic Forms controls page visibility, not the underlying field access.

• A — Two record types and page layouts: Page layouts can control field placement and editability, but they are less flexible for conditional field visibility and would not be the best fit here.
• C — Muting permission set: Permission-set muting is used with permission-set groups; it does not conditionally hide fields on a page.
• D — Field-Level Security: FLS would remove field visibility at the security level. If fields are hidden by FLS, users generally cannot report on or access those fields, conflicting with the requirement that both users report on all data.

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

• A — Tables
• B — Named file formats
• C — Schemas
• E — Databases

Why these are correct

• Tables: Can be cloned using CREATE TABLE ... CLONE. The clone initially uses zero-copy cloning, so storage is shared until changes are made.
• Named file formats: Can be cloned as database objects, preserving the file-format definition.
• Schemas: A schema and its eligible objects can be cloned.
• Databases: A database and its eligible schemas and objects can be cloned.

Why the others are incorrect

• Shares: A share is an account-level data-sharing object, not a normal cloneable database object.
• Users: Users are security principals and cannot be cloned with CLONE.

• CPU: Number of virtual CPUs and, where applicable, CPU reservations.
• Memory: Amount of memory and memory reservations.

• Network interface: Usually configured through the VM or workload networking configuration.
• PCI devices: Specialized hardware and not a standard VM Class resource in this context.
• Storage: Typically selected through storage policies or the VM’s storage configuration.

• Deploy five individual VMs: This does not create a VM scale set.
• Modify Availability Zones or Size settings: These actions do not create the required scale set and add unnecessary steps.
• VM orchestration mode: This is Flexible orchestration, intended for more individually managed VMs and mixed configurations. It is not the best choice for a straightforward group of identical instances.

• Record changes — a flow can start when a record is updated or otherwise changes.
• Schedules — a flow can run at a specified date/time or on a schedule.
• Record inserts — a flow can start when a new record is created.

• Subflows are reusable flow components called by another flow; they are not normally trigger types.
• Record views do not generally initiate a Flow Designer flow.

• Case Assignment Rules normalmente são avaliadas quando o caso é criado. Elas podem ser executadas novamente em uma edição somente se o usuário marcar “Assign using active assignment rules”; isso não acontece automaticamente apenas porque o caso foi fechado.
• Portanto, criar uma regra de atribuição não corrige os centenas de casos já fechados e não garante, por si só, que um caso será transferido antes de ser fechado.

• B — Usar uma ferramenta de dados: corrige os registros históricos já existentes, atualizando o Owner.
• D — Criar uma regra de validação: impede que um caso seja fechado enquanto ainda pertence a uma fila. Exemplo conceitual: se Status = Closed e o proprietário for uma fila, bloquear o salvamento.

• COE: Identifies the Center of Excellence, such as Payroll or Benefits.
• Topic Detail: Classifies the HR service within its COE; it does not identify the catalog item.
• Template: Supplies default values or case configuration.
• Record Producer: Represents the catalog item that employees use to submit the request and create the case.

• A script of cloud CLI commands: IaC because the commands can be saved, reviewed, versioned, and rerun consistently.
• Manually run curl commands: Not necessarily IaC; they are manual actions unless organized into an automated script.
• A sequence of REST requests passed to an API: Could represent automation, but the wording does not explicitly say they are stored and executed as reusable code.
• Commands entered into a cloud console: Manual operation, not IaC.

• SQL injection
• Cross-site scripting (XSS)
• Malicious or malformed web requests
• Some application-layer attacks

• Layer 4 firewall: Filters based mainly on IP addresses, ports, and transport protocols; it cannot deeply inspect web application content.
• NGFW: Provides advanced network filtering and may include application awareness, but a WAF is more specifically designed to protect web applications.
• UTM: Combines several security functions in one appliance, but it is not the most targeted solution for a web portal.

• up ? down ? up
• Often happens rapidly or intermittently

• Faulty or loose cable or connector
• Failing transceiver, NIC, or switch port
• Speed/duplex or auto-negotiation problems
• Power or hardware instability
• Layer 1 interference

• Nothing plugged in: the port is simply down
• Latency: does not directly trigger err-disable
• shutdown: administratively disables the port, but that is not the same as an automatically detected err-disabled condition

• Determine risk tolerance: Tolerance defines how much variation or exposure the organization is willing to accept. Scenarios may help apply tolerance, but they do not primarily determine it.
• Determine risk appetite: Risk appetite is established at an enterprise or governance level. Scenarios help compare risks with the appetite; they do not normally establish it.
• Develop risk responses: Once risks are identified and assessed, scenarios support response planning. However, response development comes later.

• Box 1: No — The rule requires user.department to equal Engineering. Engineer does not match, so User1 is not in AU1. Admin1 cannot reset User1’s password.
• Box 2: No — Admin1’s role is scoped to AU1 and cannot manage users outside that AU.
• Box 3: Yes — Admin2 is a Global Administrator and can reset User3’s password.

• Installing software
• Applying configuration changes
• Calling PowerShell scripts
• Running setup or customization commands

cmd 
powershell.exe -ExecutionPolicy Bypass -File C:\Scripts\ConfigureVM.ps1

• GPO logon script: Runs only when a user logs on and depends on domain/GPO processing.
• GPO startup script: Runs during startup, but requires the VM to be domain joined and receives the applicable GPO.
• Place scripts in a VHD: Merely makes the scripts available; it does not automatically execute them.

Box 1: No

• configure_azure_monitor() configures Azure Monitor and the OpenTelemetry pipeline.
• LangChain requires its own instrumentation or callback tracer, such as AzureAIOpenTelemetryTracer.
• You must pass the tracer to the LangChain execution configuration so chains, tools, prompts, and model calls become spans in Application Insights.

Box 2: Yes

text 
OTEL_SERVICE_NAME=customer-agent 
OTEL_SERVICE_NAME=invoice-agent

• Suspended an operator who correctly refused to use unsafe equipment.
• Rewarded another operator for using the equipment despite the broken safety guard.

• A — Management is not particularly concerned with managing risks.

• B — Employees will perceive that management does not care about health and safety risks.

• C — This factory’s safety record is likely to be poor.

• Initial Intrusion: The compromised VPN account and stolen phishing credentials describe how the attacker first gained access, but that happened months earlier.
• Persistence: The scheduled tasks and recurring C2 connections show how the attacker maintained and automated continued access.
• Search and Exfiltration: This would involve locating and transferring data. The scenario does not primarily describe data discovery or theft.
• Cleanup: Cleanup involves removing evidence or covering tracks. Obfuscated scripts may make detection harder, but the main behavior here is maintaining access.

• Existing measures
• Relationships
• Calculated columns
• Tables and fields
• Existing transformations in the model

• SharePoint folder: Reconnects to the source files. You would likely need to recreate the model and measures.
• Power BI dataflows: Primarily provide reusable data preparation and storage, but they do not automatically provide the existing semantic model and measures.
• Excel workbook: Connects directly to the source file and would also require rebuilding the model and measures.

• Early units show relatively large time savings.
• Later units still take less time, but the reduction becomes progressively smaller.
• The curve therefore becomes flatter as production approaches 256 units.

• B: The reduction is not constant; learning normally diminishes over time.
• C: Time does not reduce at an increasing rate.
• D: A steady state may eventually be reached, but the question concerns the first 255 units while learning is still occurring.

• Additional running costs: $800
• Less depreciation: $300

• The $100 reduction in fixed production overhead absorbed is only an accounting reallocation. It does not represent an actual saving in total fixed overhead.

• Annual interest payments net of tax relief (A): future cash outflows for the issuer.
• Redemption value (B): the final cash outflow when the bond is redeemed.
• Market value now (C): the cash proceeds received now, acting as the initial cash flow in the IRR calculation.

• Job Links ? URL ID: Mainly summarizes link performance; it is not the easiest place to retrieve individual email addresses by alias.
• Tracking Overview ? Clicks: Provides aggregate click metrics, not a targeted list for one aliased link.
• Click Activity ? Link View: Focuses on link-level reporting, but the question’s intended workflow for locating clicks tied to a specific placement/alias is Email Overlay.

• A Screen Flow can present a form that inspectors complete and submit on an Experience Cloud page.
• It can collect inspection findings, validate the input, and create or update records.
• An Autolaunched Flow has no user interface, so it cannot directly provide the form.
• A Related List only displays related records, and Record Detail is primarily for viewing or editing an existing record—not for a custom inspection submission form.

• Suporta domínios personalizados.
• Oferece 50 GB de armazenamento — suficiente para os 10 GB de cada aplicação.
• Usa instâncias de computação dedicadas.
• Inclui balanceamento de carga entre instâncias.
• É o plano mais econômico entre as opções que atendem a todos esses requisitos.