Test Prep TEAS Section 4: Sentence Completion Exam Prep
Test of Essential Academic Skills - Sentence Completion (Page 15 )

• Create a CodeCommit repository in the secondary Region.
• Use CodeBuild to run a Git mirror operation from the primary repository to the secondary repository.
• Use EventBridge to detect relevant repository events, such as a pull request being merged.
• Invoke a Lambda function, which starts the CodeBuild project.

• B: Amazon S3 is object storage, not a Git repository that developers can use as a CodeCommit remote.
• C: CodeArtifact is intended for packages and artifacts, not source-code repository mirroring.
• D: An AWS Cloud9 environment is not an appropriate automated replication mechanism and would require manual or persistent infrastructure management.

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

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.

• Deterministic approve/reject results
• Strict adherence to predefined rules
• Consistent, reproducible outcomes
• Auditability and regulatory compliance

1. Define Power Platform DLP policies

1. Add custom prompt modifications

1. Conduct adversarial testing

Why this is correct

• Each user authenticates with their own Google account.
• Google manages the user’s SSH key association.
• IAM controls who can access instances.
• Access can be audited by user identity, so security can determine who accessed a VM.
• Granting the role to a Google group avoids managing permissions individually.

Why the others don’t apply

• A: A shared private key is difficult to distribute securely and cannot reliably identify which employee used it.
• B: Manually collecting and deploying keys on every instance is operationally inefficient and complicates auditing.
• D: A project-wide shared key has the same identity and key-management problems as option A. It also does not provide per-user accountability.

• Data loss prevention (DLP): Helps detect or prevent sensitive data from being copied or transmitted, but it does not primarily protect a stolen laptop’s stored data.
• Operating system hardening: Reduces vulnerabilities and attack surface but does not encrypt files if the device is stolen.
• Boot security: Helps ensure that only trusted software starts, but it does not fully protect the drive if an attacker accesses it offline.

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

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

• Guiding principles
• Governance
• Service value chain
• Practices
• Continual improvement

• Guiding principles: Recommendations that guide decisions and actions; they do not describe the entire system.
• Four dimensions: Perspectives used to ensure a balanced approach to service management.
• Service relationship: Describes cooperation between a service provider and service consumer, rather than the whole value-creation system.

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

• CCTV system — Detective control: Cameras monitor and record activity, helping identify or investigate security incidents after—or while—they occur.
• Signs about being filmed — Deterrent control: The signs discourage people from attempting unauthorized or criminal activity because they know surveillance is present.

• Preventive: Stops an incident from occurring, such as a lock or access-control system.
• Corrective: Restores systems after an incident.
• Directive: Instructs people to behave in a certain way, such as a security policy.
• Compensating: Provides an alternative control when the preferred control cannot be implemented.

• Identifying the communication strategy: Usually part of a business continuity or incident response plan.
• Evaluating the risk management plan: Part of risk assessment and risk management activities.
• Establishing backup and recovery procedures: Usually part of disaster recovery planning.
• Developing the incident response plan: Part of incident response planning.

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

• BCP (Business Continuity Plan): Ensures the organization can continue its broader business operations during and after a disruption. It is broader than the IT-focused recovery required here.
• Communication plan: Defines how information is shared with employees, the public, and other stakeholders; it does not restore systems.
• IRP (Incident Response Plan): Handles and contains security incidents, such as malware or unauthorized access. A tornado is a disaster, not primarily a cybersecurity incident.

• Replaces the verbal message — this describes non-verbal communication being used instead of words.
• Substitutes for verbal communication — similar; it means communicating without speech.
• Confuses the verbal message — this occurs when non-verbal signals contradict or obscure the spoken message.

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

1. Product + ProductSubCategory: Inner join

1. Result + ProductCategory: Left outer join

• Documented and formally requested
• Analyzed for security, cost, and operational impact
• Reviewed and approved by the appropriate personnel
• Tested before implementation
• Tracked and reversible if problems occur

• Risk management process: Identifies and evaluates risk, but does not directly authorize design changes.
• Product design process: Applies primarily while creating or developing the product.
• Design review process: May have identified the issues, but the next step for changing an already released design is controlled change management.

• Required response and resolution times
• Availability or uptime targets
• Performance standards
• Support obligations
• Remedies or penalties for failing to meet the terms

• SOW (Statement of Work): Defines the project’s scope, tasks, deliverables, and schedule.
• MOA (Memorandum of Agreement): Describes agreed responsibilities between parties, often for a specific activity.
• MOU (Memorandum of Understanding): Records a mutual understanding or intention, usually less formal than a contract.

• Financial performance
• Customer perspective
• Internal business processes
• Learning and growth

• Increasing the number of indicators can make the scorecard cluttered and less useful. Measures should be limited to those that are strategically important.
• The scorecard is mainly a tool for implementing and monitoring strategy, not for formulating strategy.
• It should contain both leading indicators and lagging indicators. Leading indicators predict future performance, while lagging indicators measure results already achieved.

• B. Users accessing Salesforce from public Wi-Fi

• C. Users choosing the same password as their Facebook password

• A: 2FA does not protect an already-authenticated, unlocked session if someone accesses an unattended laptop.
• D: Weak password-reset questions are an account-recovery weakness. 2FA primarily strengthens login authentication, not necessarily the security-question reset process.

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

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

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

• D — Managers focus on keeping costs low in the short term to maximise profits.

• E — Managers are given incentives to meet or undercut budgets.

• F — Managers delegate responsibility simply to reduce their workload.

• Scheduling overlapping working hours for critical collaboration
• Assigning independent tasks that can proceed asynchronously
• Adding clear handoffs between offices
• Documenting decisions, questions, and required inputs
• Building appropriate time into the schedule for responses

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

• Response and resolution time frames
• Availability or uptime requirements
• Performance targets
• Support obligations
• Penalties for failing to meet requirements

• SOW (Statement of Work): Defines the project’s scope, tasks, and deliverables.
• MOA (Memorandum of Agreement): Describes cooperation and responsibilities between parties.
• MOU (Memorandum of Understanding): Records a general mutual understanding, usually without detailed enforceable service targets.

• BCP (Business Continuity Plan): è più ampio e mira a mantenere le funzioni essenziali dell’organizzazione durante un’interruzione. Il DRP è una componente più specifica del BCP.
• Communication plan: stabilisce come comunicare con dipendenti, cittadini e altre parti interessate, ma non ripristina i sistemi.
• IRP (Incident Response Plan): gestisce la risposta iniziale a un incidente di sicurezza, come un attacco informatico, non principalmente il recupero da un disastro fisico.

sql 
CREATE PROCEDURE dbo.usp_CreateOrder 
AS 
BEGIN 
    SET NOCOUNT ON; 
    SET XACT_ABORT ON; 


    BEGIN TRY 
        BEGIN TRANSACTION; 


        INSERT INTO dbo.Orders (/ columns /) 
        VALUES (/ values /); 


        SET @OrderID = SCOPE_IDENTITY(); 


        COMMIT TRANSACTION; 
    END TRY 
    BEGIN CATCH 
        IF @@TRANCOUNT > 0 
            ROLLBACK TRANSACTION; 


        THROW; 
    END CATCH; 
END;

• BEGIN TRY contains the transactional work.
• SCOPE_IDENTITY() retrieves the identity generated by the INSERT; it belongs after the insert, not as the error-handling logic.
• COMMIT runs only if all statements succeed.
• BEGIN CATCH handles failures.
• IF @@TRANCOUNT > 0 prevents attempting a rollback when no transaction is active.
• ROLLBACK undoes partial changes.
• THROW re-raises the original error with consistent details for the application.
• SET XACT_ABORT ON ensures many run-time errors automatically terminate and roll back the transaction.

• A: It allows for branching and merging...

• C: It allows multiple engineers to work against the same code and configuration files and manage differences and conflicts.

• B: Build automation and infrastructure provisioning are handled by CI/CD and automation tools, not by version control alone.
• D: User Stories and backlogs are managed by project-management tools.
• E: Version control stores and tracks code, but it does not itself ensure that developers write effective unit tests.

• Managerial: policies, standards, risk management, governance
• Operational: procedures carried out by people, such as training, incident response, and backups
• Technical: firewalls, encryption, access-control systems
• Physical: locks, guards, cameras

• 800 devices ? a scalable, centralized solution is needed.
• Four hardware/vendor classes ? the tool must handle different drivers and images.
• Two user groups ? it should allow different configurations for each group.
• “Distribute custom images” ? an imaging/deployment tool is required, not just a file-copy utility.

• Microservices: An application-design approach that divides an application into smaller services. It does not inherently reduce the number of operating systems.
• Virtualization: Creates virtual machines, but each VM generally requires its own complete operating system. This improves isolation but does not minimize OS instances as effectively.
• Infrastructure as code: Uses code to automate infrastructure deployment and configuration. It improves consistency but does not determine how many operating systems are used.

• Custom domain: miami.weyland.com requires a paid App Service tier; Free and Shared are unsuitable.
• Two instances: Standard supports scaling to multiple instances.
• SSL: Standard includes SSL support.
• 12 GB storage: Basic provides only about 10 GB, so it does not meet the requirement. Standard provides substantially more storage.
• Cost minimization: Standard is the lowest tier among the choices that satisfies all requirements.

• Blue team: Defends systems, monitors activity, and responds to attacks.
• Purple team: Coordinates red- and blue-team activities to improve defenses.
• White team: Oversees or manages the exercise, including rules and scope.

• Encryption to preserve confidentiality
• Integrity protection to detect alteration
• Authentication of the server through certificates

• SHA-256: A hashing algorithm; it does not encrypt data for transmission.
• SSL 3.0: Obsolete and insecure. It should not be used.
• AES-256: A strong encryption algorithm, but by itself it does not provide the complete secure communication protocol needed for data in transit.

• Plenum: Describes a fire-resistant cable jacket rating, not a transmission medium or speed.
• Ethernet: Describes a networking technology; Ethernet can use copper or fiber, so the term alone does not identify the fastest cable type.
• DAC (Direct Attach Copper): Uses copper and is typically intended for short-distance, high-speed connections in data centers.

• An active relationship is used automatically when filters are evaluated. An inactive relationship does not propagate filters unless explicitly activated in DAX, so it would not reliably enforce the required security behavior.
• Apply security filter in both directions allows RLS filters to propagate across the relationship in both directions. This ensures that bidirectional filtering respects the RLS rules applied to both tables.
• Assume referential integrity is unrelated to RLS. It is mainly a DirectQuery optimization that allows Power BI to use an inner join when matching keys are guaranteed to exist.
• The relationship must therefore be active, with security filtering enabled in both directions.

• Periodic vulnerability assessments: Identify technical weaknesses but do not establish governance or ensure risks are managed.
• Established information security metrics: Help measure performance and report status, but measurement alone does not make governance effective.
• Advanced security technologies: Support security operations, but governance is primarily about direction, accountability, decision-making, and alignment with business objectives.

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

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

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

1. Install a Cassandra-compatible ODBC driver.
2. Configure a data source name (DSN), if required.
3. In Power BI Desktop, select Get Data > ODBC.
4. Choose the configured DSN and connect.

• Microsoft SQL Server database: Connects to SQL Server, not Cassandra.
• OLE DB: Requires a compatible OLE DB provider; this is not the standard choice for Cassandra in Power BI.
• OData: Requires Cassandra data to be exposed through an OData service, which is not the normal direct connection method.

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

• Gaia Portal: Controlled by Gaia administration settings, not SmartConsole Trusted Clients.
• SSH: Controlled by Gaia or operating-system SSH access settings.
• Security Gateway(s): SmartConsole connects to the Security Management Server, not directly to gateways for this purpose.

1. Define – establish the project’s objectives, scope, feasibility and requirements.
2. Design – plan how the project will be carried out, including resources, schedules and controls.
3. Deliver – execute the project and produce the required outputs.
4. Develop – close the project formally and capture learning for future projects.

• Filing documentation and records
• Closing project and accounting systems
• Settling costs
• Handing over the completed work and obtaining sign-off
• Reviewing performance and giving feedback